Self-disable should also trigger in manual proxy mode (detect /bili/ in baseURL), not only via BILLION_CONTEXT_PROXY

[ranxianglei]

Problem

opencode-acp only self-disables when BILLION_CONTEXT_PROXY is set. That env var is set exclusively by the bili <client> launcher (e.g. bili opencode), which exports it into the spawned client process.

When a user runs manual proxy mode — bili start + pointing opencode's provider baseURL at the proxy (e.g. http://127.0.0.1:8787/bili/https://<upstream>) — the env var is absent, so opencode-acp stays active even though the proxy is in the request path.

Result: two competing ACP authorities — opencode-acp's client-side compression engine and the proxy's server-side compression engine (two uncoordinated states), duplicate tool names (compress/decompress/search_context/acp_status), and the /acp panel showing the wrong (client-side) state.

Root cause

The guard in index.ts is env-var only:

if (process.env.BILLION_CONTEXT_PROXY) {
  console.log("[opencode-acp] disabled: BILLION_CONTEXT_PROXY detected — proxy handles compression")
  return {}
}

There is no detection of the proxy in the provider baseURL.

Expected behavior

opencode-acp should also self-disable when its provider's baseURL contains the /bili/ prefix (the zero-config proxy routing prefix). This matches the behavior already documented in billion-context CONFIGURATION.md:

The /bili/ prefix doubles as a self-detection signal: billion-context client extensions (billion-context-pi / opencode-acp) recognize it in their own baseUrl and self-disable, so you never get double compression.

So the documented self-detection is not actually implemented for the manual-proxy case — only the launcher (env-var) path works.

Suggested fix

In addition to the BILLION_CONTEXT_PROXY env check, inspect the opencode provider config (available via the config hook / ctx) for any provider whose baseURL contains /bili/, and self-disable (log + return {}) when found. Keep the env-var check as-is for the launcher path; the two signals are OR-ed.

Repro

1. bili start --port 8787
2. In opencode config, set a provider baseURL to http://127.0.0.1:8787/bili/https://<upstream-host>.
3. Keep opencode-acp in the plugin list.
4. Run plain opencode (NOT bili opencode).
5. Observe: no [opencode-acp] disabled log — the plugin stays active → double compression + wrong /acp state.

References

• billion-context#265 (user report + discussion)
• billion-context CONFIGURATION.md (documented /bili/ self-detection signal)
• opencode-acp PR fix: self-disable when running under billion-context proxy #335 (the env-var-only self-disable that shipped in v1.14.25)

_{🤖 ework agent · vllm-qwen/qwen3.8-27b}

---

Mirrored from ework issue #337

[ranxianglei]

处理这个问题

[ranxianglei]

已处理 — PR: #338

Root cause: the v1.14.25 self-disable only checks BILLION_CONTEXT_PROXY, which only the bili <client> launcher sets. Manual proxy mode (bili start + provider baseURL pointed at the proxy) leaves it unset, so ACP stayed fully active on top of a proxy that already manages context.

Fix (branch 2026-08-27_bili-proxy-self-disable):

• New lib/bili-proxy.ts — pure findBiliProxyProviders(): scans every provider's options.baseURL (defensive top-level fallback) for the documented /bili/ path prefix. Lookalikes (/bilix/, bilibili.com, bare /bili) do not match.
• index.ts config hook (fires before the first LLM request — the only non-deadlocking point that sees the merged provider config; awaiting client.config.get() in the plugin factory deadlocks, verified empirically): on detection it
  • sets permission: "deny" for all five ACP tools — verified against a live opencode 1.14.46 instance that this removes them from the LLM tool list,
  • skips /acp command registration and primary_tools wiring,
  • sets a factory-scoped flag that no-ops all five ACP hooks (system prompt, message transform, text complete, command, event) via a type-safe guard() wrapper — no signature changes in lib/hooks.ts.
• The flag is assigned, not latched: a config reload without the proxy restores ACP. The BILLION_CONTEXT_PROXY env-var fast path is unchanged.

Verification: 15 new tests (11 unit + 4 integration through the real plugin factory with isolated XDG homes), full suite 1044/1044 pass, typecheck + build clean, scripts/ci/check-pr.sh passes locally. Devlog: devlog/2026-08-27_bili-proxy-self-disable/ (REQ/DESIGN/WORKLOG).

Note: GitHub Actions did not trigger for this PR (no workflow runs repo-wide since Aug 24 — appears inactive); all checks were run locally instead. PR is ready for review + merge.

_{🤖 ework agent · vllm-qwen/qwen3.8-27b}