Desktop: pending "Suggested task" chips are lost on app restart — not persisted with the session

Environment

• Claude Code desktop app, Windows 11 Home (10.0.26200)
• Claude Code 2.1.218

Bug

Pending "Suggested task" chips (the ones spawn_task creates) do not survive a restart of the desktop app. They are not attached to the session — they only exist in the running app's memory. Restart the app, reopen the exact same session, and the chip is simply gone. There is no pending-suggestions list, no entry in the transcript you can click, no way to recover the suggestion. The only trace is the tool call in the scrollback, which is not actionable.

The dismiss_task tool description already admits the underlying cause: "Task ids are not persisted across app restarts." So the id layer is stateless by design — but the user-visible consequence is that a suggestion the model deliberately surfaced for me to act on later is destroyed by an unrelated app restart.

Why this bites constantly

Restarting the desktop app is not a rare event — it is a routine, and often mandatory, part of the workflow:

1. Applying an app update — you get prompted to restart.
2. Reloading MCP servers — after adding a new MCP server, or after adding new tools to an existing one, a restart is the reliable way to get the app to reconnect and pick them up.

Both of those are things you do while working, mid-session, exactly when suggestions are piling up. So the two most common reasons to restart are also the two most common ways to silently lose every queued suggestion. The whole point of the chip is "this is out of scope, do it later" — and "later" is precisely when it no longer exists.

It also means the feature quietly punishes you for keeping the app current: taking the update costs you your backlog.

Steps to reproduce

1. Work in a session until Claude surfaces one or more "Suggested task" chips.
2. Don't start them and don't dismiss them — leave them pending, which is the intended use.
3. Fully quit and relaunch the desktop app (update prompt, or to reconnect an MCP server after adding a tool).
4. Reopen the same session.

Actual: No chips. Nothing pending anywhere in the UI. The suggestions are unrecoverable.

Expected: Pending suggested-task chips are persisted alongside the session and re-rendered when the session is reopened. A chip should disappear only when I resolve it — start it, or dismiss it — not because the app process ended.

Suggested fix

• Persist pending chips (prompt, title, tldr, cwd, originating session) to session state on creation, and rehydrate them on session load.
• Stable, persisted task ids so dismiss_task can still target a chip after a restart, instead of the current documented "ids don't survive restart" behavior.
• Ideally also a global "pending suggested tasks" view so suggestions aren't only reachable through the one session that produced them — this would also address the queued-chip problem in #70388.

Related

• #70388 — queued chips: only the front one is reachable
• #77405 — chips never rendering at all on Windows desktop
• #75641 — the mirror-image bug: stale commit chips that persist across restart when they shouldn't

Between #75641 and this one, chip lifecycle looks inverted across the board: the chips derived from live git state stick around forever after they're irrelevant, while the chips that represent real user intent get thrown away on process exit.