dsh-auto-archive

A DeepSeek Harness (dsh) web plugin that archives sessions which are finished and have not been used for three weeks, once a night, without getting in your way.

A community plugin from SolidiFact. Not an official DeepSeek product.

What it archives

A session is archived only when all of these are true:

it has had no activity for 21 days (dsh's own last-activity time);
its goal, if it has one, is complete: an active, paused or blocked goal keeps it;
every to-do item is completed;
nothing is queued for its next turn;
it is not open, not running, not pinned, and not starred in @michengai/dsh-archive-manager (starring is respected when that plugin is installed);
it is a top-level session (a sub-agent's session follows its parent).

A session whose state cannot be read is kept. An empty session (opened, never used) has nothing unfinished, so it is archived once idle.

Why it is safe to leave running

Archiving deletes nothing. In dsh it hides a session, and it is restored with one click (for example from the archive manager's page).
Once a night, in a quiet window (03:30 to 05:30 local by default). If any session is running, it skips that check and tries again ten minutes later.
Each session is re-checked just before it is archived, and dsh is never asked to stop work: dsh itself refuses to archive a session with running activity.
Starred sessions it cannot read mean no archiving that night, not "no stars".
No more than 200 a night, oldest first.
Everything it does is written down: one JSON line per night in ~/.dsh/auto-archive/ledger.jsonl, naming every archived session with its title and last activity, plus how many were kept and why.

What it found on one install

A dry run on a real install with 769 sessions (dsh 0.1.7-rc.2):

	Sessions
Would archive (finished, idle 21+ days)	105
Kept: used in the last 21 days	442
Kept: sub-agent sessions	186
Kept: already archived	21
Kept: unfinished to-dos	11
Kept: blocked goal	1
Kept: state could not be read	2
Kept: open	1

Install

Tested with dsh 0.1.7-rc.2. Use the profile you run; these examples use web.

dsh plugin --profile web add @solidifact/dsh-auto-archive

See what it would do first. Before restarting dsh, put this in the profile's own ~/.dsh/profiles/web/cordis.patch.yml (replacing the empty [] if that is all it holds):

- id: auto-archive
  config:
    dryRun: true
    passOnStart: true

Restart dsh web, wait a minute, and read the last line of ~/.dsh/auto-archive/ledger.jsonl. It lists every session it would archive and how many it kept, and why. When the list looks right, remove those lines; from then on it archives each night.

To remove it:

dsh plugin --profile web remove @solidifact/dsh-auto-archive

Without npm: copy index.mjs into the profile folder as auto-archive.mjs and add it to that profile's cordis.patch.yml (drop the config: lines once the dry run looks right):

- insert:
    - id: auto-archive
      name: './auto-archive.mjs'
      config:
        dryRun: true
        passOnStart: true

Settings

Setting	Default
`idleDays`	`21`	days without activity before a finished session is archived
`runAt`	`"03:30"`	local time the nightly window opens
`windowHours`	`2`	how long the window stays open
`maxPerRun`	`200`	most sessions archived in one night
`dryRun`	`false`	decide and record, archive nothing
`passOnStart`	`false`	one extra pass a minute after dsh starts
`ledger`	`~/.dsh/auto-archive/ledger.jsonl`	where each night is recorded

Tests

node --test

@solidifact/dsh-auto-archive

Install

README

dsh-auto-archive

What it archives

Why it is safe to leave running

What it found on one install

Install

Settings

Tests

License