claude-code - 💡(How to fix) Fix [DOCS] Agent view deletion docs say deleted sessions remain resumable

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Because claude rm <id> is the shell equivalent of removing a background session, its reference should match the updated deletion behavior too.

RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/agent-view

Section/Topic

"Monitor sessions with agent view" deletion instructions, plus the claude rm <id> command description

Current Documentation

The docs currently say:

To remove a session from the list, press Ctrl+X to stop it and Ctrl+X again within two seconds to delete it. Pressing Ctrl+X on a group header deletes every session in that group after confirmation.

Deleting removes the session from agent view and cleans up its worktree, including any uncommitted changes in it, so push or commit work you want to keep before deleting. The conversation transcript stays on disk and remains available through claude --resume.

The command reference on the same page also says:

| claude rm <id> | Remove a session from the list. Cleans up its worktree if there are no uncommitted changes |

What's Wrong or Missing?

The current agent-view docs conflict with the v2.1.143 changelog entry:

Fixed deleting a session from agent view not removing its transcript file

That changelog entry indicates that deleting a session from agent view now removes the transcript file. The current docs still say the opposite: that deleting a session leaves the transcript on disk and keeps it available through claude --resume.

This creates a user-facing contradiction in the deletion workflow:

A. The delete behavior appears to have changed, but the docs still describe the old behavior

Users reading the current page are told that deleting a session only removes it from agent view while preserving the transcript for later resume.

B. The claude rm <id> description does not clarify transcript deletion semantics

Because claude rm <id> is the shell equivalent of removing a background session, its reference should match the updated deletion behavior too.

Suggested Improvement

Update the agent-view deletion docs to match the current behavior introduced by v2.1.143.

Before:

Deleting removes the session from agent view and cleans up its worktree, including any uncommitted changes in it, so push or commit work you want to keep before deleting. The conversation transcript stays on disk and remains available through claude --resume.

After:

Deleting removes the session from agent view, cleans up its worktree, and deletes the local transcript file, so the session is no longer available through claude --resume.

Also update the claude rm <id> command description to make the same deletion semantics explicit, and add a short warning telling users to stop or export a session instead of deleting it if they want to keep the conversation history.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/agent-view174-176, 358Deletion instructions explicitly say the transcript stays on disk and remains resumable, while the same page also documents claude rm <id> for the corresponding shell workflow
https://code.claude.com/docs/en/cli-reference36claude rm <id> is documented without clarifying that deleting a background session also removes its transcript file

Total scope: 2 pages affected

Source: Changelog v2.1.143

Exact changelog entry:

Fixed deleting a session from agent view not removing its transcript file

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING