dsh-graft-plugin

A DeepSeek Harness plugin that puts graft — a prebuilt graph of every symbol, its file:line span, and who calls what — in front of both you and the model.

It does four things:

• A chip in the composer naming the graft index the current session is actually serving, whether it still matches the code, and how many tokens graft has saved in that repo.
• Five tools for the model — graft_ask, graft_grep, graft_callers, graft_skeleton, graft_map — resolved per session, so one dsh can serve several workspaces at once.
• /graft to build or rebuild the index, and auto-rebuild after the model edits files.
• A graft viz button that opens the graph as a tab in dsh-better-sidebar.

Install

dsh plugin --profile web add dsh-graft-plugin
dsh --profile web

The install also puts the graft CLI (@nanonets/graft) on your PATH — every tool here shells out to it, so a plugin without it can do nothing. If your global npm prefix needs elevation the postinstall says so and prints the one command to run by hand:

npm install -g @nanonets/graft

Then index a repo once:

cd <your repo>
graft build

The sidebar tab

The graft viz button needs dsh-better-sidebar mounted. It ships as a dependency of this plugin, so it is already downloaded — but dsh only mounts what the profile lists:

dsh plugin --profile web add dsh-better-sidebar

Skip it if you do not want the tab. The chip, the tools, /graft and the auto-rebuild all work without it; the button just reports that the sidebar is unavailable.

This plugin does not insert a dsh-better-sidebar row itself, on purpose. That package's own bundle row carries a guard that disables it when another enabled row already mounts the same package. A second row with a different id makes that guard circular, and the losing outcome is your existing sidebar silently disabling itself. One explicit command is worth more than that risk.

What you get

The chip

Sits in the composer next to the model name:

● graft · my-repo          in sync
◐ graft · my-repo          syncing
▲ graft · my-repo          stale

Hovering (or clicking) opens a card with the resolved root, node and edge counts, freshness, the running saved-token tally, and the graft viz button.

The root is resolved from the session's own workspace, not from wherever dsh was launched. That is the whole reason this exists rather than the graft mcp server: graft mcp resolves its repo once, from its own working directory at startup, and nothing can re-point it afterwards. Launched from a home directory it answers "no graph found" for every workspace you open.

The visualiser

The graft viz button opens the graph as a tab in dsh-better-sidebar. The context view lays out the whole graph:

The code view drills into a single file — what it contains, what it depends on, what depends on it:

The tools

tool	what it answers
graft_ask	"how does X work" / "where is Y" — ranked hits with code inlined at exact file:line
graft_grep	every occurrence, grouped by enclosing symbol (graft_ask is top-N and misses some)
graft_callers	who calls a symbol, what it calls, or the full blast radius before a rename
graft_skeleton	a file's whole API in ~200 tokens
graft_map	orientation in an unfamiliar tree

None of them take a boolean parameter. They take string enums instead — detail: "full" rather than full: true — which reads better to a model and sidesteps a real failure mode on some OpenAI-compatible servers, where a tool call that sets a boolean is emitted as literal <tool_call> text and never runs.

/graft

• /graft — build the index, or rebuild it if one exists
• /graft status — what the chip knows, as text
• /graft deep — a full rebuild

Auto-rebuild

After the model writes or edits files, the index is rebuilt in the background, debounced so a long turn does not rebuild on every keystroke. This reuses graft's own sync runner rather than reimplementing it, so it cannot drift from what graft build does.

Configuration

All optional, all on the plugin's row in your profile's cordis.patch.yml:

- id: graft-status
  name: 'dsh-graft-plugin'
  config:
    cwd: 'C:/path/to/repo'   # pin to one repo instead of resolving per session
    tools: false             # drop the graft_* tools, keep the chip
    command: false           # drop /graft
    promptSection: false     # stop telling the model to prefer graft
    autoBuild: false         # stop rebuilding after edits

Requirements

• dsh 0.1.2-rc.1 or newer, web profile
• Node 22+
• the graft CLI on PATH (installed for you; see above)

Development

npm install
npm test           # portable: builds a synthetic graft index in a temp dir
npm run test:live  # drives the real graft CLI against a real repo

npm test needs no graft index and no graft install anywhere on the machine. The one suite that does build a real index skips itself, loudly, when graft is absent — a missing CLI is a setup state, not a defect.

Licence

MIT