[BUG] "Import issue" dialog returns zero results (even searching by exact issue number) for a repo that was just transferred to a new GitHub org, despite the connected account having verified read/write access to all those issues."

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:
After transferring a GitHub repository from a personal account to an organization, Claude Code Desktop's "Import issue" feature (Code tab → Import issue) returns no results — both for the default "issues you're involved with" list and for explicit search by issue number — despite the connected GitHub account having full, verified access to the repo and those issues.

Environment:
Claude Code Desktop (macOS)
Repo: transferred from a personal account to an organization (GitHub org transfer)
Local git remote and gh CLI both correctly resolve to the new org/repo path post-transfer

Actual behavior:
Search by exact issue number returns nothing.

Diagnostics already performed (ruling out GitHub-side causes):

gh auth status — authenticated, scopes include repo, read:org.
gh repo view <org>/<repo> — resolves correctly to the new org.
gh issue list --repo <org>/<repo> --assignee <user> and --author <user> — both return multiple open issues confirming the connected GitHub account is in fact the author/assignee.
Disconnected and fully reconnected the GitHub integration in Claude Code Desktop — issue persisted.
Confirmed no GitHub App installation exists/needed; confirmed org's third-party OAuth access restriction is not the blocker (tested temporarily unrestricting — no change).
Suspected cause:
Claude Code's backend appears to index "your" GitHub issues keyed to the original repo path/owner, and this index does not get refreshed or re-resolved when the underlying repo is transferred to a new owner — even though the repo's id is unchanged on GitHub's side and the GitHub API itself reflects the new owner immediately.

Workaround:
None within the Import issue dialog. Issues can still be fetched via the gh CLI through normal chat in Claude Code (e.g. asking it to run gh issue view <number> --repo <org>/<repo>).

What Should Happen?

Claude Code should be able to access issues after transferring ownership of a repo

Error Messages/Logs

Steps to Reproduce

Own a repo on a personal GitHub account, with open issues you've authored/are assigned to.
Transfer the repo to a GitHub organization (Settings → Danger Zone → Transfer ownership).
In Claude Code Desktop, open the project linked to that repo's local clone and click Import issue.
Observe the dialog shows "No issues you're involved with here."
Type an exact issue number you are the author/assignee of into the search box.
Expected behavior:
Searching by exact issue number should return that issue regardless of any "involved with" quick-list staleness, since it's a direct lookup.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.150 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_