Posted by acossta 9 hours ago
A lot of evidence for this.
- Adaptive Auto-Harness: Sustained Self-Improvement for Agentic System Deployment on Open-Ended Task Streams (https://arxiv.org/abs/2606.01770) talks about multi-agent, role-based adaptive harnesses collaborating on non-homogeneous workstreams
- team-solve (https://github.com/guregodevo/memdoor/tree/main/examples/wor...) team of small models beats Fable on LiveCodeBench
- Agensh paper (https://arxiv.org/html/2609.26781v1) also talks about "role-playing agents to study autonomous cooperation"
All show that role-based, multi-agent setups improve performance.
We are constantly improving/evolving /teamwork and pushing those changes for external users. Will also post more about improvements and details for building teams of agents dynamically as Antigravity blog posts soon. Stay tuned!
Also I added a list of examples here: https://x.com/mirrokni/status/2121351383236436247?a=ma9UPZg_... and https://lnkd.in/p/esVTpR6p. I'll add a comment with examples as well.
Both take a long time. It used to be that antigravity was much faster than codex, but with recent releases it is substantially slower.
Inspecting the agents communication in teamwork, there seems to be an overwhelming amount of ceremony: BRIEF.md, specialized roles, multiple rounds of checking. Is all that necessary? Codex also uses agent “swarms” but unless they’ve hidden how the sausage is made, it doesn’t seem so heavyweight.
* Math Open Problems & Formal Verification: Reporting 10+ open math and CS theory problems solved including 50M-line Lean 4 proof of Courtade–Kumar conjecture plus progress on several open problems in quantum query complexity, Tarjan's Deque Conjecture.
Also autonomous Lean formalizations of the Weil (1.8M lines), Birkhoff, and 3D Bochner–Riesz conjectures via Teamwork-LEAP, plus updates on Deep Review for STOC’27.
* Chemistry & Discovery: 95% top-1 exact match on NMR molecular structure elucidation (nearly 2× single-agent). Also empowering Nuclear Fusion and Quantum algorithm results as well autonomously generating a CausalAnalyst Benchmark. In addition, we show how /teamwork can start from Alphazero paper, implement a competitive go game, and autonomously improving it by playing with KataGo to get to the medium Elo level.* Several Systems, TPU Kernel, & Infra: * Clustering 1-Trillion-edge graphs on FarArray and RDMA (up to 180× faster), * 800K-line Zircon & 170K-line libgav1 safe Rust rewrites (20–30% faster than C++/ASM), * 4.09× JAXBench TPU kernel speedups with DuoDiscover, * Google internal examples: surpassing 1 PiB fleet memory savings, and 24% fewer Borg TPU preemptions for Borg Scheduling.
Antigravity as a harness feels very behind. There's not even any auto mode. And they announced /goal long after I ever felt the need to use it in CC or Codex.
Seems likely that the people who maintain Antigravity don't use Antigravity to do it. It has too many rough edges that would be trivial to fix if someone actually noticed them.
> For n-bit integer multiplication, multi-agent campaigns simplified the theoretical Turing-machine bound below n log n, while a separate effort gave a new O(n log n) algorithm on a single two-dimensional grid whose C implementation matches the GNU Multiple Precision Arithmetic Library (GMP) bit-for-bit up to a billion bits.
Is "simplify a bound" a normal wording? What does it mean to simplify a bound?
[0]: https://antigravity.google/blog/teamwork-when-ai-becomes-a-r...
"In under eight days, the engine gained roughly 2,600 Elo, reaching 1,885 Elo, placing it between KataGo at 16 and 32 visits per move."
The pattern seems to be pervasive at Google. Too much Ai, not enough human, top-down orders
I still don’t understand why they don’t use their massive market position to give more value to Google workspace customers to have more access to their models for teasing higher value plans. The existing credits timeout before they even build a playwright scraper.
I wonder if they optimised the C++ it would actually have more speed benefits than the Rust alternative. Only they can't claim it's a Rust rewrite like every other company at the moment.