Code tab accumulates hundreds of empty auto-created sessions (body = "settings dialogue dismissed")

Summary

The desktop app's Code tab accumulates hundreds of empty, auto-created sessions whose only content is the string "settings dialogue dismissed". They build up over time (entries going back months) and cannot be cleared by quitting/relaunching the app.

Environment

• Claude desktop app — Code 2.1.160, bundled claude-code-vm 2.1.156
• macOS 26.3.1 (build 25D771280a), kernel Darwin 25.3.0
• Apple Silicon

What I observe

• The Code tab lists hundreds of sessions going back a long time.
• Each is displayed with a VM slug name of the form <hostname>-local-<adjective>-<surname> (e.g. machine-local-wobbly-ritchie), not a human-readable title.
• Opening one shows a body containing only the text "settings dialogue dismissed" — no real prompt or conversation.
• They persist across a full Cmd+Q quit and relaunch.

Investigation / likely cause

• The local on-disk stores under ~/Library/Application Support/Claude/ (local-agent-mode-sessions/, claude-code-sessions/) contain only ~80 real sessions, each with a proper title and transcript — not hundreds, and none whose body is "settings dialogue dismissed".
• The literal string "settings dialog…dismissed" appears only inside the app's own binaries (claude.app/Contents/MacOS/claude and the VM rootfs.img), not in any saved session transcript.
• Conclusion: the hundreds of entries are server-side account records rendered by the Code tab, being auto-created with this placeholder body — apparently triggered by a benign UI event (dismissing the settings dialog) rather than by starting an actual task. That's why local cleanup and app restarts have no effect.

Expected behavior

• Dismissing the settings dialog (or whatever UI event triggers this) should not create a session/conversation record.
• Empty / no-prompt sessions should not be persisted or listed, and the Code tab should never fill with hundreds of unnamed placeholder entries.

Impact

• The Code tab session list is effectively unusable — real sessions are buried under hundreds of identical empty placeholders.
• The records appear to be created server-side, so users cannot remove them by clearing local data.

Requests

1. Fix the root cause so these placeholder sessions are no longer created.
2. Provide a bulk-delete / "clear all" path (and ideally a server-side purge), since deleting hundreds individually is impractical.