Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)

DeepSeek Open-Sources an Agent That Picks Up GitHub Issues and Writes Code on Its Own

DeepSeek has published the code for dsh-superagent, an agent that picks up tasks from GitHub on its own instead of waiting for them in a chat. For example, if an issue titled "Export crashes on empty date" appears in the repository, the agent opens a separate session, fixes the code, and opens a Pull Request, a set of proposed changes for a human to review. This is a prototype, not a production system, so it is best treated as an example of architecture.

AI-processed from TG: @ai_machinelearning_big_data (Machinelearning); edited by Hamidun News
DeepSeek Open-Sources an Agent That Picks Up GitHub Issues and Writes Code on Its Own
Source: TG: @ai_machinelearning_big_data (Machinelearning). Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceTG: @ai_machinelearning_big_data (Machinelearning) ↗
Editor-in-Chief
Key metric #1Accepts tasks from GitHub and Feishu, and only from authorized teammates
Key metric #2A web panel shows the tasks that need a human decision
Key metric #3Released under the MIT license, built with TypeScript and DeepSeek Harness

Most coding assistants work the same way: a developer opens a chat, describes a task, waits for a response, and copies the result. DeepSeek has released dsh-superagent as open source, flipping that scheme around. The agent monitors GitHub, where the team files issues, picks them up, edits the code, and opens a Pull Request, a request to merge the changes into the main branch that a person then reviews. None of this requires manually passing the task into a chat.

The project is an experimental system built on DeepSeek Harness, designed to automate development within a team. The code lives on GitHub in the deepseek-ai/dsh-superagent-prototype repository under the MIT license and is written in TypeScript.

How It Works in Practice

Imagine a task is filed in the repository: "Report export crashes on empty date." Normally, someone on the team takes the ticket, creates a branch, fixes it, opens a Pull Request, and posts in the discussion that it's done. Here, the agent handles most of that chain.

According to DeepSeek's description, it can do the following:

  • monitor GitHub events and messages in Feishu (a corporate messenger popular in China);
  • accept tasks only from authorized team members;
  • create a separate working session for each task, so tasks don't interfere with one another;
  • work with the code independently and prepare a Pull Request;
  • post the result back to the original discussion where the task came from;
  • show the tasks that need a human in a web panel.

A separate session per task is a sensible design. When an agent works through several tickets in a row within one context, it mixes up files and carries traces of an old fix into a new one. Isolation reduces this risk, although the original description offers no data on how much.

The Principle of Minimal Developer Attention

The authors frame the architectural idea as minimal developer attention and maximal useful autonomous work. The agent acts on request or on predefined rules and doesn't distract the team unnecessarily. Anything that requires a human decision goes to the web panel. Developers check it themselves rather than receiving a stream of notifications.

For product managers and tech leads, this is an interesting shift. The question is no longer which model writes code best, but how to fit the agent into the process: who has the right to assign it tasks, where it reports, and when a human steps in. The authorization checks and the panel for manual intervention suggest DeepSeek is thinking about exactly these issues.

Limitations and What to Do About Them

DeepSeek explicitly warns that this is a research prototype, not a ready production solution. One more detail: part of the project's code was also written by AI agents. That sounds impressive, but it is also a reason to read the repository more carefully before carrying anything from it over.

What the description doesn't include: benchmarks, statistics on accepted Pull Requests, comparisons with other agents, or data on the cost of runs. So, beyond your own experiments, there is currently no way to judge the agent's quality. The Feishu integration may also be inconvenient for teams that work in Slack or Telegram. You would have to write an adapter, which the MIT license permits.

What practitioners should do:

  • if you are building your own development agent, study how the project structures sessions, run rules, and the task panel; it is a ready-made example of structure;
  • if you want to try it, start with a sandbox and a repository without sensitive code, and give access to a narrow group of people;
  • do not let automatic Pull Requests land in the main branch without human review.

The release by itself promises no revolution: it is an open-source prototype. But it shows where the market is heading. Agents are moving out of the chat window and becoming team members, with task queues, access rights, and reports posted in the same discussions where people work. For developers, it is a chance to look at this architecture from the inside and borrow whatever fits their process.

Story

Key Questions Answered

How It Works in Practice?

Imagine a task is filed in the repository: "Report export crashes on empty date." Normally, someone on the team takes the ticket, creates a branch, fixes it, opens a Pull Request, and posts in the discussion that it's done. Here, the agent handles most of that chain.

What are the key details on The Principle of Minimal Developer Attention?

The authors frame the architectural idea as minimal developer attention and maximal useful autonomous work. The agent acts on request or on predefined rules and doesn't distract the team unnecessarily. Anything that requires a human decision goes to the web panel. Developers check it themselves rather than receiving a stream of notifications. For product managers and tech leads, this is an interesting shift.

What are the key details on Limitations and What to Do About Them?

DeepSeek explicitly warns that this is a research prototype, not a ready production solution. One more detail: part of the project's code was also written by AI agents. That sounds impressive, but it is also a reason to read the repository more carefully before carrying anything from it over. What the description doesn't include: benchmarks, statistics on accepted Pull Requests, comparisons with other agents, or data on the cost of runs.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…