opencode acp mode ignores OPENCODE_CONFIG_CONTENT and OPENCODE_CONFIG_DIR #34638

Activity

1. github-actions

   assigned

   nexxeln

   on Jun 30, 2026
2. github-actions commented on Jun 30, 2026

   

   github-actionsBot

   on Jun 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • opencode serve ignores configuration #19078: opencode serve also ignores configuration env vars (OPENCODE_CONFIG/provider config) — same class of problem where a non-TUI mode bypasses env-based config overrides.
3. Nnyan commented on Jul 1, 2026

   

   Nnyan

   on Jul 1, 2026

   Author

   More actions

   Empirical verification (2026-06-30, opencode 1.17.11, Linux)

   Reproduced with a test listener on a random loopback port:

   • OPENCODE_CONFIG_CONTENT env var: NOT honored ✅ (confirms the issue)
   • OPENCODE_CONFIG env var (file path): NOT tested but likely same code path
   • cwd opencode.json: IS honored ✅ (new finding)

   The cwd opencode.json test: wrote a custom provider config to <cwd>/opencode.json, launched opencode acp with all override env vars stripped. The agent resolved the custom provider (session/new returned currentValue: "charon_probe/cpt") and routed 2 API calls through the test listener. Full trace available.

   Impact update

   There IS a workaround for Charon/SLOP-Platform/charon: write per-run opencode.json into the ACP subprocess cwd (Charon already controls the worktree cwd for each ACP subprocess). This unblocks the per-run-proxy routing approach without mutating the user global config.

   Correction suggestion

   The issue title mentions OPENCODE_CONFIG_DIR. That env var points at a resource directory (agents/commands/plugins/skills scanning), not a config file path. The correct env var for a config file override is OPENCODE_CONFIG (Flag.OPENCODE_CONFIG). Recommend updating the title accordingly.

   Root cause (per architecture analysis)

   ACP is a separate entry point (packages/opencode/src/acp/agent.ts) from CLI/TUI. It resolves config independently and never calls resolveNetworkOptions() in packages/opencode/src/cli/network.ts. PR #23318 adds getGlobalWithOverrides() to fix serve/web — the same pattern needs wiring into the ACP agent path.
4. Nnyan commented on Jul 1, 2026

   

   Nnyan

   on Jul 1, 2026

   Author

   More actions

   Update: found a workaround. While OPENCODE_CONFIG_CONTENT is ignored by opencode acp, the subprocess DOES honor a per-run opencode.json in its current working directory. By writing the config to the worktree and launching opencode acp from there, we can inject per-run provider overrides.

   Tested working on opencode 1.17.11 Linux. The cwd config approach resolves the immediate blocker, but the root cause (ACP mode skipping the standard config initialization) should still be fixed for robustness.
5. nexxeln commented on Jul 1, 2026

   

   nexxeln

   on Jul 1, 2026

   Contributor

   More actions

   i couldnt reproduce this on latest/dev
6. github-actions commented on Aug 31, 2026

   

   github-actionsBot

   on Aug 31, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
7. github-actions

   closed this as not plannedon Aug 31, 2026