dsh-plugin-git-status

When you are in the middle of a multi-turn conversation around a repository in DeepSeek Harness, checking the current branch or spotting unstaged changes usually means switching to a terminal, running git status, and switching back. dsh-plugin-git-status brings that information into the conversation surface in a strictly read-only manner: it never creates, modifies, or deletes any file and stores no data of its own, simply computing results on demand via git status and git log.

It offers two layers of capability. First, a Git status chip on the composer tool row shows the branch name and a clean/dirty summary; the change count is clickable and expands into a file list grouped by conflicted, staged, unstaged, and untracked, each row carrying the porcelain status code and rename origin. The panel auto-refreshes every 30 seconds by default, pauses while the browser tab is hidden, resumes with an immediate refresh when the tab becomes visible, and hides entirely when the workspace is not a Git repository. Second, the git_status model tool is callable through the standard tool pipeline and returns structured JSON including the branch, commits ahead/behind upstream, grouped change counts, the full file list, and the most recent commit; it also accepts an optional cwd parameter to inspect any directory. The refresh interval is adjustable at runtime from Settings or the plugin config file; setting it to 0 disables auto-refresh entirely.

It is best suited for workflows where you are iterating on the same repository over multiple rounds of reasoning, debugging, or code discussion inside Harness. Keeping the status always at a glance reduces context-switching interruptions and lets the AI read the working-tree state directly when needed, without extra prompts.