dsh-hooks-git-ai
DeepSeek Harness 插件，可使用 git-ai 记录代理编辑（agent-v1 检查点）
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-hooks-git-ai@0.1.1Hooks Git Ai 以 dsh-hooks-git-ai 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A DeepSeek Harness plugin that records which files the agent edited, with which model, and in which session into git-ai. It listens on the harness's tools/pre-execute / tools/post-execute interception points, translates each relevant tool call into git-ai's generic agent-v1 checkpoint payload, and invokes git-ai checkpoint <preset> --hook-input stdin with that JSON on stdin. git-ai itself is never modified; after the agent commits, git-ai writes the attribution into git notes and reports ai_additions/ai_accepted per tool-model pair.
npx @deepseek-ai/dsh@latest) — the plugin peer-depends on the official @deepseek-ai/* packages it ships with.PATH (or point gitAiPath at it).The package ships as a profile bundle: installing it and activating the patch is one command.
dsh plugin --profile web add dsh-hooks-git-ai
dsh plugin forwards to pnpm inside your profile directory and auto-activates the bundle because the package declares dsh.bundle. Without the bundle mechanism (or to load it in a custom profile), add the row to your profile's cordis.patch.yml:
- dsh-hooks-git-ai:
gitAiPath: git-ai
agentName: deepseek-harness
import type { Config } from 'dsh-hooks-git-ai'
const config: Config = {
gitAiPath: 'git-ai', // optional: git-ai executable (bare name resolves through PATH)
agentName: 'deepseek-harness', // optional: `agent_name` stamped on every checkpoint
model: '', // optional: explicit model; empty falls back to agent.options.model
checkpointPreset: 'agent-v1', // optional: the git-ai generic-integration preset
timeoutMs: 10_000, // optional: git-ai invocation timeout
trackBash: true, // optional: emit pre/post shell checkpoints for bash/pwsh
}
| Harness point | Tool | git-ai payload |
|---|---|---|
tools/post-execute (success) | write, edit | ai_agent with edited_filepaths from file_path |
tools/post-execute (success) | str_replace_editor (not view) | ai_agent with edited_filepaths from path |
tools/pre-execute | bash, pwsh | pre_shell_command with command and tool_use_id |
tools/post-execute | bash, pwsh | post_shell_command with command and tool_use_id |
Payload identity fields: repo_working_dir is the session cwd (falling back to the process cwd), agent_name is config.agentName, model is config.model when set else agent.options.model (else ''), and conversation_id is the session id. Relative file_path / path values are resolved against the session cwd into absolute paths; absolute values pass through unchanged. str_replace_editor view commands are read-only and never attributed.
A failed edit (result.isError === true) emits nothing; a failed bash command still emits its post_shell_command so the before/after pair closes. Bash tracking keys on the tool callId, so pre and post checkpoints share tool_use_id.
git-ai is an optional external dependency. A missing binary, nonzero exit, timeout, or executor rejection is logged as a warning and never propagated: the tool call and the agent turn proceed exactly as if the plugin were absent.
# 1. start the harness with the plugin loaded
dsh web
# 2. have the agent edit files in a git repository
# 3. check git-ai received the checkpoints
git-ai status --json
# 4. commit
git add -A && git commit -m "test"
# 5. check attribution
git-ai stats HEAD --json
pnpm install
pnpm test # vitest, 100% coverage on src/
pnpm typecheck
pnpm build # emits lib/ for publishing
pnpm build
pnpm publish --access public
ai_agent checkpoint. git-ai attributes a file's changed lines against HEAD or the last checkpointed value, so uncommitted edits made to the same file before the agent's edit (e.g. by the user) are also attributed to the agent. A pre-edit human checkpoint before each edit tool would isolate them; the bash pre/post pair already provides this isolation for shell commands.pre_shell_command is possible. If a bash tool is denied or canceled between pre and post, the pre snapshot stays open and later changes to the same files are treated as untracked by git-ai until the next checkpoint.timeoutMs) before the tool result settles.MIT