Agent profiles: explicit network grant for workflows that need raw DNS, ICMP or TCP #1968

Open
opened 2026-11-13 13:15:18 +00:00 by sam · 0 comments
Owner

Problem

Since #1867 every task container runs on an internal sandbox bridge. Image-profile workflows that need raw network access (for example a firewall investigator using DNS, ICMP or arbitrary TCP) had it only because containers used to join the daemon's network. No profile grants it explicitly: AgentProfile carries only image and tools.

Wanted

An explicit, per-profile network grant, edited through the control plane and dashboard, that attaches that profile's containers to a routed network. Every profile without it stays sandboxed. The grant is visible where the profile is configured.

Done when

  • A profile with the grant can resolve DNS and open TCP connections; one without it cannot.
  • The grant is set and shown in the dashboard, and applies on the next task without a restart.
## Problem Since #1867 every task container runs on an internal sandbox bridge. Image-profile workflows that need raw network access (for example a firewall investigator using DNS, ICMP or arbitrary TCP) had it only because containers used to join the daemon's network. No profile grants it explicitly: AgentProfile carries only image and tools. ## Wanted An explicit, per-profile network grant, edited through the control plane and dashboard, that attaches that profile's containers to a routed network. Every profile without it stays sandboxed. The grant is visible where the profile is configured. ## Done when - A profile with the grant can resolve DNS and open TCP connections; one without it cannot. - The grant is set and shown in the dashboard, and applies on the next task without a restart.
sam added the featuremedium labels 2026-11-13 13:15:26 +00:00
sam added the deferred label 2026-11-15 17:26:09 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1968