Vizuara logoVizuara AI Labs
Vizuara · Run on 4 November 2026

DeepSeek's prototype, actually running.

DeepSeek published its Super-agent prototype under the MIT licence. We installed their code unchanged, pointed it at a small repository with a real bug, and recorded 45 minutes of what it did. This page replays that run.

What is real: their code, every decision, ticket, commit, pull request and restart below. What is staged: the bug and the issues are ours, the Before screen is a simulation, and a rule named "bugs" was written by us. Limits we hit: it ran in observe mode, so proactive work was recorded and not carried out; two mentions were silently missed; the container kill was tested only with no uncommitted edits at stake. DeepSeek calls this a research prototype, not an official product, and says it differs from their internal version. Vizuara is not affiliated with DeepSeek.

[01] The video

Before and after, in about two minutes

[02] Before

Before: you are the Router.

You open a session for each task, paste in what it needs, and remember what each one knows. In DeepSeek's experience, a person can follow only 3 to 5 active sessions at once.

+ New session
Review #412you pasted in the CI log
Release notesopened by you
Android login bug?opened after scrolling the group
Flaky testyesterday
Onboarding copyyesterday
Here is the CI log for PR #412 and Ankit's review comment. Why does it fail? [pasted 400 lines]
Reading the failing test...
wait, does this also explain Priya's login bug?
I don't have any information about Priya's login bug in this session. Could you share the details?

Nothing connects these sessions except you. A simulated screen, but you have probably lived it.

[03] After: the real run

After: tickets, not tabs.

Press Play. On the left is what appeared on GitHub. On the right is what the prototype recorded, from its own database, reworded into plain sentences with the values unchanged.

GitHub, as the team saw it
from the prototype's own records
0events
0dropped by code
0judged by a model
0tickets opened
0agent replies
[04] The four properties

Each property, in this run

Continuous

A comment on the pull request changed the request. The agent acknowledged it within a minute and pushed a second commit to the same pull request, then reported back on the issue.

Productive

Two issues ran at the same time in separate directories, and each became its own pull request. The first bug went from mention to open pull request in about two minutes.

Proactive

Observe mode only. On an issue nobody mentioned it to, it recorded that it would accept under the team's rule, and on a musing it recorded ignore. It took no action, by design of the mode we ran.

Persistent

We restarted the service mid-work and, separately, killed the container and restored from its volume. Both times a new assignment picked the work up, and no comment was repeated.
[05] How it was built

How we ran it

DeepSeek Harness 0.2.1-rc.3 and the dsh-superagent-prototype code, in a Modal container, never on a personal machine, because its workers run with full access to the machine they are on. Workers used DeepSeek V4 Pro and the main session used V4.1 Flash, through OpenRouter. We switched off session-log upload and telemetry. Nothing was merged.

What did not work: mentions in the bodies of two issues were silently missed, probably a timing race in its GitHub polling, judging from its code. Comments and the receive-all switch worked. We also needed a workaround to sign its GitHub tool in. Its subagent feature was not exercised.

[06] Who wrote this
Vizuara logo

Built and written by Dr. Raj Dandekar and the team at Vizuara AI Labs, for a webinar on 4 November 2026. The design it follows is explained in full at superagent.vizuara.ai.

We teach with love, care and passion. If you want to build agents like this end to end, our live cohort Agentic Systems Engineering takes you from the LLM to retrieval, tools over MCP, the agent harness, workflows and evals, on a real business system. It is open to engineers moving into agentic AI roles and to enterprise teams.