AI Agent Hub
Back to plugins
🖥️

dsh-github-ci

Client Updated 2026.09.03

Run the following command in DeepSeek Harness:

dsh plugin install knownasmobin/dsh-github-ci

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

Run dsh plugin install knownasmobin/dsh-github-ci in your DeepSeek Harness terminal to install this plugin, available at https://github.com/knownasmobin/dsh-github-ci

About this plugin

While you are writing code and running tasks inside DeepSeek Harness, your GitHub Actions status is stuck in another browser tab. Checking whether a pipeline passed, grabbing a few lines of failure logs, or clicking Rerun means constant context switching that breaks focus and keeps the agent out of the debugging loop entirely. dsh-github-ci moves the entire CI management surface into the Harness web UI: a floating dashboard shows pass, failed, and running summaries with status badges at a glance, and one click lets you cancel in-progress runs, rerun failed jobs, or jump straight to GitHub. Failed-step log tails are extracted automatically so you can inspect them without leaving the panel.

Equally important is the github_ci agent tool it registers. The assistant can list workflows and runs, inspect job details, pull log tails, trigger new workflows, and perform cancel or rerun actions on its own. When a build breaks, a single click on Fix with Agent composes a structured debug request containing run metadata and failure logs directly into the chat composer, eliminating the copy-paste ritual. Authentication supports both the OAuth device flow (no client secret required) and Personal Access Tokens, with credentials stored in the DSH credential store and reused across sessions; an expired token triggers a guided re-authentication prompt.

If you develop inside Harness, rely on GitHub Actions for CI, and want your agent to go beyond writing code—to read logs, kick off reruns, and join the debugging process—this plugin shrinks the distance between you and the pipeline from window-switching and copy-paste to a single sentence.

Use Cases

  • Monitor GitHub Actions pipeline status and failure logs in real time without leaving the Harness web UI
  • Let the agent autonomously read failed-step logs, trigger reruns, or cancel in-progress builds
  • One-click compose a structured debug request with run metadata and failure logs directly into the chat for agent-assisted troubleshooting

Best For

  • Independent developers who use Harness as their primary environment and depend on GitHub Actions for CI
  • Senior engineers who want their agent to go beyond code writing into log analysis and CI reruns
  • Teams that minimize context switching by keeping development and debugging in a single interface