OpenCode adds Claude subscription access through local Claude Code

OpenCode has added a way to use a Claude subscription through a locally installed copy of Claude Code. Version 2.2.3, released on October 30, introduces a provider called Claude Agent. Developers can keep OpenCode’s working interface while using their own Claude Code login and available models. OpenCode also announced subscription access through its official account that day.

The integration was proposed on October 24 and merged on October 30. Its author says it runs the user’s Claude program through Anthropic’s Claude Agent SDK. The SDK is a library for running Claude Code inside another application. Unlike a client library that calls the model API directly, it operates the Claude Code program. Anthropic’s SDK exposes file tools, permissions and persistent sessions to applications.

A subscription login consumes the existing plan allowance. Anthropic’s help page, updated on October 7, says Agent SDK and noninteractive Claude Code work still draw from subscription limits when signed in with a Claude plan. An API-key login follows separate billing. Monthly API credits included in Max, Ultra and Team plans apply when running with a key from the linked Console organization. Which allowance pays depends on the authentication route.

Edits and commands use OpenCode’s tools and permissions. OpenCode supplies project instructions and compacts conversations; Claude Code’s own tools, settings files, automatic memory and user hooks are disabled.

Claude Code must be installed and signed in on the same machine. Hosted OpenCode and remote workspaces are unsupported, as are Claude Code cloud sessions and computer use.

Authentication and connection setup

Anthropic’s current compliance documentation describes conditions for running an unmodified Claude Code binary within another platform. The platform must preserve its built-in authentication methods. Every end user must sign in with their own subscription, API key or cloud-provider credentials, and usage is billed directly under that user’s agreement. Platforms are restricted from paying for, reselling or intermediating usage on their users’ behalf. Product names and branding must also avoid implying Anthropic built, endorses or partners with the integration.

The same document requires Claude-account sign-in to complete through Anthropic’s own flow and prohibits third-party developers from collecting, storing or intermediating account credentials or session authentication values. The general SDK overview also requires prior approval for offering Claude-account login in a third-party product. OpenCode’s release establishes a new integration; it provides no basis for claiming Anthropic has opened subscription access to every external tool.

The merged change keeps models visible with older Claude Code and requests an update in the first chat. Tool and permission waits no longer trigger the five-minute idle timeout that could mark a conversation as user-cancelled.

OpenCode followed with guided setup in version 2.2.4, also dated October 30. Selecting Claude Agent leads users through installation, sign-in and connection verification before model selection. The desktop app adds recovery from a needs-sign-in state.