anthropics / anthropics/claude-code
[BUG] PR chip stays in the bar after the PR is closed or merged, with no way to dismiss it
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 147k
- Forks
- 24k
- PR merge metrics
- PR metrics pending
Description
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?
Claude Code desktop app, Windows 11.
When a session is bound to a pull request, the PR chip stays in the bar after
that PR is closed. There is no × or any other control I can click to
clear it unlike a merged or open PR, so the session keeps showing a dead PR icon beside chat name. In my case the chip sat on a PR that had been closed as superseded and
went on showing "conflicting", which reads as an open problem on work that no
longer exists.
The agent can clear it, since it has an unbind tool. I cannot, and that is the gap: it is my UI and I have no control over what it shows.
What Should Happen?
Expected: the chip clears itself when the PR closes, or it exposes a
dismiss control I can use.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce
- Open a session in a repo with a GitHub remote.
- Ask Claude to open a pull request. It runs gh pr create and the app binds
that PR to the session automatically, showing a chip in the PR bar. I never
asked for it to be tracked, so I had no reason to expect I would have to
untrack it. - Close that PR, either with gh pr close or from GitHub. In my case Claude
closed it because a replacement PR superseded it. - Look at the PR bar.
What happens
The chip is still there, pointing at the closed PR and showing its last known
state.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.1.263 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the session binding by running gh pr create, then close the PR with gh pr close or on GitHub and observe the PR bar. Start by tracing the session's PR binding, state refresh, and unbind behavior; done means a closed or merged PR chip clears automatically or provides a working dismiss control.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100