Skip to content

[FEATURE]: First-class Claude Code bridge / external runtime support for Claude models #20002

@nianyi778

Description

@nianyi778

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I'm a Claude Pro/Max subscriber using OpenCode daily. After upgrading to 1.3.x, I noticed the built-in Anthropic OAuth was removed (#18186). Before that, I was constantly hitting Token refresh failed: 429 — same as what's reported in #18329, #18315, and #15562.

Right now I'm using the community plugin opencode-claude-bridge, which reads credentials from my local Claude Code installation instead of doing its own OAuth token refresh. It works, and it's been stable for me.

What I'm requesting: make this kind of path a first-class feature instead of relying on community plugins.

Specifically:

  • External runtime / bridge mode: let OpenCode use Claude models through a local Claude Code installation. OpenCode handles UX, tools, and sessions; Claude Code handles auth and request format. This avoids OpenCode needing to own subscription token refresh logic.
  • Detection and migration: if OpenCode detects that Anthropic OAuth is broken but Claude Code is installed and logged in locally, offer a one-click switch to bridge mode instead of just showing Token refresh failed: 429.
  • Better error diagnostics: replace raw errors like Token refresh failed: 429 with actionable messages — e.g. "Anthropic OAuth refresh failed. Claude Code is installed on this machine. Switch to bridge mode?"

Why this is different from #18329 / #18315 / #15562: those are bug reports about the old OAuth flow breaking. This is a feature request for a more durable integration path that doesn't depend on OpenCode managing Claude subscription tokens directly.

If policy or legal reasons prevent official support, I'd appreciate a clear statement so the community knows to maintain plugins independently. Either way, I'm happy to help test.

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions