OpenCode v2.2.3 introduces a built-in Claude Agent provider that uses a Claude Code login and its available models. For someone already working with Claude Code, this offers another interface to the existing account access.
The documented connection sequence
- Make sure Claude Code is installed.
- Run
claude auth loginand sign in to your own account. - Open
/connectin OpenCode and choose Claude Agent.
The October 30 release notes give that sequence. If the Claude executable is in a custom location, OPENCODE_CLAUDE_PATH can override the path. Establish whether discovery is actually failing before adding a custom setting.
Check the connection before assigning changes
Confirm the selected provider and the models offered. A small question about the project, requiring no file changes, is a useful proposed first test. It keeps account access separate from permission to modify the workspace.
What the integration does not add to the account
The provider connects to existing Claude Code access; its addition is not a second subscription or a separate allowance. Model availability and usage remain associated with the connected account. The same release also includes rendering improvements for long desktop sessions and fixes for several session and side-panel issues.
Oliver’s assessment
First, isolate the change. Login, provider selection and a small read request are separate checks. Keeping them separate makes a failure easier to locate before a larger coding assignment begins. The practical gain is a clearer connection path, rather than a reason to change several unrelated settings at once.
