Can OpenCode use a Claude subscription?

Anthropic's help centre and Claude Code's legal page say four things:

• A plan's usage is for Anthropic's own apps. It is designed for ordinary use of the Claude web, desktop and mobile apps and Claude Code.
• Third-party tools should use an API key. The preferred way in is API key authentication through the Claude Console or a supported cloud provider, open-source projects included.
• Some tools may run on usage credits. Anthropic may let paid subscribers who switched on usage credits use certain third-party tools. It reserves the right to draw that use from usage credits rather than plan limits, and the subscriber pays those charges.
• Disguised traffic is prohibited. A tool that misrepresents its identity to Anthropic's servers, or routes third-party traffic against plan limits, may be enforced against.

A Team or Enterprise seat is a subscription plan too, so the same rule covers it. A request that Anthropic counts as a third-party app's is answered with its own message:

OpenCode's own providers page says plugins exist that let OpenCode use Claude Pro and Max models, and that Anthropic explicitly prohibits this. OpenCode bundled such plugins in earlier versions. As of 1.3.0 it no longer does.

Anthropic's help centre prohibits a tool that misrepresents its identity to Anthropic's servers or routes third-party traffic against plan limits, and says such use may be enforced against. The account at risk is the one whose plan the plugin signs in with.

• A Claude API key from the Claude Console, billed per token. This is the route Anthropic names for third-party tools.
• Claude on a cloud provider, which Anthropic also names, billed to your cloud account.
• Subscriptions OpenCode supports with no setup: ChatGPT Plus, GitHub Copilot and GitLab Duo, per OpenCode's providers page.
• OpenCode's own models: Zen, a list of models the OpenCode team provides, and Go, a low-cost subscription to open coding models.

A key added with OpenCode's /connect is saved on that machine, in ~/.local/share/opencode/auth.json.

Each developer then holds a provider key of their own, in a file on their laptop. That has three costs:

• the key spends outside every limit the company set;
• its usage belongs to a key rather than to a person;
• its prompts skip any secret scanning the team's other requests go through.

Keeping keys off laptops altogether is covered in the guide to keeping API keys off developers' laptops.

One command instead of opencode. It needs OpenCode 2 and selan 1.24.0 or later.

• The company's models. Every model in its Selan catalog is in OpenCode's /models: Claude, GPT, Gemini on Vertex, OpenRouter, Ollama, whatever it connected. See which models.
• No key on the laptop. Selan writes nothing to OpenCode's config, and no credential lands on disk. See your config file.
• The same rules as Claude Code and Codex. Each request is the developer's own, under their sign-in, with the company's allowed models, spend limits and secret scanning.
• Connectors and skills. The company's MCP connectors and plugin skills come with it.

Tested with OpenCode 2.2.0: its requests reached Selan's gateway and were served, tool calls included.

For one developer with a key or a plan of their own. ChatGPT Plus and GitHub Copilot work in OpenCode with no setup, and a single key in /connect is simple and enough.

Selan earns its place once a team shares the bill and the company wants each person's usage shown and capped, OpenCode beside Claude Code and Codex. Which providers a company can connect is on running any model on your own accounts and models and providers.

Free for up to three seats, and the Free plan needs no card.