🔄 dsh-session-sync
- 1024 store channel:
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 · हिन्दी
Compatibility
| Surface | Status |
|---|
| Harness | DeepSeek Harness dsh-v0.1.5-rc.2 (GitHub tag, verified 2026-09-11: full gate chain + profile install smoke). npm dependency line 0.1.5-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 |
What you get
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.- Append-only conflict resolution — session logs are append-only; on any divergence the plugin keeps both sides (local version kept, remote version preserved as fork files) and never silently overwrites. Diverged sessions can also fork at the session level.
- Auto modes — pull on start, push after every closed turn, and periodic pull, all configurable and all reversible.
- Confirmation-gated writes —
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)
Quick start
# 1. install the bundle into your profile
dsh plugin --profile web add "github:PerryLink/dsh-session-sync#main"
# 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
Install & uninstall
- git channel (latest
main): dsh plugin --profile web add "github:PerryLink/dsh-session-sync#main" (equivalent to installing from git+https://github.com/PerryLink/dsh-session-sync.git). No build step — index.mjs and lib/ are the shipped artifacts.
- npm channel (published releases):
dsh plugin --profile web add dsh-session-sync.
- tarball channel:
pnpm pack in this repo, then dsh plugin --profile web add ./dsh-session-sync-<version>.tgz.
- uninstall:
dsh plugin --profile web remove dsh-session-sync (or remove the row from the profile patch).
Configuration
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 |
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
Tools & surfaces
| 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 |
Permissions & data
- Permissions: mutating operations cross the confirmation gate (
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.
- Data: sync metadata (device id, last pull/push, last push head, last error) lives in the
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.
- Session log:
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.
Security boundaries
- Never silently overwrite. The append-only three-way merge keeps both sides on any divergence; fork files are never deleted, and git never force-pushes, resets, rebases, or switches branches.
- Path containment. Files are mirrored as opaque bytes with symlinks refused and every joined path containment-checked (
PATH_UNSAFE fails loud).
- Sanitized output. Remote-URL credentials, tokens, and
key=value secrets are redacted before reaching the model or the log; path display refuses anything outside its root.
- No credential storage. The plugin stores no credentials; git credentials live in your normal git credential helper. age keys are read from paths you configure (
ageIdentity); keys never enter the sync repository.
- Git hardening. Git runs with
GIT_TERMINAL_PROMPT=0 and GIT_OPTIONAL_LOCKS=0, deadline- and signal-bounded, with a per-stream output cap.
- Fail closed. A missing confirmation answerer, a missing remote, or an unsafe path refuses the operation loudly.
Encryption & threat model
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:
- Mirror content at rest in the remote. The session files you push are age ciphertext; the remote host, its operators, and anyone who clones the repository do not see plaintext session bytes without the private key.
What it does not protect (the boundary):
- Keys and age identities are yours to manage. The recipient/identity files are never shipped, stored, or rotated by the plugin. If a key leaks, the mirror content it protects is exposed. Use a passphrase-less identity and keep it out of the repository.
- The remote is still a private repository in practice. git metadata — commit messages, the
.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.
- Plaintext still exists locally. The mirror at
<repoDir>/sessions/ is plaintext on disk; encryption protects the transmitted/remote copy, not local disk encryption or the live session store.
- graceful degradation means plaintext. With
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.
Known limitations
- Object storage backend reserved.
object-storage is an interface placeholder and fails loudly at load; only git and encrypted are implemented.
- git required. The plugin needs the
git executable and the subprocess service; without them, sync operations fail with a clear reason (profiles keep booting).
- age is optional, external. Encryption depends on the
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).
- One repoDir per backend. Switching between
git and encrypted on the same repoDir is not supported; use a fresh worktree per backend.
- Session events on
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. 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.- Host-private artifacts stay host-private.
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.
Development
pnpm install # node ^22.19 || >=24
pnpm run typecheck && pnpm run typecheck:ci # tsc --checkJs against the published 0.1.5-rc.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.
Topics
dsh, dsh-plugin, deepseek-harness, deepseek, cordis, session-sync, session, git, sync, cross-device
Contributors
- @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.
PerryLink DSH Plugin Family
This project is one of the 40 DeepSeek Harness plugins maintained by PerryLink. If this one helps you, the others likely will too:
| Plugin | One-liner |
|---|
| dsh-auto-review | Second-model auto-review on the approval chain, fail-closed by default |
| dsh-background-agents | Durable background child agents with a Web UI sidebar, messaging and interrupt |
| dsh-budget | Cost governance for DeepSeek Harness: budgets, carbon, and latency in one panel. |
| dsh-checkpoint-rewind | Claude Code /rewind-equivalent: snapshots, session forks, one-shot restore |
| dsh-claude-move | Migrate Claude Code sessions, memory, skills and CLAUDE.md into DSH |
| dsh-click | Cross-platform native desktop control for DeepSeek Harness — Windows first. |
| dsh-composer-history | Terminal-style input history for the web composer: arrows, Ctrl+R search |
| dsh-data-quality | Dataset quality checks and citation cross-checks (the optional numeric bridge consumed here) |
| dsh-defend | Prompt-injection, jailbreak, and secret-leak defense for DeepSeek Harness. |
| dsh-doublecheck | Engineering-discipline guard: requirements grill, test gates, adversary review |
| dsh-draw | Unified static-image generation routing for DeepSeek Harness. |
Install from the DSH Desktop Market
All PerryLink plugins are browsable in the built-in DSH Desktop Market: Market → Sources → add source → paste https://perrylink-dsh-catalog.perrylink.workers.dev/catalog-source.json → select it. Installation still goes through the Market's npm-identity verification and your confirmation.
License
LICENSE (Apache License 2.0) © 2026 dsh-session-sync contributors
