claude-code - 💡(How to fix) Fix Session list PR status chip always renders greyed out despite gh + backend reporting correct state

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…

Code Example

$ gh pr view <N> --repo <org>/<repo> --json number,state,title
   {"number":<N>,"state":"OPEN","title":"..."}

---

{ "title": "...", "prNumber": <N>, "prState": "OPEN", ... }
RAW_BUFFERClick to expand / collapse

What happened

In the Claude Code desktop app, each session that has an associated pull request shows a PR status chip in the session list. This chip is always rendered greyed out (as if the state were unknown/pending), regardless of the PR's actual state on GitHub.

I verified that the underlying data is correct and available at every layer except the rendered chip:

  1. gh CLI resolves state correctly:

    $ gh pr view <N> --repo <org>/<repo> --json number,state,title
    {"number":<N>,"state":"OPEN","title":"..."}
  2. The session backend already knows the state — the session metadata returns the correct prState:

    { "title": "...", "prNumber": <N>, "prState": "OPEN", ... }
  3. But the UI chip is still grey for that same session.

So both the gh data source and the session backend report OPEN, yet the chip never reflects it. This looks like a rendering / state-mapping bug in the desktop app rather than a gh auth or network problem.

Secondary observation

Of the PR-related sessions in the list, only a couple had a prNumber associated at all; the rest had no PR linkage. For those the grey chip may be "correct" (no PR linked), but the association seems to be missed for most sessions that did create/work on a PR.

Impact

  • PR state is never visible at a glance in the session list.
  • "Auto-archive after PR merge or close" appears to never fire (it relies on the same state signal), so archiving must be done manually.

Steps to reproduce

  1. Have a session with an associated open PR.
  2. Confirm gh pr view <n> returns OPEN.
  3. Observe the session-list PR chip — it stays grey.

Environment

  • Claude for Windows (desktop app): 1.9659.2 (390d6c)
  • Claude Code engine: 2.1.90
  • gh CLI: 2.88.1 (authenticated, scopes include repo)
  • OS: Windows 11 (10.0.26200.8390)

Expected

The PR chip should reflect the resolved PR state (open / merged / closed), matching what gh and the session backend already report.


🤖 Reported with Claude Code

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

claude-code - 💡(How to fix) Fix Session list PR status chip always renders greyed out despite gh + backend reporting correct state