omdsh-status

Working across several repositories inside the DeepSeek Harness Work window raises one question on every conversation switch: which repo am I in, on which branch, and is the tree clean? omdsh-status pins the answer into the conversation header. It shows the workspace title, the checked-out branch, and whichever of ahead/behind, staged, modified, untracked, and conflicts are non-zero. Conflicts are drawn in the alarm colour; a clean tree simply shows the branch. A tooltip carries the full directory, every count spelled out in words, and the reason figures are stale when a refresh failed.

Two design choices deserve mention. First, the project name is derived entirely on the browser side from the already-live workspace and session lists, with nothing guessed or stored; git counts are resolved by the host process parsing git status --porcelain and returning only the handful of numbers the UI draws, so no path list or diff ever crosses the trust boundary. Second, while a conversation is still blank and Harness hides the entire header row, the plugin stands in from the frame-wide floating layer at the very same pixel position, then steps down the moment the header reappears so the two never render together. When a mode system classifies the conversation as a chat, both the readout and the poll stop, because a chat is not a directory anyone chose.

It is built for developers who maintain several Git repositories simultaneously in the Harness web GUI and would rather glance at the header than run git status again, and for teams that mix chat and work in one profile and want the plugin to hide itself automatically where no project applies. There are no settings and no preconditions; install it alone and it boots and works.