dsh-session-remove

LIMITATIONS

Known limitations

- **Deletion is permanent**: no trash, no undo. - Subagent sessions are deleted with their parent by default; `deleteSubagentSessions: false` turns that cascade off. - A forked conversation is independent: deleting its source does **not** delete the fork, even though the fork records `parentSession`. - If a subagent session cannot be cleaned up, the parent is still deleted (the user's main intent already succeeded) and the leftover needs manual handling; the dialog lists the session ids. - Workspace cleanup is a **creation-time heuristic**: a pre-existing file the session overwrote is not deleted (its new content stays), the walk is capped at 20,000 entries, and the skipped rest is reported. - Attachments are content-addressed and deduplicated; only objects that no other session references are reclaimed, shared ones are kept. - Deleting the session that is open in the UI releases it first (the main area returns to its empty state). - Stopping discards queued input — that is the semantics of the official stop path it reuses. - An update needs a restart; the old Host module stays in memory until then.