dsh-git-graph

Tracing Git history inside a terminal chat usually means staring at a wall of commit hashes; when a branch split, when it merged back, and which worktree is parked where all have to be reconstructed in your head. dsh-git-graph turns that into a lane graph: press the ⎇ dock button next to the chat input, type a repository path, and the last few hundred commits unfurl as colored lanes—first-parent lines run straight, merge edges curve between lanes, and branch and tag labels sit right beside their commits. A strip beneath the graph lists every worktree with its branch or detached state, giving you a full picture of the working area at a glance.

For the agent, a visual is helpful but not enough. The plugin also registers two read-only tools, git_graph and git_worktree, that hand the same topology to the model as structured, one-line summaries—parents, refs, and worktrees all included—so the agent can reason over real commit graphs instead of guessing at log order when you ask which feature branch came from which commit or how many lines are pending merge.

Every Git invocation goes through a fixed-argv subprocess seam, and the plugin is strictly read-only: it never commits, checks out, creates, or removes anything. It is a good fit for developers who juggle multiple branches or worktrees in DeepSeek Harness and want the agent to participate in Git-topology conversations—open and view, no build step, no extra dependencies.