Feature Request: Allow OAuth/subscription tokens with Agent SDK for personal development use

Resolved 💬 4 comments Opened Apr 1, 2026 by coobeeyon Closed May 20, 2026

Summary

Power users on the Max plan ($200/mo) want to customize their Claude Code experience - building personal tooling, custom agents, and modified workflows - but face a stark choice:

  • Stay on the subscription: Powerful but locked to the official client
  • Use the API: Full freedom but ~50x the cost

Proposal

Allow individual subscribers to use their subscription credentials with the Agent SDK (or similar) for personal software development, under a simple policy:

  • Software development use only - not resale, not powering a product
  • By the individual licensee only - one person, one token, no sharing

Why this makes sense for Anthropic

  • The infrastructure for per-user rate limiting and anomaly detection already exists
  • Loss of entire Claude ecosystem access is a credible enforcement deterrent - most users will self-police
  • Opens a legitimate path for customization, reducing incentive for gray-market workarounds
  • Turns community energy into ecosystem advantage (the VS Code model)

Context

The recent source code leak has spawned multiple open-source reimplementations. Rather than playing enforcement whack-a-mole, blessing personal-use customization with reasonable guardrails would give Anthropic more control, not less.

---

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗