[Bug]: Cannot select other agents

[ankarhem]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Fresh t3code-desktop, default agents in opencode
2. Connected opencode
3. Cannot change to plan mode

Expected behavior

Be able to select primary agents in opencode (switch to plan)

Actual behavior

Only Build is available

Impact

Blocks work completely

Version or commit

tag v0.0.38

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[eduardozf]

Validated against v0.0.38 and current main. This is intentional client-side gating, not failed OpenCode agent discovery.

OpenCode v1.14.19 defines Build and Plan as primary agents. T3 forwards visible primary agents, but filters out Plan when planModeEnabled is false. See getProviderModelCapabilities.

This setting defaults to false on fresh installs and was introduced in #6420.

As a result, a fresh install using the default OpenCode agents will only show Build.

To enable Plan:

Settings → General → Legacy features → Plan mode (legacy)

If there's interest in having OpenCode's Plan agent available by default, it would be worth opening a discussion about it.

[ankarhem]

Since plan mode is enabled by default in opencode, I expected the same to be true when using through t3code.

[juliusmarminge]

Thanks for taking the time to report this and provide the details. We revisited it during the orchestrator V2 cleanup.

OpenCode Plan is intentionally hidden while the legacy Plan mode setting is disabled. Enabling Plan mode in Settings makes it available. I understand expecting the same defaults as OpenCode itself; changing that default would be a separate product decision.

I’m closing this as answered, rather than attributing it to a new V2 fix.

Source reviewed.

Close as answered/expected configuration, not as a V2 fix. Keeping OpenCode Plan available by default would be a product change.

If you still hit this on a current build, please reply with the app/server versions and the steps that reproduce it. We can reopen this if the original problem is still there.