[BUG] Desktop: stuck "Commit changes" suggestion cards never clear — survive restart, dismiss, and being acted on

Status Closed — duplicate
Reported on v2.1.219
Maintainer reply None cached
Activity 3 comments · opened Aug 8, 2026 · closed Aug 25, 2026

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?

Summary
Five "Commit changes" suggestion cards are permanently stuck in a Claude Code Desktop session and cannot be cleared by any means found.

Environment

  • Claude Code Desktop v2.1.219 (entrypoint: claude-desktop), Windows 11 Pro (build 26200)
  • Local git repo with several linked worktrees; the session cwd is a linked worktree whose git resolves to the main checkout's branch

Background
For ~12 days the working tree intentionally held uncommitted changes (an explicit "don't commit yet" hold), with several sessions active on the same branch during that window. The app minted five "Commit changes" cards during that period. The changes were then committed and pushed; the branch has been verified clean many times since (git status + git stash list across the main checkout and every linked worktree — all clean, up to date with origin).

The five cards never clear. They survive:

  • Full app restart (process fully ended via Task Manager first)
  • Opening and switching through every session in the project
  • Being acted on: each click just re-fires the stored prompt "Commit the working tree changes with a sensible message." into the active session (7+ times so far); the session verifies a clean tree and reports nothing to commit; the card remains
  • The session's task list being empty (all TaskCreate/TaskUpdate entries completed, then explicitly deleted; ~/.claude/tasks/<sessionId>/ is empty)

Investigated from inside the session (elimination)

  • ~/.claude/tasks/*: zero pending tasks, zero tasks mentioning "commit"
  • Session transcripts (~/.claude/projects/.../<session>.jsonl) record only gitBranch per message — no dirty-file snapshot that could be stale
  • No "Commit changes" string found in %APPDATA%/Claude Local Storage / Session Storage / IndexedDB label search
  • Conclusion: the card state appears to live in server-side session state that is never invalidated or consumed

Expected
Cards should clear when the tree they reference is clean — or at minimum when the card is acted on or dismissed.

Actual
Cards persist indefinitely and re-inject the same commit prompt into the session on every click.

Related
#83844 reports the same persistent-card symptom for a non-git (SVN) directory. This report shows it also occurs for a clean, fully-pushed git repository, that multiple cards can accumulate, and that acting on a card does not consume it — so the stale-card invalidation bug is not specific to non-git directories.

What Should Happen?

"Commit changes" suggestion cards should be invalidated when the working tree they reference becomes clean, and at the very least should be consumed (removed) when the user clicks them or dismisses them. Stale cards should not survive an app restart, and identical cards should not accumulate.

Error Messages/Logs

Steps to Reproduce

  1. In Claude Code Desktop, work in a git repository and intentionally leave the working tree with uncommitted changes over several days, across multiple sessions on the same branch (an explicit "hold the commit" workflow). One "Commit changes" suggestion card appears per session-ish — five accumulated here.
  2. Later, commit and push everything. Verify git status is clean and the branch is level with origin in the main checkout and every linked worktree.
  3. Fully quit the app (end the process) and reopen the session.
  4. The cards are all still displayed. Clicking one re-sends its stored prompt ("Commit the working tree changes with a sensible message.") into the active session; the session finds a clean tree and nothing to commit; the card is NOT consumed and can be clicked again indefinitely. Dismiss/refresh paths (switching sessions, opening each session once) also do not clear them.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.219 (Claude Code Desktop)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Environment note: this is the Claude Code Desktop app (entrypoint claude-desktop), not a terminal CLI session — the Terminal/Shell field above reflects the shell the harness uses on Windows. The affected UI element is the desktop app's "Commit changes" suggestion card.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗