Sessions and Resume
DSH owns conversation persistence. DSH Console does not maintain a parallel transcript database.
/newcreates a fresh DSH Agent and empty Session after confirmation when the current conversation has content./sessionsopens a dialog of persisted top-leveldsh-console-*Sessions for the current working directory./resumeopens the same browser, while/resume <full-session-id>resumes a specific eligible Session.
Resume reads the canonical DSH event log, restores the historical model route, projects the visible surface into the TUI, and continues with the next turn. The switch is transactional: an unavailable model, damaged log, failed flush, or cancellation leaves the active Session unchanged.
Completion Sessions and Sessions from another working directory do not appear in the browser. Cross-directory search, rename, delete, and fork are not part of the current alpha.