API Error 403 (permission_error) — page 3
The credential is valid but not allowed to use this model, org, or endpoint.
258 issues · 32 open · 226 resolved (88%) · first seen Feb 25, 2025
First response · account
What to do now
Most likely: The credential is valid but lacks access to the requested model, organization or policy scope.
- Confirm model availability and organization membership for the active account.
- Check enterprise policy or gateway allow-lists before rotating credentials.
- Capture the permission error body when asking an administrator for access.
These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.
Is this getting better or worse?
This class of problem is converging. 47 new reports in the last 90 days vs 63 in the 90 before — -25%. The open backlog peaked at 48 in 2026-07 and sits at 32 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
116 of these reports name the Claude Code build they were running, spanning 71 releases. Heaviest reporters:
- Claude Code v2.1.114
- Claude Code v2.1.220
- Claude Code v2.1.81
- Claude Code v2.1.211
- Claude Code v2.1.92
- Claude Code v2.1.195
- Claude Code v2.1.161
- Claude Code v2.1.12
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 29 days across 226 closures. Of the 226 closures with a recorded reason, 27% were closed as completed and 164 as not-planned or duplicate. The most recent completed fix landed in 2026-10.
Workarounds reported by the community
56 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG]Cowork network egress allowlist not working - custom domains blocked with 403 blocked-by-allowlist
- …3. Proxy scope - Cowork might use a separate proxy instance Workaround: Run a local proxy bypass: export HTTP PROXY= Similar issues in OpenClaw's sandbox - config and enforcement must be synchronized.
Found in the thread of #30112 · still open - [Bug] Anthropic API Error: Usage credits required for 1M context window with opus-plan model
- …sn't work, and just stops working at 1M Context. A feasible workaround would be to periodically use the /compact command manually.
Found in the thread of #61869 · resolved - [BUG] Claude Code on the Web .NET SDK binary downloads blocked by proxy even with "All domains" network access enabled
- …SL -o /tmp/install.sh Returns: valid 1888-line shell script Workaround None currently. Users must: Have Claude write code Pull and compile locally Report errors back to Claude Repeat until code compiles This significantl…
Found in the description of #11897 · still open - [BUG] Allow network egress - All domains' setting not reflected in session proxy JWT
- …o this is not a tool-layer issue and there is no in-sandbox workaround. For completeness, the form: The denial comes from an upstream gateway : Direct CONNECT against the local proxy: So the local proxy relays and the ga…
Found in the thread of #34690 · still open - [Bug] Anthropic API Error: OAuth token missing user:profile scope
- …completed successfully but error persists - Still getting: Workaround to try: Based on @gerrywastaken's comment, will try and logging back in instead of . Note: appears insufficient to fix this - requires full logout/lo…
Found in the thread of #11985 · still open
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 201–258
Ranked by community engagement (reactions weighted over comments).
- C:/Program Files/Git/stickers returns 403 Forbidden in Japan
- [BUG] oauth_org_not_allowed on personal Pro account — subscription access blocked without any changes
- Your organization has disabled Claude subscription access for Claude Code · Use an Anthropic API key instead, or ask your admin to enable access
- /stickers command returns 403 Forbidden on the linked sticker page
- I'm not able to generate a GitHub issue title from "resti" as it doesn't contain enough information about the bug or feature request. Could you please provide: - A description of the problem or feature request - Any error messages encountered - Steps to r
- [BUG] Please run /login · API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}} /login Login OAuth error: Request failed with status code 403
- [DOCS] Troubleshooting docs omit server-error guidance and usage-vs-rate-limit distinction
- [BUG] Cowork 403 "Request not allowed" on Pro plan
- [Billing Bug] account_session_invalid on billing page – subscription paused 3 weeks
- [BUG] Claude Desktop - Google OAuth login loop, claude:// callback not delivered to running instance (Windows Store)
- [Bug] Unable to determine issue from empty bug report
- [FEATURE] ExpiredTokenException (403) from AWS Bedrock should fast-fail instead of retrying
- Settings usage page fails with OAuth scope error: permission_error user:profile
- [BUG] Error checking /usage
- [BUG] Claude Code Web: Proxy blocks CONNECT tunnel to npm.pkg.github.com (403), preventing yarn install of private packages
- Security: Claude Code exposed Figma API token in conversation by running 'claude mcp list'
- [Bug] /usage command fails with insufficient OAuth scope (user:profile required)
- [Bug] Anthropic API Error: OAuth token missing user:profile scope for /status usage data
- [BUG] <meta> tag in CLAUDE.md file causes 403 Forbidden error when using LiteLLM proxy
- [BUG] API Error: 403 when I successfully logged in using claude-code
- [BUG] Bedrock + `ANTHROPIC_MODEL` / inference profiles not being used for 3.5 Haiku requests
- [GitHub integration] 403 Forbidden when pushing to News92-tg/skyschool
- Remote Control: desktop app sessions always fail with HTTP 403 (CLI sessions connect fine)
- Cowork cloud egress: WebSocket (wss) hosts refused while ordinary HTTPS to the same service is allowed
- login Session bug
- [BUG] "Vercel MCP integration returns 403 Forbidden on deploy_to_vercel for existing/manually-created projects, works only once on brand-new project names."
- [BUG] MCP client shows "token expired" for a 403 insufficient_scope response
- Cowork sandbox network allowlist not affected by sandbox.enabled toggle in settings
- [BUG] Microsoft 365 connector never requests Calendars.ReadWrite / MailboxSettings.ReadWrite — calendar write tools fail with 403 even when connected
- [BUG] Desktop app: elevated-auth re-login navigates to /new and destroys the prompt being typed
- [FEATURE] Team seat usage is available in `/usage` but inaccessible to local integrations
- [BUG] Agent unilaterally created/rotated a production API credential without asking
- [BUG] Claude Desktop on Windows: /compact fails with 403 "Request not allowed" and usage increases substantially despite failed compaction
- [BUG] Cloud routine GitHub App onboarding fails to install on personal account when identity is a member of an org with an existing installation
- [Bug] Claude Fable 5 blocks legitimate first-party security review with active CVP approval
- [BUG] Desktop app hangs when Bedrock model unavailable (403), cannot switch model
- [BUG] Desktop app sandbox network proxy ignores sandbox.network.allowedDomains from project .claude/settings.json, while CLI honors it correctly
- [BUG] Cowork/Code fail with 403 "Invalid authorization" for 10+ days — Chat works fine
- [BUG] Routine repository picker shows "no repository found" — GitHub connector authorized but GitHub App never installed
- [BUG] Git proxy returns 403 Forbidden
- [BUG] HTTP 403 (no WWW-Authenticate) is misclassified as "requires OAuth"; stale flag is keyed by server name and not cleared by mcp remove
- [Bug] Claude generates incomplete responses and avoids task completion
- [BUG] ERR_BAD_REQUEST on startup persists across MSIX and npm installs — confirmed not network/proxy/TLS/DNS related
- Cloud routine environments silently changed AWS_* env handling twice (stripped, then platform-injected), breaking production workloads
- I need more specific information about the error you're experiencing to generate an accurate issue title. Could you please provide: 1. The error message you're receiving 2. What MCP server you're trying to integrate 3. What steps you took to set it up 4.
- Desktop app DCR uses client_name "Claude Desktop (…)" which Figma's MCP register endpoint rejects with 403 — CLI works because it sends "Claude Code"
- [BUG] v2.1.96: Claude Code GitHub Action fails with AWS authentication
- API Error: 403 {"error":{"type":"forbidden","message":"Reque...
- [BUG] Cloud session network access settings are silently ignored for GitHub
- [BUG] claude.ai connector: transient 403 (mcp_request_blocked) is cached as needs-auth; later sessions skip the connector and re-authorizing can't clear it
- Cloud session sandbox proxy returns 403 for the Browserbase API, breaking skills that depend on it
- [BUG] "All domains" egress setting not applied to Cowork cloud sessions
- [BUG] Cowork sandbox egress proxy blocks all custom domains regardless of org allowlist config — breaks access to own infrastructure
- Cloud routines/sessions cannot access private repos on a personal GitHub account (403 permission_error)
- [Bug] Anthropic API Error: Server Rate Limiting During Request
- [BUG] Claude in Chrome side panel (Cowork mode): GET /api/bootstrap returns 403 from extension context while identical authenticated request returns 200 from a claude.ai tab — endless sign-in loop
- [Bug] Anthropic API Error: Server Rate Limiting - Request Throttling
- [Bug] Claude Sonnet refuses to generate network monitoring code