Advancing science and engineering with Antigravity's /teamwork

acossta 188 points 40 comments November 14, 2026
research.google · View on Hacker News

Discussion Highlights (11 comments)

shmageggy

I think the authors also used Antigravity to write this article, because it sucks at communicating whatever point it’s trying to make. I think it’s something like “We did the OpenAI 100 problems thing, but across many disciplines, and in collaboration with the experts instead of just dumping results on the world, and we also made the tooling feature available,” but I’m not sure because it has that distinct Gemini flavor of packing in so many low-level details that the actual point becomes entirely obscured.

classified

Sloppification is now called "advancing". That may even be innovative.

dava96

Interesting that a Rust re-write pre optimisation was 30% slower than the C++ equivalent. 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.

gdevenyi

This doesn't tell me how to use it.

mirrokni

As noted by others, we already announced parts of /teamwork in Antigravity here: https://antigravity.google/blog/teamwork-when-ai-becomes-a-r... with more visualizations and more. Thi post was meant to report some advances in math/science/coding/engineering to show-case examples of tasks you can do with it. 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.

stbenjam

It is not clear to me how or if /teamwork is any different than Claude dynamic workflows. 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.

s_u_d_o

The amount of breakthroughs this could deliver. Previously we should’ve established R&D departments, prepare multi-cultural teams, all to work on a single project. Today? I can see a domain expert, guiding antigravity and delivering fast.

kats

Google is missing LLMs the way that Microsoft and Intel missed cell phones.

CharlieDigital

Related: I've been finding a lot of success (defined as more autonomy with less quality dropoff) with team-based workflows. 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.

jdw64

I'm not really sure. I've tried the EGM plugin too, but the issue that “the auditor verified it” doesn't solve the auditor's own reliability problem and just circulates the responsibility for verification within one layer—honestly, I'm curious how they solve that. What I want to know is this kind of thing. In practice, when I use the Antigravity Argon multi-agent model, the problem of auditors making false completion reports still exists. I wish the Antigravity team would write something like a whitepaper on how they actually use the Gemini models. It works properly in other models' harnesses, and I pay for credits and use Gemini, but I've never gotten results that good from Gemini.

mtzaldo

My experience using oh-my-claudecode as orchestrator and using the teams options was a mix. For one side the work completed was very good and it took less time. The main issue I had was my hard drive was getting full because I was using worktrees and the weekly tokens were spent in about 2 days (plan Max 20x)because all the context was being duplicated in all the agents as part of the teams. Not sure how Antigravity works, but I hope it doesn't have the context issue.

Semantic search powered by Rivestack pgvector
12,728 stories · 120,417 chunks indexed