[BUG] /web-setup returns "Login failed" in v2.1.119 despite valid claude.ai auth and connected GitHub Integration

[brianfofficial]

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?

Summary

/web-setup consistently returns Login failed. Please visit https://claude.ai/code and login using the GitHub App even though every
prerequisite is satisfied. Cloud sessions spawned from the claude.ai web UI work correctly against the same repo, so the failure is isolated
to the CLI handshake itself.

Environment

• Claude Code: v2.1.119 (latest, claude update reports up to date)
• OS: macOS Darwin 25.5.0
• Shell: zsh
• Repo: private, on GitHub, clean working tree on main

Auth state (verified)

claude auth status:

{
  "loggedIn": true,
  "authMethod": "claude.ai",
  "apiProvider": "firstParty",                                                                                                                
  "subscriptionType": "max"
}                                                                                                                                             
         
gh auth status: logged in, scopes gist, read:org, repo, workflow.                                                                             
 
claude.ai → Settings → Connectors → GitHub Integration: shows connected (Disconnect button visible).                                          
         
GitHub App "Claude" installed on the account, scoped to the target repo (also tested with All repos).

### What Should Happen?

**What Should Happen?**                                                                                                                       
 
```markdown                                                                                                                                   
`/web-setup` either succeeds and links the local CLI to claude.ai cloud sessions, or returns a more specific error indicating which side of
the handshake failed (missing GitHub App slug, missing OAuth scope, expired token, etc.).    

### Error Messages/Logs

```shell
Login failed. Please visit https://claude.ai/code and login using the GitHub App
                                                                                                                                              
(Also: claude -p --debug=api "/web-setup" rejects with /web-setup isn't available in this environment, so the failing request body cannot be  
inspected from headless mode.)

Steps to Reproduce

Steps to Reproduce:

1. claude inside any git repo on macOS
2. Run /web-setup
3. Output: Login failed. Please visit https://claude.ai/code and login using the GitHub App

What I already tried

1. claude update — already on latest 2.1.119
2. gh auth status — logged in, repo + read:org + workflow scopes
3. claude auth status — claude.ai Max, firstParty provider, loggedIn: true
4. Visited https://claude.ai/code in browser — page loads, no install prompt appears
5. Toggled Claude GitHub App from "All repos" → single repo → "All repos"
6. Disconnected + reconnected the GitHub Integration in claude.ai → Settings → Connectors
7. Retried /web-setup after each change — identical error every time

Cloud sessions spawned from the claude.ai web UI on the same repo work correctly (pull, hooks, commit, push all succeed). Only the CLI
/web-setup handshake fails.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.119 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Warp

Additional Information

• Cloud sessions work fine when spawned from the claude.ai web UI directly. They pull the repo, run hooks, commit, and push successfully. Only
  the /web-setup CLI code path is broken.
• ~/.claude.json shows claudeAiMcpEverConnected: true and a populated oauthAccount block with billingType: stripe_subscription,
  subscriptionType: max, and a valid organizationUuid.
• Happy to share more debug output if there's a flag that surfaces the failing request body.

[github-actions]

Found 3 possible duplicate issues:

1. Remote agent GitHub connector: 're-authorize GitHub in settings' error has no resolution path in settings UI #48769
2. /ultrareview fails with 'GitHub repository access check failed' even though /schedule works on the same repo + account #53648
3. [Bug] /autofix-pr command not functional despite proper GitHub app installation #49855

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[brianfofficial]

#53574 is unrelated.

Likely related (same cloud-dispatch GitHub-access check, different commands):

• /ultrareview fails with 'GitHub repository access check failed' even though /schedule works on the same repo + account #53648 — /ultrareview returns GitHub repository access check failed despite the Claude GitHub App being installed and /schedule
  working on the same repo + account.
• [Bug] /autofix-pr command not functional despite proper GitHub app installation #49855 — /autofix-pr returns The Claude GitHub app must be installed on this repository first despite the App being installed. One
  commenter (@jlazarre95) found /autofix-pr reads the unsuffixed Claude Code-credentials Keychain entry instead of honoring
  CLAUDE_CONFIG_DIR.

In my case there's only one Claude profile (~/.claude/, no CLAUDE_CONFIG_DIR override), so the multi-profile angle doesn't apply — but the symptom shape (cloud-dispatch GitHub access check fails while every other auth surface reports connected) matches both issues. Worth investigating as one cluster.

[rpigab]

Same here, cannot get Claude Code Web to work with a cloud env setup. I've tried multiple auth flows, they all fail. I cannot remove the Github connection to try again the whole thing. I can do the claude cli /web-setup + gh cli handshake again but it won't work.

Edit: it works now, can't remember how I managed to get it to work but I switched between desktop and mobile and found a way which did work.

[johanna-maier]

I ran into the same issue and managed to fix it with point 2 from the debugging list below (the items on the list were also provided by Claude CLI).

1. Re-run /web-setup as-is. On 2.1.177 the regression is probably gone. If it works, stop here. (That didn't solve it, not a version issue.)
2. Refresh the claude.ai-side OAuth token. The "Login failed" message is about the claude.ai handshake, not gh. A stale firstParty token is the most common remaining cause. Run /login (sign out → back in with your claude.ai account), then /web-setup again. (That did the trick.)

Other suggestions, not tested:
3. Refresh the gh token, then retry: gh auth refresh -h github.com -s repo,read:org,gist,workflow
4. Use the browser path instead - this fully bypasses the broken CLI handshake. Per the official docs (https://code.claude.com/docs/en/claude-code-on-the-web), the GitHub App and /web-setup are two equivalent ways to grant the same access. Go to https://claude.ai/code, authorize the Claude GitHub App, and select your repo. /schedule and cloud sessions accept either form of access - you don't actually need /web-setup to succeed.
5. Check the admin toggle (you're org admin, so this applies to you). /web-setup can be disabled org-wide via Quick web setup at
https://claude.ai/admin-settings/claude-code — confirm it's enabled.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.