DeepSeek Open Sources a Proactive Coding Agent and Warns Users to Fence It In
DeepSeek has published dsh-superagent, an MIT-licensed research prototype that watches GitHub and Feishu and returns pull requests unprompted. Its own docs say the workers run with full access to the operator's account and call for a dedicated OS user.
DeepSeek has open sourced a coding agent that does not wait to be summoned, and its own documentation tells you to give it a computer account of its own.
The project is called dsh-superagent. DeepSeek's Harness team published it on GitHub over the weekend under an MIT licence, alongside a long design essay titled "Exploring Super-agent Design: Towards a More Autonomous Agent System". The repository describes it as a proactive coding agent for a single GitHub repository, built as a bundle for DeepSeek Harness. It listens to GitHub and, optionally, to Feishu, the workplace chat app. When someone on an approved list asks for work, it opens a ticket, tackles the job in its own session and directory, and replies in the original thread, often with a pull request. A web panel flags whatever needs a human.
DeepSeek frames the philosophy as taking "as little human attention as possible" while giving as much value as possible. In practice that means a quiet agent. According to the project's docs, it acts only when asked or when a rule the team wrote allows it, and it speaks only when a person must act or can use a result. Work nobody requested starts in a mode that merely records what the agent would have done. That is a sensible leash for software that watches a whole team's conversations.
It also lands squarely on turf held by Anthropic's Claude Code and OpenAI's Codex, according to coverage from the South China Morning Post and Digital Trends. The SCMP reported that the design aims to cut the effort humans spend coordinating several agents and checking on their progress. Under the hood, the repository splits the job in two: one long-lived router session that handles incoming messages and decisions, and a separate worker session for each ticket.
Now the part DeepSeek deserves credit for stating plainly. The agent's workers are not sandboxed.
"A worker can execute programs by path and read the operator's home directory. For isolation, use a dedicated OS account containing only the agent's credentials." DeepSeek deployment guide
The deployment guide says both agent presets run with "danger-full-access" as the operator's own OS user. The execution doc adds that worker sessions run commands without approval, and that the wrappers and directories are defaults, not a security boundary. Translation: if you wire this to a repository where strangers can open issues, you are betting on the allow list and the prompts. DeepSeek's setup notes also require a separate GitHub user account for the agent, and say a GitHub App will not work because the tool reads that account's notifications.
Developers are clearly curious. GitHub showed more than 13,800 stars and about 1,460 forks on the repository when I checked on Monday evening, only days after it appeared.
What DeepSeek has not given us is a scoreboard. I found no benchmark figures in the repository or its README, and the coverage I read cites none. Digital Trends was blunt about it: the announcement does not show how reliable Super-Agent is on complex development work, or how ready it is to run at scale. Its verdict was that this is no reason to uninstall Claude Code or Codex just yet.
DeepSeek is just as upfront about the code's status. The README calls it a "research prototype for reference only, not an official DeepSeek product" and says much of the engineering was done by coding agents. It warns the code may contain bugs and inconsistent style, differs from DeepSeek's internal version, and leaves some designs from the essay unimplemented, listing them as directions for future development.
So treat this as a blueprint with working parts, not a rival product. It matters because DeepSeek is spending its attention on the harness around the model, not just the model itself. This site covered the company's last major model drop when it released V4 Pro in August. This time the interesting question is not how smart the model is. It is how much of a team's day-to-day work you are willing to let an agent see, touch and answer for.

