Skip to content
BSWEN
Blog

Can You Use Claude Code with Third-Party Harnesses? Terms Explained

Cowrie
Cowrie
Dev @ Bswen

Purpose

I researched whether Claude subscription accounts (Free, Pro, Max) can be used with third-party coding tools like OpenCode, Cursor, or custom harnesses. The short answer: No. OAuth tokens from subscription accounts only work with official Claude tools. For third-party integration, you need API keys.

The Core Confusion

I kept seeing developers ask the same question:

Reddit question
"How are you using Claude Code with [third-party tool]?
 Anthropic specifically prohibited using another harness than their own"

This confusion stems from the Agent SDK release. Developers assumed they could use the SDK with their existing Claude Pro or Max subscriptions. The documentation wasn’t clear, and community discussions added to the uncertainty.

What Anthropic Actually Prohibits

According to Anthropic’s legal compliance documentation (updated February 2026):

Official policy statement
"Using OAuth tokens obtained through Claude Free, Pro, or Max accounts
in any other product, tool, or service -- including the Agent SDK --
is not permitted and constitutes a violation of the Consumer Terms of Service."

Here’s the key distinction:

Authentication methods comparison
┌─────────────────────────────────────────────────────────────────┐
│                    Authentication Methods                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  OAuth Tokens (Subscription)          API Keys (Pay-as-you-go)  │
│  ─────────────────────────────        ─────────────────────────  │
│  - Claude Free/Pro/Max accounts       - Consoleconsole.anthropic.com│
│  - ONLY works with:                   - Works with:              │
│    * Claude Code CLI                    * Claude Code CLI        │
│    * Claude.ai web interface            * Third-party tools      │
│  - BLOCKED from:                         * Custom harnesses      │
│    * Third-party harnesses               * Agent SDK             │
│    * Agent SDK                           * Any API integration   │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Why This Policy Exists

I found three reasons from The Register’s coverage (February 2026):

1. Revenue model protection

Claude subscriptions offer subsidized token rates compared to API pricing. Using subscription accounts with third-party tools would create arbitrage opportunities.

2. Support and debugging challenges

Third-party harnesses generate unusual traffic patterns without the telemetry that Claude Code provides. This makes it hard for Anthropic to help debug issues.

3. Terms existed since 2024

Section 3.7 of Consumer Terms has prohibited automated access “except when you are accessing our Services via an Anthropic API Key” since at least February 2024. The enforcement is what changed, not the rule.

Enforcement Timeline

Policy enforcement history
2024-02  Consumer Terms Section 3.7 published (no automated access rule)


2026-01  Anthropic begins technical enforcement
         - Blocks third-party tools from spoofing Claude Code harness
         - Thariq Shihipar comments on X about SDK usage


2026-02  Legal terms updated for clarity
         - Explicit Agent SDK prohibition added
         - OpenCode removes Claude Pro/Max support
         - Cites "anthropic legal requests"

The Agent SDK Confusion Explained

The Agent SDK documentation created confusion because:

  1. It provides tools for building custom AI agents
  2. Developers assumed they could use it with Claude subscriptions
  3. The February 2026 clarification made it explicit: Agent SDK requires API keys

Thariq Shihipar’s comment about “experimenting with SDK in individual projects” refers to using the SDK with proper API authentication, not subscription accounts.

What You Can Actually Do

Option 1: Use Claude Code Natively

If you have Claude Pro or Max, this is your best value:

Native Claude Code usage
# Install Claude Code CLI
npm install -g @anthropic-ai/claude-code


# Login with your subscription account
claude-code login


# Use normally - fully compliant
claude-code

Pros:

  • Best value for subscription holders
  • Full agentic coding features
  • Proper telemetry for support
  • No additional API costs

Cons:

  • Must use official Claude tools only

Option 2: Use API Keys with Third-Party Tools

This is the compliant way to use Cursor, OpenCode, or custom harnesses:

API key setup for third-party tools
# Get API key from console.anthropic.com
export ANTHROPIC_API_KEY="sk-ant-api03-..."


# Use with any third-party tool
cursor --provider anthropic --api-key $ANTHROPIC_API_KEY

Pros:

  • Full flexibility in tool choice
  • Compliant with terms of service
  • Works with Agent SDK

Cons:

  • Pay-as-you-go pricing (no subscription discount)
  • Costs can scale quickly

Option 3: Hybrid Approach

Cost optimization strategy
┌─────────────────────────────────────────────────────────────┐
│                     HYBRID WORKFLOW                          │
├─────────────────────────────────────────────────────────────┤
│                                                              │
│  Heavy coding sessions ──────► Claude Code + Subscription   │
│  (best value per token)                                      │
│                                                              │
│  Specific integrations ──────► API Keys + Third-party       │
│  (when you need other tools)                                 │
│                                                              │
│  Quick questions ────────────► Claude.ai web interface      │
│  (included with subscription)                                │
│                                                              │
└─────────────────────────────────────────────────────────────┘

Common Mistakes I’ve Seen

Mistake 1: Confusing OAuth tokens with API keys

These are fundamentally different authentication methods with different permissions. You cannot “convert” one to the other.

Mistake 2: Thinking the rule is new

This has been in terms since 2024. Only enforcement changed in 2026.

Mistake 3: Expecting exceptions for “personal projects”

The terms don’t distinguish between personal and commercial use. Any third-party harness usage violates the subscription terms.

Mistake 4: Risking account termination

Anthropic has begun actively enforcing this policy. Violations risk losing your subscription account.

Summary

I researched the third-party harness question thoroughly. The answer is clear: Claude subscription OAuth tokens only work with official Claude tools. For third-party integration, always use API keys. The policy isn’t new, but enforcement is now active. Choose your authentication method based on your use case, not on hoped-for loopholes.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: