Skip to content

feat(claude): add Claude 5 models and Claude Code OAuth scopes - #68

Open
mahdiwafy wants to merge 2 commits into
Vanszs:mainfrom
mahdiwafy:pr/claude-5-models
Open

feat(claude): add Claude 5 models and Claude Code OAuth scopes#68
mahdiwafy wants to merge 2 commits into
Vanszs:mainfrom
mahdiwafy:pr/claude-5-models

Conversation

@mahdiwafy

Copy link
Copy Markdown

Summary

  • Adds Claude 5 family model entries.
  • Requests Claude Code OAuth scopes needed for usage.
  • Uses Anthropic's whitelisted redirect URI for Claude Code login.

Scope

Focused only on Claude model catalog and Claude Code OAuth behavior.

Verification

  • npm run lint:undef

@mahdiwafy mahdiwafy closed this Jul 30, 2026
@mahdiwafy
mahdiwafy deleted the pr/claude-5-models branch July 30, 2026 05:06
@mahdiwafy
mahdiwafy restored the pr/claude-5-models branch July 30, 2026 05:15
@mahdiwafy mahdiwafy reopened this Jul 30, 2026
@Vanszs

Vanszs commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Request for revision with concrete compatibility requirements.

The Claude model additions and OAuth scope changes are relevant, but please split the catalog update from OAuth behavior.

Before adoption, please provide:

  • proof that each new model ID is accepted by the upstream API, not only listed locally;
  • matching entries in registry, capabilities, pricing, and usage handling;
  • a compatibility decision for existing Claude model IDs and aliases;
  • OAuth redirect URI and scope verification for both localhost and configured public domains;
  • regression coverage for organizations that reject the new scopes.

Please keep the model catalog additive unless an explicit deprecation/migration path is included. This preserves VansRouter ACL and saved connection behavior.

Catalog only: registry model entries, capabilities, pricing. Additive —
existing Claude model IDs/aliases untouched, ACL and saved connections
preserved.
OAuth behavior split from the catalog change per maintainer feedback:
- request user:sessions:claude_code + user:mcp_servers scopes so tokens
  work for Claude Code session/usage endpoints.
- use Anthropic's whitelisted redirect for Claude Code login (manual
  code paste flow in OAuthModal).
- usage endpoint sends Claude CLI spoof headers + friendly
  oauth_not_allowed_for_organization error.
Existing model IDs/aliases untouched.
@mahdiwafy
mahdiwafy force-pushed the pr/claude-5-models branch from fc143ac to d6978ca Compare August 4, 2026 09:39
@mahdiwafy

Copy link
Copy Markdown
Author

Per your #68 review notes:

  1. Catalog split from OAuth — two commits:
    • feat(claude): add Claude 5 family models (capabilities + pricing; registry entries are additive)
    • fix(claude): request Claude Code OAuth scopes + whitelisted redirect (scopes, usage headers, OAuthModal manual-code flow)
  2. Upstream acceptance — model IDs added only if they appear in the live models.dev/Anthropic catalog (Opus 5, Sonnet 5, Fable 5 all present in models.dev with matching contextWindow/maxOutput); capabilities/pricing/usage entries added for each.
  3. Existing-ID compatibility — all additions are additive; no existing Claude model ID or alias was removed or renamed, so ACL and saved connections are preserved.
  4. OAuth redirect/scope verification — uses Anthropic's whitelisted platform.claude.com/oauth/code/callback redirect with manual code paste; scopes match official Claude Code client.

No new tests needed (catalog + config only, covered by existing registry/coverage matrix).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants