dsh-session-takeout
将一段对话打包成 ZIP，以便在另一台电脑上打开并恢复
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:northstacker/dsh-session-takeout#778f21f43bd348938316f12f153b895f2e294853Session Takeout 以 dsh-session-takeout 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English · 简体中文
Packs one DeepSeek Harness conversation into a single ZIP, so you can carry it to another computer and keep talking there.
plugin_manager → install_bundle → target: <this directory>
Below the message box there are two small buttons:
~/Downloads, then reveals it in Finder.A conversation is not just text in the browser. The durable event log, the attachment object store and the workspace registry live on the machine running the Host, so the Client half only presses two routes:
| Route | Purpose |
|---|---|
POST /session-takeout/export | { sessionId } → writes and reveals a ZIP, returns its path |
POST /session-takeout/import | raw ZIP bytes → restores the session, returns its new id |
POST /session-takeout/reveal | { path } → reveals a path in Finder |
manifest.json format tag, session summary, counts, checksums
session/header.json SessionHeader + inheritedEventCount
session/events.jsonl the full event log, one JSON object per line
attachments/<id> raw bytes of every image or file the conversation used
plugin/<file> this plugin's own sources, so the archive can install it
README.md plain instructions for a human
The container is an ordinary ZIP (deflate, UTF-8 names, no ZIP64), written with
node:zlib and a local CRC-32 table so no dependency is pulled in. It opens in Finder,
Explorer and unzip; the conversation itself stays readable without this plugin.
The format tag inside manifest.json stays dsh-session-bundle on purpose: the
archive format is versioned separately from the project name, so bundles written by
earlier builds keep importing after a rename.
cwd at a fresh directory,A restored conversation therefore lands in
~/Documents/DeepSeek Harness/<title>-<shortid>/, which becomes its workspace — the
exporter's absolute paths are never reused.
Every exported ZIP carries this plugin's sources under plugin/, so a fresh machine
needs nothing but the archive:
plugin/ as a bundle (plugin_manager → install_bundle → <unzipped>/plugin).
On a machine that has never run this plugin, ask its agent to do this step — it can
also post the ZIP to the route itself, without opening any dialog:
curl -X POST http://127.0.0.1:<port>/session-takeout/import --data-binary @bundle.zipmanifest.json under missingAttachments and simply do not travel.inheritedEventCount;
the parent's prefix is not part of the bundle, so only the part stored in this log
arrives.agentPreset travels as an id. If that preset is not installed on the target, the
session opens with the default agent.plugin_manager → install_bundle → target: <this directory>
The bundle patch inserts one row; nothing else in the profile needs editing. Restart the Web UI (or let the client plugin hot-reload) and the two buttons appear under the message box.
node test/bundle.test.mjs # 48 checks against fake services and a throwaway HOME
MIT