[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

[alexwork1611]

Nice 1️⃣!

[alexwork1611]

@juliusmarminge, please check this out!

[Haddadios]

This is awesome, I can't wait to have this in T3Code, really want to use OpenCode 2 through T3Code

[0pilatos0]

With opencode2 being the new default +1 from me

[olivierreuland]

It feels like this is now an issue rather than an idea, knowing v2 is the default.

[gjertsenjostein]

Agreeing with the comments above, this now qualifies as an issue @juliusmarminge

[hardik88t]

#12643 seems to be v2 support in work

[alexwork1611]

Nice 1

[orielhaim]

finally

[DileSoft]

I made v2 support: #13958

[juliusmarminge]

Thanks for reporting the OpenCode 2 compatibility gap. The orchestrator V2 work has now merged in #2829.

V2 now supports OpenCode 2, with the shipped compatibility policy requiring version 2.0.18 or newer for supported 2.x use. Update OpenCode and use the existing OpenCode provider; a separate V2 provider entry is not needed.

Closing this as delivered. If a specific part is still missing in a build containing V2, please open a focused follow-up with the provider/version and the behavior you are seeing.

[alexwork1611]

Thanks a lot!