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
OpenCode v2 is not supported by Orca’s Chat UI. Users must rely on the terminal view or layer another agent interface over an OpenCode session, which is especially problematic on mobile where the workaround can lag.
Proposed solution
Add first-class OpenCode v2 support to the Chat UI, including starting and resuming OpenCode v2 sessions and rendering their conversation and interaction states natively.
Alternatives or additional context
This request is specifically for OpenCode v2; it should not be treated as support for only the legacy OpenCode v1 integration.
This request is specifically about first-class OpenCode v2 support in the native Chat UI, rather than treating OpenCode as a terminal-only integration or placing a second agent interface over an OpenCode terminal.
Why v2 needs explicit scope
OpenCode v2 is not simply a renamed v1 process. Its session and plugin contracts differ, and Orca already models it separately as opencode2. The Chat UI support should therefore detect and preserve the actual OpenCode version/session identity instead of assuming that the opencode executable name means the legacy integration.
The desired experience is the same coherent chat surface available for other supported agents:
Create a new OpenCode v2 chat from the agent picker.
Open an existing OpenCode v2 session directly in Chat UI.
Resume the same v2 session without creating a parallel conversation or losing its history.
Send a message, show it as pending only until the agent receives it, and render streamed/updated assistant output in order.
Switch between Chat UI and terminal without changing session ownership, status, or transcript identity.
Work on desktop, mobile, local workspaces, and SSH-hosted workspaces wherever the underlying OpenCode v2 session is available.
Existing integration work that should be reused
This should build on Orca's existing OpenCode v2 integration rather than introduce a second adapter:
opencode2 is already a distinct agent type with its own launch command, label, resume capability, and native-chat profile.
The v2 status plugin has a separate identity and hook endpoint, which should remain distinct from the v1 plugin and avoid duplicate-plugin/config-overlay regressions.
Orca already has a v2 transcript reader for the session_v2 and session_message SQLite schema. That reader should be the source of truth for loading history and incremental updates, including text, tool activity, files/attachments, errors, and interrupted outcomes.
The native-chat interactive-send path already recognizes OpenCode/OpenCode v2. The work should make delivery and acknowledgement reliable for real v2 sessions, not fall back to a visual-only transcript.
Functional expectations / acceptance criteria
Correct selection and versioning
A detected OpenCode 2.x installation is offered as OpenCode 2 in Chat UI.
A generic opencode command that reports version 2.x is routed to the v2 implementation; an opencode2 binary must work as well.
Existing v1 sessions remain supported and are never silently parsed or resumed as v2 sessions.
Session fidelity
Opening or resuming a v2 session displays the complete persisted conversation in chronological order.
New messages and assistant updates appear without requiring a manual refresh.
Tool calls/results, file attachments, system/error notices, and interrupted/cancelled runs remain intelligible rather than disappearing or being reduced to raw terminal output.
A subagent or background activity must not cause messages or status from one v2 session/pane to appear in another.
Interactive behavior
Sending from the Chat UI delivers the prompt to the intended running or resumed OpenCode v2 session exactly once.
Stop/cancel is scoped to that session, and the UI converges to the correct idle/busy state afterwards.
Any question, confirmation, or form-style interaction emitted by v2 has a usable Chat UI path; unsupported interaction types should surface a clear fallback/action rather than leave the chat apparently stuck.
Host and configuration safety
The implementation works with local and remote execution hosts and does not assume a local SQLite path or local-only process status.
It must not overwrite, shadow, or unexpectedly disable a user's OpenCode configuration/plugins.
v1 and v2 can coexist without plugin-ID collisions or cross-session state leakage.
Include a real OpenCode v2 smoke test or a captured protocol/transcript fixture for the supported v2 release range.
Verify the mobile Chat UI path as well as desktop, since avoiding the current terminal/overlay workaround is a primary reason for this request.
Out of scope for the first milestone: redesigning the OpenCode TUI itself or claiming that every future OpenCode v2 plugin event is natively rendered on day one. The first release should instead provide a reliable, version-aware Chat UI path with graceful fallback for an event that has not yet been mapped.
Activity
[-][Feature]: Opencode supports Chat UI.[/-][+][Feature]: Support OpenCode v2 in Chat UI[/+]AmethystLiang commentedon Oct 13, 2026
This request is specifically about first-class OpenCode v2 support in the native Chat UI, rather than treating OpenCode as a terminal-only integration or placing a second agent interface over an OpenCode terminal.
Why v2 needs explicit scope
OpenCode v2 is not simply a renamed v1 process. Its session and plugin contracts differ, and Orca already models it separately as
opencode2. The Chat UI support should therefore detect and preserve the actual OpenCode version/session identity instead of assuming that theopencodeexecutable name means the legacy integration.The desired experience is the same coherent chat surface available for other supported agents:
Existing integration work that should be reused
This should build on Orca's existing OpenCode v2 integration rather than introduce a second adapter:
opencode2is already a distinct agent type with its own launch command, label, resume capability, and native-chat profile.session_v2andsession_messageSQLite schema. That reader should be the source of truth for loading history and incremental updates, including text, tool activity, files/attachments, errors, and interrupted outcomes.Functional expectations / acceptance criteria
Correct selection and versioning
opencodecommand that reports version 2.x is routed to the v2 implementation; anopencode2binary must work as well.Session fidelity
Interactive behavior
Host and configuration safety
Validation
Out of scope for the first milestone: redesigning the OpenCode TUI itself or claiming that every future OpenCode v2 plugin event is natively rendered on day one. The first release should instead provide a reliable, version-aware Chat UI path with graceful fallback for an event that has not yet been mapped.