Feature Request: API access tier for Max subscribers (bring your own harness)

Open 💬 2 comments Opened Jan 22, 2026 by newsbubbles

Summary

Allow Claude Max subscribers to use their subscription quota with custom tooling/harnesses, not just Claude Code and claude.ai.

The Problem

Currently, Max subscribers ($200/month) can only access their quota through Anthropic's interfaces (Claude Code, claude.ai). Using the API directly with Opus 4.5 costs roughly $100/day for heavy usage - approximately 15x more expensive.

This creates a frustrating situation for advanced users who build custom agentic systems:

  • Forced into constrained interfaces: Builders with sophisticated custom harnesses must abandon their tooling to use the affordable tier
  • Economic lock-in: The choice is "use our interface" or "pay enterprise rates"
  • Lost community input: Advanced builders who understand agentic UX deeply are priced out of experimenting with their own approaches

Use Case

I'm an independent developer who builds custom agentic harnesses. My tooling is tailored to my workflow and in many ways exceeds what Claude Code offers for my specific needs. But I can't afford $3000/month in API costs, so I'm forced to use Claude Code and lose the benefits of my own system.

Proposal

Offer some mechanism for Max subscribers to use their quota with custom tooling:

  • An API access tier included with Max
  • A token bucket that can be spent via API
  • Some other "bring your own harness" option

Why This Matters

Anthropic is effectively locking out the builders who could contribute the most valuable perspectives on agentic UX and tooling. These users understand the space deeply and could provide real feedback - but they're pushed toward either accepting constraints or walking away.

This isn't about wanting something for free. It's about wanting to use what we're paying for in the way that's most productive for us.

---

Filed via Claude Code, ironically.

View original on GitHub ↗

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