claude-code - 💡(How to fix) Fix [BUG] 403 "Request not allowed" when creating new Cowork chat (existing chats work fine) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47775Fetched 2026-04-15 06:42:43
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1unlabeled ×1

Error Message

Failed to authenticate. API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}

Code Example

Failed to authenticate. API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Creating a new Cowork chat in the Claude Code desktop app (macOS) immediately fails with a 403 error: "Request not allowed". This happens every time a new session is started. Existing/older Cowork chats open and work fine — only new ones fail.

When trying to start a new Cowork chat in the Claude Code desktop app (macOS), I get the following error:

Failed to authenticate. API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}

Existing/old Cowork chats continue to work normally. Only creating new sessions fails.

Steps to reproduce

  1. Open Claude Code desktop app (macOS)
  2. Go to the Cowork tab
  3. Try to start a new Cowork chat
  4. Error appears immediately

What Should Happen?

A new Cowork session should be created successfully.

What I tried

  • Updated Claude Code CLI to 2.1.105
  • Logged out of all devices and logged back in
  • Issue persists after re-authentication

Environment

  • OS: macOS Version 15.7.4
  • Claude desktop app
  • Account: Claude Pro

Error Messages/Logs

Failed to authenticate. API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}

Steps to Reproduce

  1. Open Claude Code desktop app (macOS)
  2. Navigate to the Cowork tab
  3. Click to start a new Cowork chat
  4. Error appears immediately: "Failed to authenticate. API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}"

Note: Existing Cowork chats (created previously) open and work fine.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.105 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely related to authentication or permission issues with the Claude Code desktop app on macOS, resulting in a 403 error when trying to create a new Cowork chat.

Guidance

  • Verify that the authentication tokens or credentials are valid and not expired, as the error message suggests an authentication issue.
  • Check the API documentation for any changes in authentication requirements or permissions for creating new Cowork chats.
  • Try clearing the app's cache and stored credentials to ensure a fresh authentication attempt.
  • If the issue persists, investigate potential differences in permissions or settings between existing and new Cowork chats.

Example

No code snippet is provided as the issue seems to be related to authentication and permissions rather than code-specific errors.

Notes

The issue may be related to a regression in the Claude Code version 2.1.105, as the user mentions it worked in a previous version. However, without more information on the previous working version, it's difficult to pinpoint the exact cause.

Recommendation

Apply workaround: Try clearing the app's cache and stored credentials to ensure a fresh authentication attempt, as this may resolve the issue temporarily until a more permanent fix is found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING