AI Agent Hub
Back to plugins
🖥️

dsh-git-branch

Client Updated 2026.08.16

Run the following command in DeepSeek Harness:

dsh plugin install hanyueqiang/dsh-git-branch

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install hanyueqiang/dsh-git-branch in DeepSeek Harness to install this plugin (source: https://github.com/hanyueqiang/dsh-git-branch), then restart the profile and refresh the page to activate it.

About this plugin

Writing in the DeepSeek Harness Web UI usually hides your git branch behind another terminal window. You just switched to feature/auth in the editor, glance at the composer area, and see only the mode and plan controls — which branch you are actually on is a guess. dsh-git-branch puts that answer in plain sight: a slim chip sits right after the access-mode and plan buttons, appears only when the workspace is a git repository, and disappears cleanly otherwise.

The chip is not a static snapshot. It refetches the branch on mount, on session or workspace switch, when the window regains focus, when the tab becomes visible, and via a 60-second safety poll. Clicking the chip triggers an immediate refresh. For detached HEAD, worktrees, and submodules, the host walks up from the session working directory to the nearest .git and parses HEAD, so what you see is always the commit you are actually on.

If you drive conversations from the DSH Web UI and hop between branches or worktrees several times a day, this one-second glance before you start typing removes the small but constant interruption of switching windows to run git branch. It ships as a light bundle that activates with the host on next boot — no extra configuration needed.

Use Cases

  • Confirm the active branch at a glance while switching branches in the DSH Web UI
  • Avoid branch confusion when developing across multiple git worktrees
  • See which commit the workspace is on during multi-window collaboration
  • Verify the exact commit when recovering from a detached HEAD state

Best For

  • Engineers who drive development through the DeepSeek Harness Web UI daily
  • Developers who hop between multiple git branches or worktrees frequently
  • Developers who want fewer window switches and tighter context in the web interface