AI Agent Hub
Back to plugins
⚙️

dsh-agent-project-sync

Workflow Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install Harzva/dsh-agent-project-sync

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

Run dsh plugin install Harzva/dsh-agent-project-sync in your DeepSeek Harness terminal; the plugin source is hosted at https://github.com/Harzva/dsh-agent-project-sync . After installation, restart the target profile to activate it.

About this plugin

The same project often starts in Codex, continues in Claude Code, and eventually lands in DeepSeek Harness. Each agent stores its session metadata in a different format, leaving project directories scattered across separate config folders with no shared understanding. dsh-agent-project-sync bridges this gap by reading only the working-directory path from each agent's session files, deduplicating by real path, and registering every discovered project as a native DSH Workspace without copying source code, migrating chat history, or creating a second set of files.

The plugin ships with built-in adapters for Codex and Claude Code. Discovery is strictly read-only, limited to the cwd field in the first 128 KiB of each JSONL session file, and no chat content is ever read or stored. The confirmed list is written to a shared projects.json manifest and pushed through DSH's workspaceRegistry API. All mutating operations default to dry-run mode; a real write requires explicit confirmation. Syncing only creates or reuses Workspaces and never deletes existing Workspaces, sessions, or project directories. A local CLI is also provided so other agents can read the manifest or add entries manually.

If you switch between multiple local agents on the same machine and want DeepSeek Harness to serve as a single entry point for your projects, this plugin turns what used to be a tedious manual exercise into one safe, repeatable step, without touching any of your existing data or files.

Use Cases

  • Switching between Codex and Claude Code on the same project and wanting DSH as the single entry point for all working directories.
  • A local machine has accumulated many agent sessions that need to be discovered and registered as native DSH Workspaces in one step.
  • Multiple agents working on different modules of a codebase, with a shared manifest available for CLI queries or tooling integration.

Best For

  • Project engineers who develop with multiple local agents such as Codex and Claude Code.
  • Power users who standardize on DeepSeek Harness and need centralized Workspace management.
  • Advanced developers running multiple concurrent agent sessions on a single machine.