[BUG] Cloud routine GitHub App onboarding fails to install on personal account when identity is a member of an org with an existing installation

Preflight Checklist

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

What's Wrong?

Summary
The GitHub App onboarding flow for Claude Code cloud routines (claude.ai/code/onboarding?magic=github-app-setup) never completes installation on a user's personal GitHub account when that same identity is already a (non-admin) member of an organization where the app happens to be installed. No consent/installation screen is ever shown, and the routine creation API remains blocked.

Environment

• claude.ai Claude Code cloud routines (RemoteTrigger / scheduled agents)
• Single GitHub identity, member (non-admin) of an org where the Claude GitHub App is already installed by someone else

Hypothesis
The onboarding flow treats "this identity has some visible Claude App installation" (via org membership) as sufficient to consider GitHub connected, and never prompts a fresh, personal-account-scoped installation — even though the existing installation grants no access to the user's own repos and the user has no admin rights to modify it.

Impact
Unable to create any cloud routine referencing a personal-account repository. Currently working around this with a manual Google Calendar reminder instead of the intended scheduled agent.

What Should Happen?

Expected behavior
Visiting the onboarding link while authenticated to GitHub should walk me through GitHub's App installation/consent flow and let me install the app on my own personal account (which I own and administer), independent of any org-level installation elsewhere.

Actual behavior
Clicking the link redirects to claude.ai/code with no GitHub consent/installation screen at any point, and no installation is created — confirmed repeatedly.

Error Messages/Logs

Steps to Reproduce

Repro steps

1. Be a member (non-admin) of a GitHub org where the Claude GitHub App is already installed.
2. Have a separate private repo under your own personal account (same GitHub identity) that a cloud routine needs access to.
3. Attempt to create a routine referencing that repo via the API → fails with 401 authentication_error: "Connect your GitHub account before saving a routine that uses a GitHub repository."
4. Visit https://claude.ai/code/onboarding?magic=github-app-setup while logged into GitHub as that identity → redirected to claude.ai/code, no consent screen, nothing installed.
5. Retry routine creation → error changes to 403 permission_error: "You don't have access to a repository this routine uses." This suggests claude.ai now considers GitHub "connected" (likely via the pre-existing org-level installation), but that installation has no access to the personal-account repo.
6. Check github.com/settings/installations on the personal account → "No installed GitHub Apps." Zero entries, despite repeated attempts at step 4.
7. Searched GitHub Marketplace for "Claude" → app is not listed (only unrelated Actions found), confirming it's an unlisted/private GitHub App reachable only via claude.ai's own redirect — no independent GitHub-side path to trigger installation exists.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.223

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_