Run History

Run History

Every command you run (see Running Commands) is recorded. The History view (left pane footer, next to Settings) lists past runs newest-first and lets you search, reopen, replay and re-run them.

The list

Each run appears as a card showing:

• the Snip title and a status chip (Exit 0, Exit 1, … or Cancelled),
• the resolved command that was executed,
• the CLI, the time it ran, and the duration,
• a short preview of the run's clean output.

A search box filters the list by matching text in either the command or the captured output (case-insensitive).

Open and replay a run

Click Open on a run to reopen it in the same panel used for a live run, in replay mode: the retained raw output is written back into the terminal, so you see it again in full colour. The Cancel button is disabled (nothing is running) and Run again is available.

Run again

Run again re-runs the same Snip from scratch — it walks the normal Run flow (parameter fill and dry-run preview) so you can confirm before it executes. If the original Snip has since been deleted, Snipdeck tells you it's no longer available.

Delete and clear

• Delete removes a single run from the history.
• Clear all removes every recorded run (confirmed first).

What's stored, and the clean-vs-raw distinction

Each run records its command, the parameter values used, start time, duration, exit code and cancelled flag, plus two forms of output:

• a clean transcript — plain text with all ANSI escape codes, cursor movements and stacked spinner/progress frames collapsed away. This is what's shown in previews and what search matches against, so it stays readable and grep-friendly.
• the raw stream — the original terminal output (compressed), kept so a run can be replayed in colour.

Retention and size limits

• Per-Snip retention — Snipdeck keeps the most recent N runs per Snip (default 50) and prunes older ones after each run. Configurable in Settings (1–1000).
• Capture cap — a single run's captured output is limited (default 5 MB); beyond that it's truncated and marked as such. Configurable in Settings (1–100 MB).

Where history is stored

Run history lives in a dedicated SQLite database (history.db) alongside your store, not in the JSON snip store — run output isn't "small", so it's kept separate to keep the store lean. See Data Storage and Backups.