Replay Export

Replay export

Every slipstream session is already captured as an append-only event log under .claude/slipstream/dashboard/<sessionId>.jsonl, alongside the observation store. The slipstream export command bundles a session into a portable archive you can replay, share or attach to a bug report.

The command

node dist/cli/index.js export <sessionId>
# or, after the plugin is installed
slipstream export <sessionId>

Options:

• --out <path> write to a specific file. Default: ./slipstream-export-<sessionId>.zip.
• --include-memory include the observations and any lessons cited by this session.
• --redact apply the configured redaction rules from .claude/slipstream/redact.json before writing (on by default for shared exports).

The session id is whatever the dashboard picker shows for the session, also visible in the statusline log.

Manifest shape

The archive is a zip containing:

manifest.json
events.jsonl              the raw event stream (post-tool, hook, savings, budget)
map.json                  the project map as it was at session end
budget.json               targetTokens, warnPct, compactPct, actualTokens
observations/*.md         only the observations referenced by this session
lessons/*.md              only the lessons cited in those observations

manifest.json carries the metadata:

{
  "sessionId": "cursor-abc123",
  "createdAt": "2026-06-04T15:22:11.004Z",
  "client": "cursor",
  "slipstreamVersion": "0.6.0",
  "events": 1284,
  "tokensSaved": 184302,
  "redacted": true,
  "includeMemory": true
}

Why this is useful

• Debugging. Reproduce a bad turn against a fixed map and event stream, without needing the user's whole repo.
• Sharing a flow. Send a teammate the exact sequence of sp_* calls that led to a fix, with the dashboard timeline reconstructable from the JSONL.
• Filing a slipstream issue. Attach a redacted export and the maintainer can replay it locally.
• Auditing. Keep a per-release snapshot of what the agent did, with the same redaction policy you apply to logs.

The replay viewer at slipstream replay <archive> loads the archive into the local dashboard and steps through it; the live SSE stream is replaced by the recorded events at their original timestamps.

---

SarmaLinux . sarmalinux.com . Repository