Skip to content

[Feature]: Anthropic OAuth Sign-In for Claude Pro / Max Subscribers #16090

@SiinXu

Description

@SiinXu

Background

Users who hold a Claude.ai Pro or Max subscription must currently obtain an Anthropic API key and pay API billing to use Anthropic models in Cherry Studio, even though their subscription already includes generous model usage. Anthropic's own Claude Code and several third-party clients (e.g., ChatWise) let subscribers sign in via OAuth and consume their subscription quota directly. Cherry Studio already ships OAuth flows for other providers (CherryIN, GitHub Copilot), but the Anthropic provider has no OAuth option — forcing already-subscribed users into duplicate pay-per-token billing.

Goal

Users with a Claude.ai subscription can sign in to the Anthropic provider via OAuth in Cherry Studio and use Claude models against their subscription quota — no API key required.

Spec

  • Anthropic provider settings expose an OAuth sign-in option alongside the existing API key field; either credential is sufficient to use the provider.
  • Choosing OAuth opens a browser to Anthropic's authorization page; after consent, Cherry Studio receives and stores the credential locally.
  • When OAuth is the active credential, all requests to Anthropic models (chat, assistant, agent) draw from the user's subscription with no separate API billing.
  • Credentials persist across restarts, are transparently refreshed when near expiry, and are revocable via a Sign Out action.
  • OAuth and API key can coexist on the same provider; the user toggles which is active; only the active credential is used per request.
  • Subscription-side errors (quota exhausted, plan downgraded, scope revoked) surface as clear, actionable messages in chat or provider settings — not as silent empty responses.

Verification

  • A user with a Claude Pro subscription signs in via OAuth, sends a chat to Claude Sonnet, gets a response, and observes no charge on the Anthropic API console for that turn.
  • A user with neither subscription nor API key completes OAuth, sends a chat — the first message returns a clear "subscription required / plan inactive" message rather than a silent empty response.
  • A user signs in via OAuth, restarts Cherry Studio, sends a message immediately — succeeds without re-authorizing.
  • User signs out from Anthropic provider settings — subsequent requests fail with "not signed in" until OAuth or API key is re-supplied.
  • User has both an OAuth session and an API key configured; toggles between them; each toggle takes effect on the next chat without restart.
  • Long idle past token TTL, then send a message — the request transparently succeeds via background refresh.

Related

#8863 #13248 #12843 #13864

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Planning

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions