🕷️
SetupAI
🗾Stalecollected in 55m

Anthropic Limits Claude Subsk OAuth to Official Tools

Anthropic Limits Claude Subsk OAuth to Official Tools
PostLinkedIn
🗾Read original on ITmedia AI+ (日本)
#api-policy#oauth-restriction#terms-updateclaude

💡Anthropic just banned subsk OAuth for 3rd-party Claude—fix your integrations now!

⚡ 30-Second TL;DR

What Changed

Official docs updated to limit subsk OAuth to Anthropic's tools

Why It Matters

This change ends grey-area integrations, forcing developers to API keys which may increase costs and complexity for third-party apps relying on subsk tokens.

What To Do Next

Audit your Claude integrations and migrate to API keys for any third-party tool usage.

Who should care:Developers & AI Engineers

🧠 Deep Insight

Web-grounded analysis with 5 cited sources.

🔑 Enhanced Key Takeaways

  • •Anthropic began technically blocking third-party OAuth access starting January 9, 2026, with intensified measures by January 27, before the February 19 documentation update.[1][2]
  • •The policy enforces pre-existing Consumer Terms of Service from October 2025, including Section 3.7 prohibiting unauthorized automated access and credential sharing.[2][3]
  • •OpenCode removed Claude OAuth support via GitHub commit 973715f on February 19, 2026, in response to Anthropic's legal requests, redirecting users to OpenAI and others.[2][3][5]

🔮 Future ImplicationsAI analysis grounded in cited sources

Third-party developers will shift to Anthropic API keys, increasing pay-per-use costs over subsidized subscriptions.
Enforcement ends token arbitrage where subscriptions subsidized high-volume third-party usage at lower effective rates than API billing.[2][4]
OpenCode and similar tools will rely on multi-model routing with OpenAI OAuth to maintain functionality.
OpenCode's removal of Claude support and endorsement of OpenAI OAuth alternatives enable continued operation without Claude subscriptions.[3][4][5]

⏳ Timeline

2025-06
Anthropic applies similar playbook to restrict Windsurf third-party access
2025-10
Consumer ToS effective with Sections 2 and 3.7 prohibiting credential sharing and non-API automated access
2026-01
Mid-2025 practices like OpenCode spoofing headers continue until enforcement begins
2026-01-09
Technical blocks on third-party OAuth access implemented
2026-01-27
Intensified OAuth blocks affecting tools like OpenCode
2026-02-19
Documentation updated with explicit OAuth ban; OpenCode removes support
🗾Read original article on ITmedia AI+ (日本)
📰

Weekly AI Recap

Read this week's curated digest of top AI events →

👉Related Updates

Same topic

Explore #api-policy

Same product

More on claude

Same source

Latest from ITmedia AI+ (日本)

Figma's strategy to differentiate AI-generated product designs

Figma's strategy to differentiate AI-generated product designs

ITmedia AI+ (日本)•Jun 26

AI-curated news aggregator. All content rights belong to original publishers.
Original source: ITmedia AI+ (日本) ↗