AI Agent Hub
Back to plugins
dsh-jj-vcs preview

dsh-jj-vcs

Workflow Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install bingfengaaaaa/dsh-jj-vcs

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

Run dsh plugin install bingfengaaaaa/dsh-jj-vcs inside DeepSeek Harness to install the plugin; the source repository is at https://github.com/bingfengaaaaa/dsh-jj-vcs

About this plugin

When several AI agents edit the same repository concurrently, the traditional Git workflow becomes a coordination bottleneck. Every mutation requires juggling a staging index, branch checkouts, and raw Git commands, and nothing enforces who owns which change, when a handoff is valid, or whether a bookmark has actually been reviewed before pushing. dsh-jj-vcs plugs Jujutsu into DeepSeek Harness so that each agent receives its own external workspace and a durable change ID. Editing files and inspecting the diff no longer need a separate add step, and the change ID stays stable across rebases and description edits while the commit ID still pins an exact snapshot.

On top of those JJ primitives the plugin adds DSH-specific rules: it records operation-log IDs before and after every task so recovery is always possible, verifies task-to-agent ownership at handoff, rejects conflicts and divergent changes, and separates the four permission levels of read-only inspection, task-local edits, shared local history, and remote-visible actions. Remote publication is limited to the exact bookmark that passed review, and Windows symlink or workspace-alias edge cases are detected automatically.

The plugin is aimed at teams that already run multi-agent coding, refactoring, or test pipelines inside DeepSeek Harness and want Git to stay as the repository backend and GitHub as the hosting layer, while every history-changing command is executed through Jujutsu. You get deterministic agent isolation, auditable before-and-after receipts, and crash-safe recovery without losing compatibility with the existing Git ecosystem.

Screenshots

Use Cases

  • Isolating concurrent agent edits with per-agent workspaces and handoff ownership verification
  • Recording operation-log IDs before and after tasks to audit changes and detect divergence
  • Restricting remote publication to only the reviewed bookmark to prevent unauthorized pushes

Best For

  • Developers orchestrating concurrent multi-agent coding or refactoring pipelines in DeepSeek Harness
  • Team leads who want Jujutsu to replace Git staging for safer agent concurrency
  • Infrastructure engineers who care about audit trails, crash-safe recovery, and Windows symlink correctness