The DeepSeek Harness team released dsh-superagent, an MIT-licensed research prototype, MarkTechPost reports.
How it works
- It watches one GitHub repo (and optionally Feishu). When an allowed person asks, it opens a “Ticket”
- A long-running Router handles conversation and dispatch; each Ticket runs in its own isolated Worker session and directory, and results come back, often as a PR
- A local web panel shows only what needs a human
- v0.1.0, TypeScript, one commit. Needs Node.js 22.19+ or 24+, git, Python, tmux and the GitHub CLI
The idea: people can only follow 3 to 5 sessions at once, so human attention, not the model, is the bottleneck. In DeepSeek’s simulation, p95 task completion was 15.7 minutes vs 29.5 for a single-session agent.
Why the garlic
It was tested only on synthetic messages and simulated tools. Real coding quality wasn’t measured.
My take
Router-worker is a nice pattern, but an agent that acts on GitHub mentions needs a tight allow-list and workers with as little access as possible.
Review before you install: read the release notes yourself, back up your config, and try new versions somewhere you can afford to break first.
Isolate it: if you try this, run it inside a disposable VM with no access to your real accounts, keys or files, and snapshot before you start.
God Bless, and Needs Garlic!
