Add setting to hide/disable the 'Create PR' button in the git status bar

I ran into a related problem with this bar: Claude created the PR for me as part of our chat (I didn't click the "Create PR" button in the git status bar), rather confusing. In this case I'd expect to at least see it reflect the next set of steps you could take in this case (e.g. a "View PR", maybe a "Merge PR" option as well).

I completely agree. I don't need this feature at all, but the button often appears late and is frequently pressed accidentally. After the update, the user experience has actually worsened.

Adding a related use case that widens the scope of this issue (and likely covers #56092 too):

When GitHub-CLI commands like gh pr list are executed during a Claude Code session, Claude Desktop renders the output as interactive PR cards (title, branch name, thumbnail, 'Open' button). These cards remain persistent in the chat history even after the underlying PRs are closed and branches deleted — leaving a misleading visual representation of the GitHub state.

Concrete scenario from a current session: I closed 7 PRs in one batch and deleted their source branches in my fork. The cards from earlier gh pr list outputs still show all 7 as if they were live entries, with 'Open' buttons inviting interaction. There's no way to clean this up — the cards are part of rendered tool output and can't be filtered or collapsed.

A broader 'hide tool-output widgets' / 'render tool output as plain text' toggle would address both the status-bar 'Create PR' button (this issue) and these historical rendered cards in one shot. Same UX-decluttering goal, broader effect. Even a per-card 'collapse' or 'mark as historical' option would help significantly.

+1 for any progress on this — willing to test alpha/beta builds.

I am working on several related project and these bars cover half of the chat area. It is annoying in combination because I don't need this function at all and your app fails to use entire window. It leaves small space to work. It is bad ui design, make it optional.

Please allow me to remove this.

I am a single programmer using a local repo and I do not use this feature ever. Please remove it as it is taking up valuable vertical viewing area on my laptop. Thank you.

+1 for a settings.json flag like showBranchStatusBadge: false.

Adding a concrete use case for the merge-conflict color indicator a recent desktop update added next to each session in the sidebar (orange = conflicts with base, green = clean): I work across ~11 long-lived engine worktrees that have intentionally diverged from main for months. Every one is permanently orange because they genuinely conflict with main — but I'm not merging them today, so the badge is permanent noise with no action attached, and it can't reflect anything actionable until I do a deliberate reconciliation. There's currently no way to hide it (no settings key, no context-menu toggle; Ctrl+B hides the entire sidebar).

Either would solve it: (1) showBranchStatusBadge: false in ~/.claude/settings.json (preferred — non-interactive, dotfile-friendly), or (2) a right-click "Hide" on the badge that persists per session.

Same here, really annoying! should be able to remove this from popping up all the time. Thanks!

Adding a data point beyond "I just want to hide this": in my case the button wasn't just unwanted, it was showing genuinely stale/misleading state.

A "Create draft PR" suggestion appeared reflecting a large diff (~2.5k insertions) from an earlier, unrelated task. It persisted across multiple sessions over several days with no dismiss/close control anywhere in its UI (right-click only offers Create PR / Create Draft PR / Manually Create PR). Since it kept showing up in later, unrelated sessions, it actively caused confusion about what the current session's actual working state was.

The only way I found to clear it was resolving the underlying git state directly (git commit, then git reset --hard to fully clean the working tree and match origin) -- nothing in the button's own UI helped.

Worth noting since it's a slightly different failure mode than "clutter I don't want": the suggestion isn't just annoying, it can misrepresent what's actually going on in a session.