Repository navigation
fix(agent): opencode v2 acp_status renders the status panel (panel-first) - #912
Conversation
…rst) The forwarded kernel acp_status returns the legacy flat report while the /acp command shows the rich status panel — tool and command disagreed. acp_status is read-only, so the plugin now reads the panel from the proxy's status endpoint first and falls back to forwardTool when no panel is served (older proxy, unknown conversation). Fixes #911
[bot] 🏷 Picked up for review. This is a [PR] mirror of #912 (head |
[bot] 🏷 Review complete — verified, no changes needed, ready for human merge. What I verified (independently re-ran everything at head
One non-blocking observation for the record: an 中文摘要: 让 opencode v2 的 |
89928fe
into
2026-09-15_opencode-native-plugin
Fixes #911
What
In native/launcher/attach modes the v2 plugin forwarded
acp_statusto the proxy's tool endpoint, which returns the legacy flat report — while the/acpslash command renders the rich panel. Tool and command disagreed.Now
acp_status(read-only) reads the panel from the proxy's status endpoint (status.panel, same source as/acp) and returns it; falls back toforwardToolwhen no panel is served (older proxy / unknown conversation). No proxy-side change; bili pi untouched.Re-lands the panel-first UX from the closed #909 on the v2 mainline (align on the native-proxy architecture; the in-process kernel is superseded).
Test
tests/opencode-v2.test.ts: panel served → tool returns panel; status 404 → falls back to forwarded tool result.Pre-flight
npm run typecheck✅ ·npm run build✅Verified live in the oc2 rig container: native self-spawn proxy + model request routed +
status.panelserved for the live session.