AI Agent Hub
Back to plugins
🧩

dsh-git-forge

admin-security Updated 2026.08.18

Run the following command in DeepSeek Harness:

dsh plugin install thirsty5034/dsh-git-forge

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

Run dsh plugin install thirsty5034/dsh-git-forge in the DeepSeek Harness terminal, or install from the source repository at https://github.com/thirsty5034/dsh-git-forge; after installation, restart DSH web and hard-refresh the browser to activate.

About this plugin

When your Agent runs git fetch and git push on a daily cadence, credentials tend to scatter across environment variables and local configs with no per-project granularity, no host-level interception, and no guarantee that a token stays out of the model context. dsh-git-forge closes that gap by adding a unified account library and push-policy manager to the dsh-better-sidebar.

The plugin supports GitHub, Gitea, GitLab, Gitee, and Bitbucket, keyed by workspace cwd so each project carries its own grant list. A built-in Push Guard hooks into the Host layer to block git push, git remote add, and set-url commands that target non-granted hosts before they reach the network. Tokens are written to $DSH_HOME/git-forge/secrets.json with 0600 permissions; the Agent retrieves them through a Host-only credential helper, so they are available when needed yet never appear in model context or tool-result output.

If you let your DSH Agent pull and push code, juggle accounts across multiple Git platforms, and want credentials, grants, and safety boundaries in a single sidebar panel, dsh-git-forge gives the Agent a clearly defined perimeter to work within, reducing both day-to-day friction and the blast radius of a misconfigured push.

Use Cases

  • Restrict Agent git push to only approved hosts per project, with Host-level interception of non-granted remotes
  • Bind different accounts to different projects across GitHub, GitLab, Gitee, and auto-resolve credentials per workspace
  • Let Agent fetch and push via HTTPS Git while tokens stay strictly outside model context

Best For

  • Developers whose DSH Agent runs git fetch and push as part of a daily workflow
  • Ops or security leads who manage credentials across multiple Git platforms at the Host layer
  • Teams that want the Agent to operate inside a clearly defined safety boundary and minimize mis-push risk