Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

DeepSeek tests Super-agent with separate routing and coding workers

AI summary

According to a commentary report, DeepSeek published a prototype called Super-agent in which one session routes incoming requests while separate worker sessions perform coding. In a simulation of roughly 300 messages and 20 work requests per run, with five runs per configuration, the router-and-worker setup recorded median and p95 completion times of 12.4 and 15.7 minutes, compared with 20.4 and 29.5 minutes for a neutral-prompt single-session baseline. The reported 47% p95 reduction is not cleanly attributable to the architecture: the baseline never invoked its subagent tool across five runs, while a delegation-first prompt reduced median time to 13.8 minutes without improving p95, which remained 29.0 minutes. Cache-read tokens rose from 6.1 million to 23.2 million per run, although this is not equivalent to total spend. Worker directories are not operating-system sandboxes, and commands run as the user's OS account.

In-depth insight

The prototype provides a concrete multi-session pattern for coding-agent design, while its baseline, cache-read and sandboxing caveats show why the reported latency improvement needs careful assessment before adoption.

DeepSeek published a prototype of what it calls a Super-agent: one session routes incoming requests, separate worker sessions do the coding. The interesting part is the ablation, not the architecture diagram. In a simulation of roughly 300 messages and 20 work requests per run, five runs per configuration, the router-and-worker setup finished at 12.4 min median and 15.7 min p95. The single-session baseline with a neutral prompt sat at 20.4 and 29.5 min, so about a 47% cut at the tail. Caveat: that baseline never once called its subagent tool across the five runs. A delegation-first prompt brought it to 13.8 min median, with p95 unchanged at 29.0. The cost side is the part I would want before adopting the pattern: 23.2M cache-read tokens per run against 6.1M. Cache reads are not total spend, but 3.8x is not noise. Also worth noting: worker directories are not a sandbox. Commands run as your own OS user. submitted by /u/docdavkitty [link] [comments]

#DeepSeek#Super-agent

Original · 1 min readRead the original
Group chat

No comments yet. Start the conversation.