dsh-session-sync
Advanced tools
Cross-device sync for DeepSeek Harness sessions: a dedicated git mirror of the session store, append-only three-way merge with keep-both + fork conflict resolution, /sync command, sync_pull/sync_push/sync_status tools, and configurable auto push/pull
npm i -g dsh1024 once, then dsh1024 plugin --profile web add dsh-session-sync (counts toward the deepseek1024.com install ranking).
Cross-device session sync for DeepSeek Harness — a dedicated git mirror of your session store.
Sync your sessions between devices, keep both sides on any conflict, never lose a turn.
Official repository. This is the only official repository of dsh-session-sync, maintained by PerryLink. Same-name repositories under other accounts are not affiliated.
English · 简体中文 · Español · Português · हिन्दी
dsh plugin --profile <name> add dsh-session-sync
📖 Ecosystem knowledge base — measured data, not marketing: plugin development guide · plugin-selection data · maintenance criteria.
main): dsh plugin --profile web add github:PerryLink/dsh-session-sync (equivalent to installing from git+https://github.com/PerryLink/dsh-session-sync.git). No build step — index.mjs and lib/ are the shipped artifacts.dsh plugin --profile web add dsh-session-sync.pnpm pack in this repo, then dsh plugin --profile web add ./dsh-session-sync-<version>.tgz.dsh plugin --profile web remove dsh-session-sync (or remove the row from the profile patch).这个插件是 DSH 插件家族的一员（95 个，全部 Apache-2.0）。如果你在用，给个 star —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。
English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.
Cross-device session sync for DeepSeek Harness — a dedicated git mirror of your session store.
Sync your sessions between devices, keep both sides on any conflict, never lose a turn.
The same run, animated.
| Surface | Status |
|---|---|
| Harness | DeepSeek Harness dsh-v0.2.1-alpha.1 (GitHub tag, verified 2026-09-25: full gate chain against the pinned 0.1.7-rc.2 peers). npm dependency line 0.1.7-rc.2, peers `>=0.1.2-rc.1 <0.2.0 |
| Node | ^22.19.0 || >=24.0.0 |
| Platforms | Anywhere git and DSH run (git-based mirror; no platform-specific code) |
| Model | Text-only models fully supported; no vision or extra model capability required |
dsh-session-sync mirrors your DSH session store into a dedicated git worktree and syncs it to a remote you control — no cloud service, no third-party storage:
/sync command — status (branch, sanitized remote, ahead/behind, dirty files, forks), diff, log, pull, push, help.sync_status / sync_pull / sync_push tools — the same surface for the model, inside a turn.pull/push ask first (through userQuestions or approval); read-only surfaces never ask; with no answerer the operation fails closed.device A remote (your git repo) device B
$DSH_HOME/sessions ──mirror──▶ commit ──push──▶ [sessions] ──pull──▶ merge (keep-both + fork)
dsh plugin --profile web add github:PerryLink/dsh-session-sync
# 1. install the bundle into your profile
dsh plugin --profile web add github:PerryLink/dsh-session-sync
# or from npm (published releases)
dsh plugin --profile web add dsh-session-sync
# 2. point it at a private git remote and verify the row
dsh --profile web --dump-config | grep -A2 'id: session-sync'
Then set the remote in your profile patch (a private repository is the baseline) and sync:
- insert:
- id: session-sync
name: dsh-session-sync
config:
remote: git@github.com:you/your-dsh-sessions.git
> /sync status
> /sync pull
> /sync push
All tunables are Schemastery Config fields (changeable from cordis.yml). An id-targeted override replaces the whole row — restate every key you need. cordis.patch.yml documents each key inline.
| Key | Default | Meaning |
|---|---|---|
enabled | true | Master switch; false unregisters the command, tools, listeners, and auto modes |
backend | git | Sync backend: git (plaintext mirror) or encrypted (age-encrypted mirror content) |
sessionRoot | '' | Session store root; empty = $DSH_HOME/sessions (both missing fails load) |
repoDir | '' | Sync worktree root; empty = $DSH_HOME/dsh-session-sync/repo |
remote | '' | Remote address (required before pull/push; status/diff work without one) |
branch | main | Remote branch name |
gitBin | git | git executable path |
ageBin | age | age executable path (probed for backend: encrypted; missing degrades to plaintext) |
ageRecipient | '' | age recipient (public key or identity string); empty = cannot encrypt, degrades to plaintext |
ageIdentity | '' | Path to a passphrase-less age secret key for decryption; empty = cannot decrypt, degrades to plaintext |
autoPullOnStart | false | Pull once when the plugin mounts (config is the grant; no re-confirm) |
autoPushOnTurnEnd | false | Push after every closed turn |
pullIntervalMinutes | 0 | Periodic pull every N minutes (0 = off, max 10080) |
confirmVia | auto | Confirmation channel: auto (userQuestions first, then approval), userQuestions, approval |
graceMs | 10000 | Grace period for git kills (ms) |
commandTimeoutMs | 120000 | Per-command timeout (ms) |
maxOutputBytes | 262144 | Per-stream collected-output cap (bytes) |
commitName | dsh-session-sync | Commit author name |
commitEmail | dsh-session-sync@localhost | Commit author email |
registerCommand | true | Register the /sync command |
registerTools | true | Register the sync_* tools when the tools service is present |
Example override in your profile patch:
- insert:
- id: session-sync
name: dsh-session-sync
config:
remote: git@github.com:you/your-dsh-sessions.git
branch: main
autoPushOnTurnEnd: true
pullIntervalMinutes: 30
confirmVia: userQuestions
| Surface | Read-only | Needs confirmation | Notes |
|---|---|---|---|
/sync status | ✅ | — | Branch, sanitized remote, ahead/behind, dirty files, fork files, last pull/push |
/sync diff | ✅ | — | Uncommitted changes + HEAD..remote stat (read-only) |
/sync log | ✅ | — | Last commits in the sync repository |
/sync pull | ✅ | Fetch + merge with keep-both semantics; local kept, remote preserved as forks | |
/sync push | ✅ | Mirror + commit + push; never force-pushes, reconciles and retries once on rejection | |
sync_status | ✅ | — | Same facts as /sync status for the model |
sync_pull | ✅ | Model-callable pull | |
sync_push | ✅ | Model-callable push |
confirmVia); the plugin never re-implements or bypasses the harness's userQuestions/approval services. Auto modes are covered by the config grant and never re-confirm.session-sync storage domain. Session files are copied as opaque bytes — the plugin never parses them. The device id is also written to device.txt in the sync repository for cross-device fork attribution.sync/push, sync/pull, and sync/conflict are declared in types.d.ts; they are appended only when the host records the types (see Known limitations). Everything written or shown is sanitized. The one durable message the plugin writes — the conflict fork notice — carries the plugin's own producer-owned source kind (dsh-session-sync); the harness retired the shared plugin kind and refuses it when a session is read back.PATH_UNSAFE fails loud).key=value secrets are redacted before reaching the model or the log; path display refuses anything outside its root.ageIdentity); keys never enter the sync repository.GIT_TERMINAL_PROMPT=0 and GIT_OPTIONAL_LOCKS=0, deadline- and signal-bounded, with a per-stream output cap.backend: encrypted adds an optional age layer above the mirror: session bytes are encrypted into encrypted/**/*.age files before they are committed and pushed, and decrypted back to the local plaintext mirror before merging. The three-way merge always runs on plaintext locally, so the append-only keep-both semantics are unchanged.
What the encryption protects:
What it does not protect (the boundary):
.gitignore, the encrypted/ path structure, branch names, and push/fetch activity — remains visible to the remote host. Encryption hides the content, not the fact that you sync, nor the shape of your session tree.<repoDir>/sessions/ is plaintext on disk; encryption protects the transmitted/remote copy, not local disk encryption or the live session store.backend: encrypted, if age is missing, or ageRecipient/ageIdentity is empty, the plugin falls back to the plaintext git path and warns explicitly in the status/log — it never silently pretends to encrypt. Check /sync status for the warning before trusting the remote as encrypted.Baseline: with backend: git (the default), session bytes are stored unencrypted in your git remote — use a private repository.
object-storage is an interface placeholder and fails loudly at load; only git and encrypted are implemented.git executable and the subprocess service; without them, sync operations fail with a clear reason (profiles keep booting).age binary on PATH (or ageBin). No age → plaintext fallback with a warning; a passphrase-protected identity cannot be used (decryption would block on a TTY prompt, so it fails closed).git and encrypted on the same repoDir is not supported; use a fresh worktree per backend.0.1.0-rc.6/0.1.0-rc.8/0.1.1-rc.2/0.1.2-alpha.2/0.1.2-alpha.3/0.1.2-rc.1/0.1.7-alpha.2. The harness does not record sync/* event types, so the session-log appends are skipped (sessions keep loading); the plugin enables them automatically once a host records the types or exposes the ignorable envelope on Session.append.approval between turns. /sync runs between turns, where the approval channel has no open turn to attach to; use confirmVia: userQuestions for command-driven sync, or drive sync through the tools inside a turn. The open-turn check reads the host turnBoundary session projection: a composition without @deepseek-ai/dsh-session-projection cannot verify the turn state and fails closed with that reason.session.lock (the harness session lease) and session.migration.*.tmp staging files are never mirrored or deleted — they are runtime state, not syncable content. Session logs (session.jsonl, session.v[1-9]*.jsonl[.zstd]) remain the mirrored payload.pnpm install # node ^22.19 || >=24
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs against the published 0.1.7-alpha.2 peers
pnpm test # node --test (13 test files; the engine git suite skips without git)
pnpm run verify:self-contained # dependency specs resolve from the registry
pnpm run verify:artifacts # shipped files present + index.mjs importable
pnpm run check:readmes # five-language README consistency
pnpm pack # the published tarball
There is no build step: pure ESM, index.mjs and lib/ are the shipped artifacts.
dsh, dsh-plugin, deepseek-harness, deepseek, cordis, session-sync, session, git, sync, cross-device
@BlakrPander — PAT-as-username redaction and the delete/modify keep-both analysis (#14); both halves shipped in 0.2.27/0.2.28.
@PerryLink — creator and maintainer: git mirror engine, append-only keep-both merge, /sync command and sync_* tools, auto modes, sanitizers, and the five-language docs.
This project is part of the DeepSeek Harness plugin family from PerryLink. The roster stays collapsed below so every README keeps a short first screen; expand it to see every row and its status.
LICENSE (Apache License 2.0) © 2026 dsh-session-sync contributors
FAQs
Cross-device sync for DeepSeek Harness sessions: a dedicated git mirror of the session store, append-only three-way merge with keep-both + fork conflict resolution, /sync command, sync_pull/sync_push/sync_status tools, and configurable auto push/pull
The npm package dsh-session-sync receives a total of 1,062 weekly downloads. As such, dsh-session-sync popularity was classified as popular.
We found that dsh-session-sync demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Threat Research
/Security News
Socket uncovered secret-stealing workflows that ran in LiteLLM’s GitHub repository 11 days before the supply chain attack on PyPI and Docker.
Security News
Cloudflare introduces tsrs, a Rust port of TypeScript’s compiler promising faster checks and lower memory use, with the TypeScript team’s help.
Security News
The PHP Foundation says Chainguard broke a security embargo ahead of critical RCE patches, as leaks disrupted the coordinated release.