nightosong/gord-dsh-worktree

gord-dsh-worktree is a native plugin built specifically for DeepSeek Harness (DSH), packaging git worktree management as an integrated layer of the host's bundle stack. Installation is performed through the official dsh plugin --profile web add github:nightosong/gord-dsh-worktree command, and the package's manifest declares dsh.bundle.patch, so the CLI mounts it onto the profile's bundle stack on its own. A dsh web restart (or reload once the bundle is already on the stack) then surfaces five agent-callable tools — worktree_list, worktree_create, worktree_status, worktree_remove, and worktree_prune — alongside a Worktrees section in Settings.

The plugin targets DSH users who need to keep parallel investigations of the same repository from polluting each other. From the New Session row, a working-location picker offers exactly two choices: stay in the Current worktree, or pick "New worktree" and have an isolated checkout plus a freshly cut branch created and a session opened inside it in one atomic step; the right sidebar's Changes tab then shows uncommitted diffs scoped to that session's own directory. Settings → Worktrees centralises the live worktree list, archive management (per-row Unarchive, single delete, Delete all), and a Create form, while a double-click on a sidebar row renames a session without a menu. A worktree made mid-conversation does not adopt itself as a workspace, which avoids adding unsolicited sidebar entries.

It depends on DSH 0.1.5-rc.1 or newer and is plain ESM with no build step: lib/index.js is the host half, lib/client.js loads through window.__ModuleLoader__, and lib/service.js plus lib/worktree.js hold the git logic they share. Local checkouts must symlink @deepseek-ai/schemastery, dsh-tools, dsh-settings, and cordis into node_modules/@deepseek-ai/, since the host half resolves from its own directory while DSH peers resolve from the profile; GitHub or npm installs need none of this. The main worktree cannot be removed, dirty worktrees require force (because --force would also drop untracked files), locked worktrees are reported rather than silently unlocked, branch names pass git check-ref-format, paths are passed as positional git arguments to avoid flag injection, and the HTTP mutating route accepts only same-origin and loopback callers. Deleting archived sessions is the sole irreversible operation, guarded by an explicit confirmation and refused for any session still running. The project ships under the MIT license, with npm test running both smoke suites (host-side against a throwaway git repo, client-side against a minimal React runtime) and no test framework to install.