OpenCode Third-Party Apps Extra Usage: $200 Credit Explained
OpenCode Third-Party Apps Now Draw From Your Extra Usage, Not Your Plan Limits
You launched OpenCode and saw a notification: "third-party apps now draw from your extra usage, not your plan limits. We've added a $200 credit to get you started. Claim it at claude.ai/settings/usage and keep going." This post explains exactly what changed, why OpenCode is classified as a third-party app, how to claim your $200 credit, and how to keep OpenCode running once the credit runs out.
What Is OpenCode?
OpenCode is an open source terminal-based AI coding agent. Unlike Claude Code (which is built by Anthropic), OpenCode is a community-built tool that connects to multiple LLM providers, including Anthropic's Claude, through OAuth or API keys. It runs in your terminal, reads your project files, writes code, runs commands, and handles multi-step coding workflows.
Because OpenCode authenticates with Claude through OAuth rather than being a first-party Anthropic product, it falls under the "third-party apps" billing category.
| Tool | Built by | Claude access method | Billing pool | |---|---|---|---| | claude.ai | Anthropic | Direct | Plan limits | | Claude Code | Anthropic | First-party | Plan limits (with extra usage for heavy use) | | OpenCode | Community (open source) | OAuth | Extra usage credits only | | Cursor | Anysphere | OAuth | Extra usage credits only | | Windsurf | Codeium | OAuth | Extra usage credits only | | Cline | Community (open source) | OAuth | Extra usage credits only |
Why the Billing Changed
Before early 2026, third-party apps like OpenCode shared the same usage pool as your Claude Pro or Team subscription. This meant a heavy OpenCode session could eat into your claude.ai chat limits, and vice versa.
Anthropic split these into two separate pools:
- Plan limits cover direct usage on claude.ai and the mobile app
- Extra usage credits cover all OAuth-connected third-party apps
The split is meant to prevent third-party apps from degrading your direct Claude experience. But it also means you need a positive extra usage balance for OpenCode to work at all.
How to Claim Your $200 Credit
The notification tells you to visit claude.ai/settings/usage. Here is the exact process:
- Open claude.ai/settings/usage in your browser
- Sign in with the same account that OpenCode uses for OAuth authentication
- Look for a banner about extra usage credits, or check the "Extra usage" section directly
- If prompted, click to claim the credit
If you already see a balance under "Extra usage," the credit has been applied automatically. No further action needed.
Tip
Make sure OpenCode authenticates with the same Claude account where you claimed the credit. If you use a personal account for claude.ai but a work account for OpenCode, the $200 credit will not carry over between them.
How Much Does OpenCode Actually Cost?
OpenCode's Claude usage is billed per token, just like any other OAuth-connected app. The cost depends heavily on which Claude model you select and how you use the tool.
| Usage pattern | Model | Estimated daily cost | $200 lasts | |---|---|---|---| | Quick code completions, short chats | Haiku 4.5 | $0.50 to $2/day | 3 to 12 months | | Regular coding sessions (2 to 4 hours) | Sonnet 4.6 | $3 to $8/day | 25 to 65 days | | Heavy multi-file refactoring | Opus 4.6 | $10 to $25/day | 8 to 20 days | | Long-running autonomous agents | Opus 4.6 | $30 to $60/day | 3 to 7 days |
OpenCode lets you switch models per session. The most cost-effective pattern is to use Haiku or Sonnet for routine work and only invoke Opus when you need deep reasoning across a large codebase.
Configuring OpenCode to Use the Right Account
OpenCode supports multiple authentication methods. For the extra usage credit to apply, you need OAuth authentication with your Claude account, not a raw API key.
# Check your current OpenCode auth configuration
opencode config get auth
# If using an API key, you're billed through Anthropic's API billing,
# NOT through extra usage credits. The $200 credit only applies to OAuth.
If OpenCode is configured with an Anthropic API key instead of OAuth, the $200 extra usage credit does not apply. API key usage is billed separately through console.anthropic.com. Make sure you are using OAuth login if you want the credit to cover your sessions.
What Happens When the $200 Runs Out
Once your extra usage balance drops to $0, OpenCode sessions that use Claude will fail. You will see errors like "you're out of extra usage" or "request rejected" when OpenCode tries to call the Claude API through OAuth.
Your options at that point:
Warning
The $200 credit is a one-time allocation, not a monthly refresh. Once it is gone, it does not come back unless your Enterprise plan specifies recurring credits.
Monitoring Your Balance
Check your remaining extra usage credit at any time:
# Open the usage settings page
open "https://claude.ai/settings/usage"
The page shows your current extra usage balance, spending history by app, and auto-refill settings. OpenCode sessions will appear under the third-party apps section of the spending breakdown.
For teams and organizations, workspace admins can see aggregate usage across all members and set per-user spending limits at console.anthropic.com.
OpenCode vs. Other Third-Party Coding Agents
OpenCode is not the only tool affected by this billing change. Here is how it compares to alternatives in terms of the extra usage credit:
| Feature | OpenCode | Claude Code | Cursor | Windsurf | |---|---|---|---|---| | Open source | Yes | No | No | No | | Multi-provider (not just Claude) | Yes | No | Yes | Yes | | Uses extra usage credits for Claude | Yes (OAuth) | Partial (heavy use) | Yes | Yes | | Terminal-native | Yes | Yes | No (IDE) | No (IDE) | | Model switching | Per session | Per session | Per chat | Per chat | | Free tier available | Yes (bring your own key) | With Pro plan | Free tier | Free tier |
OpenCode's advantage is flexibility. If the $200 credit runs out and you do not want to add more, you can switch OpenCode to a different provider entirely without changing your workflow. Claude Code, by contrast, only works with Claude.
Common Pitfalls
- Mixing up API key billing and OAuth billing: If you configured OpenCode with an API key, the $200 extra usage credit does not apply. API calls are billed separately through console.anthropic.com. Switch to OAuth to use the credit.
- Wrong account: OpenCode must authenticate with the same Claude account that received the $200 credit. Check which account you are logged in with at claude.ai/settings before troubleshooting missing credits.
- Assuming the credit is monthly: The $200 is a one-time starter amount. It depletes with use and does not automatically replenish.
- Not tracking per-session cost: OpenCode does not always show cost estimates inline. Check claude.ai/settings/usage after heavy sessions to understand your burn rate.
- Ignoring model selection: Running Opus for every task when Sonnet or Haiku would suffice wastes credits quickly. Be intentional about which model you select for each session.
Quick Checklist
If you just saw this notification in OpenCode, here is your action plan:
- Go to claude.ai/settings/usage and claim your $200 credit if prompted
- Confirm OpenCode is using OAuth authentication (not an API key) with the correct account
- Choose cost-appropriate models for your work (Haiku for quick tasks, Opus for complex reasoning)
- Bookmark the usage settings page and check it weekly
- Set up auto-refill if you depend on OpenCode daily and cannot afford downtime
Wrapping Up
The "third-party apps now draw from your extra usage" message in OpenCode means Anthropic has separated billing for OAuth-connected tools into its own credit pool. Your $200 starter credit covers OpenCode sessions with Claude, but it depletes with use and does not auto-renew. Claim it at claude.ai/settings/usage, pick cost-effective models, and monitor your balance to avoid surprise interruptions.
Fazm is an open source macOS AI agent that watches how you work and suggests automations. Open source on GitHub.