[BUG] Option to log issue in GitHub from Claude Code can fail silently

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/68067
2. https://github.com/anthropics/claude-code/issues/66201
3. https://github.com/anthropics/claude-code/issues/30031

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

Your diagnosis (the locked-down GHE account being the default is what kills it) lines up with a much less painful workaround than logging out of GHE each time.
Why it fails silently: the "press Enter to log an issue on GitHub" step creates the issue through your active gh CLI authentication, not a fresh browser login. When your default/active gh account is the GitHub Enterprise one — which is restricted from contributing to repos outside its org — the create call to a public repo like this one is rejected (a 403 from the API), and that error gets swallowed instead of surfaced, so it just looks like nothing happened. That's exactly why it only worked the one time your regular github.com account was the only one logged in.
Repeatable workaround (no logging out of GHE): gh supports multiple accounts per host and lets you pick the active one. Switch the active account for github.com to your regular (non-GHE) account before logging feedback:

gh auth status          # see which accounts are connected and which is active
gh auth switch --hostname github.com --user <your-regular-github-username>

After that, the active github.com identity is your unrestricted account, so the issue-create succeeds without touching your GHE login at all. You can switch back with the same command. (If your regular account isn't connected yet, gh auth login --hostname github.com first.)
If it still fails after switching, run the underlying create directly to see the real error the UI is hiding — e.g. gh issue create --repo anthropics/claude-code --title test --body test — a 403 there confirms it's the account-permission path; a different error points elsewhere.
On the feature request — strongly agree, and the silent part is the worse half. Two things would fix this cleanly: (1) when more than one GitHub account is connected, prompt which one to use for issue logging (as you said); and (2) regardless of that, surface the API error instead of swallowing it — a one-line "couldn't create the issue: 403 (this account can't contribute to this repo)" would have saved you the whole investigation. A silent failure on a "press Enter to submit" action is the part that makes it feel broken rather than blocked.
(Not affiliated with Anthropic — the gh auth switch multi-account behavior is standard gh CLI; the rest is reasoned from your symptom that it only works when the GHE account is logged out.)

Good feedback @yurukusa, thank you. I connected my non-GHE account using gh auth login, and then made it the active account using gh auth switch. Even with it active, the Enter key fails to open an issue in GH. I then tried gh issue create using the command you shared, and that worked just fine. So my current situation is: logged in with two GH accounts, one GHE, but my non-GHE account is my active one, and Enter still fails to create issues in GitHub, even though gh issue create works just fine.

@KirkMunroSagent — thank you for running that so cleanly; the result is the useful part, and it means my earlier workaround was incomplete, so let me correct it.

Switching the active github.com account to your non-GHE one would have been enough if the "press Enter to log an issue" step simply shelled out to your active gh CLI. But you've now shown it doesn't:

• gh issue create --repo anthropics/claude-code ... → works (your non-GHE account is correctly active and unrestricted)
• /feedback → "press Enter to log an issue on GitHub" → still fails silently, with that same active account

Those two using the same active gh identity yet behaving differently is the key signal: the Enter-to-log action is not going through the same path as gh issue create. So this is not your account setup — you've already proven that's correct — it's Claude Code's own issue-logging integration still hitting a failing path (and still swallowing the error). I can confirm from my own environment that gh CLI/API issue-and-comment creation against this public repo succeeds fine with a standard github.com account, which lines up with your gh issue create result — the CLI layer is not the broken part.

I don't want to hand you an unverified fix, so I'll stop at what's actually established rather than guess at CC's internals. Meanwhile, since it's confirmed working, you can log the issue directly:

gh issue create --repo anthropics/claude-code --title "<title>" --body "<body>"

For the maintainers, the narrowed report: with a correct, unrestricted active github.com account (proven by gh issue create succeeding), the /feedback Enter-to-log-issue path still fails silently — so the fault is in that feature's own submission path, independent of the user's gh account, plus the swallowed error that hides it. Surfacing the underlying error (even one line) and/or reusing the same path as gh issue create would resolve both halves.

(Not affiliated with Anthropic.)