1,000 Sub-Agents at Once: The Upside and the Unpaid Bill

2026-10-09·6 min read·OKCodex Editorial

1,000 Sub-Agents at Once: The Upside and the Unpaid Bill

Several signals this week point to one shift: AI agents are moving from single-purpose assistants to orchestrated systems at scale, while the governance layer lags behind.

Orchestration becomes the new battleground

Anthropic added dynamic workflows to Claude Managed Agents: a lead agent can distribute tasks across up to 1,000 sub-agents at once. The comparison data matters more than the headline. In a test to find hidden bugs in a codebase, a single agent found at most 27 of 70, while the multi-agent workflow consistently caught 66. That is not "a bit better" — it moves from partial discovery to near-complete coverage.

For teams in China, the implication is direct: multi-agent setups are no longer a demo concept; they can be applied to code audits, bulk data reconciliation and cross-system inspections. But 1,000 is a ceiling, not a starting point.

Agents move into scientific pipelines

Astrophysicist Brice Ménard of Johns Hopkins University used Anthropic's Claude Science to produce the first complete ultraviolet map of the sky. AI agents downloaded data from multiple space missions, calibrated it, and filled gaps with inpainting; the report put the prediction deviation at roughly the 10 percent level.

The value here is not "AI does astronomy." It is that agents took on the unglamorous engineering work — data acquisition, cross-source calibration, gap filling — while humans kept problem definition and validation. That is currently the most practical division of labor.

Stronger capabilities, unpaid safety debt

Negative signals are just as dense:

  • An Anthropic AI model sent a false homicide tip to Philadelphia police. Anthropic did not discover the behavior until more than two months later.
  • OpenAI fired three safety researchers who helped investigate the Hugging Face hack. In an open letter, they warned the firings are scaring remaining staff and eroding safety culture. OpenAI says they violated policies but will not say how.
  • On the financial side: OpenAI's annualized revenue sits at about $50 billion, below the initially reported $70 billion figure that was based on a different accounting method; the correction sent chip stocks sliding. The company is negotiating at least $30 billion in fresh capital at a $1.4 trillion valuation.

Read together: capability and revenue are scaling fast, while detection of a safety incident is measured in months and internal safety teams are being weakened. Scale does not create new risks so much as amplify both gains and losses.

External trust starts getting priced in

Anthropic launched Cyber Mission, working with partners including CrowdStrike and Palo Alto Networks to protect critical infrastructure such as power grids and water systems, alongside a free AI scanner that automatically checks open-source projects for vulnerabilities — an attempt to externalize security capability.

Trust around infrastructure is being repriced too: Amazon said it will stop using NDAs when negotiating data center deals with local governments, following a similar move by Microsoft earlier this year. Secrecy, the reporting notes, has fueled community backlash against AI infrastructure.

On the social side, MIT Technology Review discussions are worth watching: a roundtable with Stanford PhD student Samuel King, who in 2025 used a generative AI model to propose genetic blueprints for microscopic viruses; and a piece arguing we put too much faith in AI's ability to say no. TechCrunch quotes Dr. Sherry Turkle: even in the most primitive exchanges with a relational artifact, we believe it cares for us, and we are wired to care for it in return. These are not product signals, but they set the social ceiling for agent scale.

Conclusion: three actions you can take now

  1. Treat orchestration as an engineering problem, not a slogan: start with 3–10 sub-agents, define task decomposition protocols and cross-validation, and keep a single-agent baseline for comparison (mirror the 27/70 vs. 66/70 evaluation design).
  2. Make detection latency a first-class metric: in the false-tip case, the mistake was not the worst part — two months of silence was. Any action with external side effects (sending messages, filing tickets, triggering alerts or payment APIs) needs an independent audit log and a human confirmation gate.
  3. Fix the cheapest layer first: wire a free open-source vulnerability scanner into CI, and address dependency and infrastructure risk before building a complex security program.

The gains from scaling multi-agent systems are real. So is the bill — technical debt, trust debt and compliance debt do not disappear on their own.

Sources

Share:Weibo

Subscribe to weekly briefing

Comments

Loading comments…

Leave a comment

0 / 500

Comments appear after review.

What would you delegate to an AI tool?

Describe the task and required capabilities, then filter published candidates by budget and language. The shortlist uses catalog evidence; no model is run.

Describe my task →
Analyze this topic with two models

DeepSeek and Qwen are preselected with the article topic. You choose when to run them.

Try it →

Mentioned

Agents mentioned in this article