Context
The agent-vault run wrapper sets NO_PROXY on the child to a fixed localhost,127.0.0.1,<broker_ip> (confirmed: a pre-set NO_PROXY is ignored; agent-vault run --help lists no flag to customize it).
This makes it impossible to exclude additional in-container loopback/wildcard hosts (e.g. a dashboard bound to 0.0.0.0:9119) from the MITM. The in-container ws client then routes through the MITM, which cannot dial 0.0.0.0, breaking the dashboard chat. (Related Hermes issue: dashboard ws client dials the bind host instead of loopback.)
Request
A flag or env var (e.g. AGENT_VAULT_NO_PROXY / --no-proxy) to extend the bypass list, or have the wrapper merge the pre-set NO_PROXY with its defaults rather than overwriting it.
Workaround currently in use
Patching the wrapped application to use 127.0.0.1 for its in-container client URL (see related Hermes issue).
Context
The
agent-vault runwrapper setsNO_PROXYon the child to a fixedlocalhost,127.0.0.1,<broker_ip>(confirmed: a pre-setNO_PROXYis ignored;agent-vault run --helplists no flag to customize it).This makes it impossible to exclude additional in-container loopback/wildcard hosts (e.g. a dashboard bound to
0.0.0.0:9119) from the MITM. The in-container ws client then routes through the MITM, which cannot dial0.0.0.0, breaking the dashboard chat. (Related Hermes issue: dashboard ws client dials the bind host instead of loopback.)Request
A flag or env var (e.g.
AGENT_VAULT_NO_PROXY/--no-proxy) to extend the bypass list, or have the wrapper merge the pre-setNO_PROXYwith its defaults rather than overwriting it.Workaround currently in use
Patching the wrapped application to use
127.0.0.1for its in-container client URL (see related Hermes issue).