You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Compiler must pass --enable-opencode to AWF when engine=opencode #29430
PR github/gh-aw-firewall#2337 gates the OpenCode API proxy listener (port 10004) behind an explicit --enable-opencode CLI flag. Previously, the listener started unconditionally whenever any credential was present (OPENAI_API_KEY, ANTHROPIC_API_KEY, or COPILOT_AUTH_TOKEN).
After this change lands, OpenCode workflows compiled by gh-aw will silently lose access to port 10004 because the compiler does not currently emit --enable-opencode.
Current Behavior
BuildAWFArgs() in pkg/workflow/awf_helpers.go does not emit --enable-opencode
The OpenCode engine routes through an existing backend port (10000–10003) via UniversalLLMConsumerEngine, but port 10004 (OpenCode's unified dynamic-routing endpoint) will no longer start
Expected Behavior
When config.EngineName == "opencode", the compiler should:
Add --enable-opencode to AWF args in BuildAWFArgs()
Add port 10004 to --allow-host-ports so the agent container can reach the OpenCode listener
Activity