dsh delete session: desktop, web and CLI compared

Desktop, web, and CLI share one behavior: the UI archives, and the disk deletes. All three read the same data, but their entry points differ; confusing archive with deletion makes "hidden" look like "removed."

Separate archive, delete, and clear

Three words are used interchangeably and behave differently.

Archive changes the registry; delete changes files. Archive only writes state, leaving logs intact. Deletion is a filesystem operation and is irreversible. Clearing affects context, not history.

All three clients share the registry. On one machine and one DSH_HOME, archiving in the desktop app hides the session in the web UI as well. Across machines, each is independent.

Desktop: archive only

The desktop app provides archive, not a delete button. That is a design choice.

1. Find the session in the list and open its context or more menu.
2. Choose Archive; the session disappears from the current list.
3. To restore it, open the archive view and unarchive.
4. To truly delete, exit the app and remove the directory under DSH_HOME/sessions.

Archive is reversible; deletion is not. Archive suits "I do not want to see it now"; deletion suits "I am sure I no longer need it."

Exit before deleting directories. Deleting while running can leave indexes and files inconsistent, causing errors or stale entries on the next start.

Web: same data, different entry

The web UI reads the same session data and archives the same way. The entry point and cache differ.

1. Find the session in the sidebar and use the archive entry.
2. Refresh after archiving to confirm it is gone.
3. If it remains, clear browser cache before deleting files.
4. Real deletion still happens on disk; the web UI does not expose it.

Most web "delete" buttons are archive aliases. Before clicking, check whether it changes the registry or files.

Multiple tabs amplify confusion. One tab archives while another shows stale state; refresh before concluding the archive failed.

CLI: no delete command, two workarounds

The CLI has no built-in session delete command.

1. Remove the directory: stop the running service, go to DSH_HOME/sessions, find the project and session directory, and remove it after copying a backup.
2. Session-management plugin: install a plugin that provides a panel or bulk delete; it ultimately operates on the same directories with extra confirmation.
3. Verify: restart and check for residue; if residue remains, the wrong level was deleted or the index did not update.

Delete the session directory, not the project directory. Sessions are usually nested under a project; deleting the project takes other sessions with it.

Plugins do not remove risk. Bulk deletion amplifies mistakes; confirm filters and export or back up before running.

Three clients compared

Compare entry, scope, and reversibility.

Use archive for daily tidying and deletion for real cleanup. They solve different problems and do not replace each other.

Recovery after accidental deletion

Session logs are plain files and do not go to a trash bin. Recovery depends on what you did before deleting.

1. Stop writes immediately. Stop the service so new data does not overwrite recoverable blocks.
2. Check backups and snapshots. A full-directory backup or filesystem snapshot can restore the previous state.
3. Check other machines. With multi-machine sync, a copy may exist; watch version consistency when copying back.
4. Check the index. Deleting logs but not the index can produce "listed but fails to open"; clean or rebuild the index as well.

The key to recovery is a backup made before deletion. Afterward you can limit damage, not restore; a backup habit beats any recovery trick.

Do not substitute regeneration for recovery. Regenerating creates a new session, not the old context and conclusions.

Pre-delete checklist

Run this list before deleting a session.

1. Confirm the directory: project name, session time, and title all match.
2. Confirm no running task: deleting while writing leaves half-written logs.
3. Confirm a backup: copy anything worth keeping before deleting.
4. Confirm the scope: remove the session directory, not the project or DSH_HOME root.
5. Confirm index sync: restart after deletion and check for residue.

The checklist turns an irreversible action into a reviewable process. Pass all five before acting.

Next steps

Use archive and deletion for different jobs, and back up first. For the conceptual difference, read Archive vs delete session. For session-management plugins, read How to choose a session manager plugin. For recovery, read Can a deleted session be recovered.

Sources: DeepSeek Harness docs, dsh CLI README, deepseek-harness repository