Bug
When the Root Agent creates sub-agents in deep mode, the new tmux terminal sessions don't inherit the Caido proxy configuration (HTTP_PROXY, HTTPS_PROXY, REQUESTS_CA_BUNDLE, SSL_CERT_FILE).
Steps to Reproduce
- Run Strix in deep mode against an external HTTPS target
- Root Agent performs recon successfully (curl, katana, nmap work)
- Root Agent creates sub-agents (e.g., SQLi Discovery Agent)
- Sub-agent runs
curl or httpx → fails with proxy/container errors
Expected Behavior
Sub-agent terminal sessions should inherit the same proxy and CA certificate configuration as the Root Agent.
Root Cause
TerminalSession.initialize() creates a new tmux session with /bin/bash but doesn't source /etc/profile.d/proxy.sh which is where docker-entrypoint.sh writes the proxy vars.
Fix
PR #429 — sources the proxy config in each new terminal session.
Environment
- Strix version: 0.1.13 (sandbox image)
- OS: macOS (Docker Desktop)
- LLM: Gemini 3.1 Pro via Google AI Studio
Bug
When the Root Agent creates sub-agents in deep mode, the new tmux terminal sessions don't inherit the Caido proxy configuration (
HTTP_PROXY,HTTPS_PROXY,REQUESTS_CA_BUNDLE,SSL_CERT_FILE).Steps to Reproduce
curlorhttpx→ fails with proxy/container errorsExpected Behavior
Sub-agent terminal sessions should inherit the same proxy and CA certificate configuration as the Root Agent.
Root Cause
TerminalSession.initialize()creates a new tmux session with/bin/bashbut doesn't source/etc/profile.d/proxy.shwhich is wheredocker-entrypoint.shwrites the proxy vars.Fix
PR #429 — sources the proxy config in each new terminal session.
Environment