AI Agent Hub
Back to plugins
🧠

dsh-git-sync

Memory Updated 2026.08.23

Run the following command in DeepSeek Harness:

dsh plugin install dHR-P/dsh-git-sync

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install dHR-P/dsh-git-sync in DeepSeek Harness to install it (source: https://github.com/dHR-P/dsh-git-sync).

About this plugin

DSH keeps its conversation logs on a single machine under ~/.dsh/sessions/, so switching to another laptop or desktop means losing sight of past sessions and being unable to pick up where you left off. dsh-git-sync turns that into a transparent git workflow: open the Git Sync card in DSH Web settings, bind a private remote, and push or pull to move conversations or full file trees between workspaces without any cloud service or extra database.

The plugin offers two granularities. Conversation-only mode moves session logs alone and never touches workspace files, which fits a setup where a primary machine runs a heavy development environment while a secondary device only needs read-only access to chat history. Full-file mode runs git add -A across the repository, letting a pure-dev workspace resume seamlessly on any other machine. A key convenience in conversation-only mode is path-agnostic mirroring: images are stored under a logical workspace name, and on pull the plugin rewrites each session header's cwd to the local path, so two devices living at entirely different absolute locations can still be recognized and resumed after a restart. Onboarding a new device is a single action inside the card: enter a local target path, pick a repository, and cloning, workspace registration, and path rewriting all happen in one shot.

It is well suited for DSH users who alternate between a laptop and a desktop, and for teams whose conversations contain sensitive content and prefer a private git repo over a public cloud host. On credentials, the plugin reuses the system's existing SSH key or credential manager in full, stores no secrets of its own, and keeps its configuration file free of sensitive fields.

Use Cases

  • Develop on a primary machine and review conversations on a secondary device only
  • Clone and restore all workspace conversations after switching to a new laptop
  • Resume a pure-dev workspace on another machine with files and sessions moving together

Best For

  • DSH users who frequently switch between multiple devices
  • Teams with sensitive conversations who prefer a private repo over a public cloud
  • Independent developers who want session sync without any extra cloud service