[BUG] PR chip stays in the bar after the PR is closed or merged, with no way to dismiss it

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?

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

1. Open a session in a repo with a GitHub remote.
2. 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.

1. Close that PR, either with gh pr close or from GitHub. In my case Claude

closed it because a replacement PR superseded it.

1. 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_