[Feature]: Opencode V2 support

[heymaaz]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/server

Problem or use case

I want to use opencode2 with t3code

Proposed solution

Add another provider for opencode2 in settings providers, will be easier to switch to opencode2 when it goes stable in a couple of weeks.

Why this matters

Users that have opencode2 can’t use t3 code.

Smallest useful scope

Add a toggle in current opencode providers for v1 /v2

Alternatives considered

I tried switching binary path to v2 but that didn’t work. I get the error:

OpenCode — Unavailable. Failed to execute OpenCode CLI health check: Unable to determine OpenCode version from 'opencode -
-version' output. T3 Code requires OpenCode v1.14.19 or newer.

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[heymaaz]

I implemented an ACP-based OpenCode 2 provider on a branch

It keeps OpenCode V1 unchanged and adds opencode2 separately using opencode2 acp.

I have tested that it works locally with opencode2 v0.0.0-next-17444

The change is big (2,949 additions and 17 deletions) because it touches the provider adapter and lifecycle tests. I have not created a PR as it is 1000+ lines and contributions are paused. I planned with Sol, implemented with Luna and then got some back and forth reviews with Sol.

I chose ACP over SDK because T3 Code already has a shared ACP runtime for Cursor and Grok, allowing the OpenCode V1 SDK integration to remain untouched.

Provider health and authentication

Model discovery and working conversation