The scariest part for me wasn't that AI couldn't answer
At 10 p.m. last Tuesday in Hangzhou, I was helping a three-person squad improve its quoting workflow: one person organized client requirements, another drafted replies, and another checked pricing. But every time we moved the AI records around, the answer seemed to be missing half a page of background. I got stuck too: after two hours, I realized we'd all been working from three different sets of documents.
If you've also had to re-explain the project to every person and every tool, maybe it's worth looking at Antigravity's new /teamwork command. Rather than training another smarter model, it lets AI divide the work across a shared team space, with tasks, code, and progress visible to everyone.
What it actually solves is context handoffs
Antigravity is Google's intelligent development environment. In plain terms, it puts coding, running projects, and AI-assisted changes in the same workbench. The new feature lets team members launch parallel tasks through /teamwork: one person builds a page, another adds tests, and a third perspective reviews the result.
Chen Yu, a developer-tool maker in Beijing, recently tried it while rebuilding a personal product. At 10:30 a.m., he assigned old-page migration, API verification, and test coverage to three collaboration roles. By noon, the team had a gap list to work from, rather than three conflicting sets of edits. The name is fictional, but this relay-style workflow, where people compare differences while working, closely reflects how small teams actually operate.
Recreating it today: low budget, but not a one-click solution
On paper, this research feature currently has no separate price, and public materials haven't revealed its long-term cost. For now, I treat it as 0 yuan in cash. The real time cost is 2–4 hours: one hour for one member to organize the requirements, then another 1–3 hours to split the tasks and verify the results. The technical barrier isn't high, but I still need to understand basic project files, software versions, and testing workflows.
The first step isn't to explore every feature. It's to open Antigravity, click “New Team” or the team entry point, and give two roles a small page change to collaborate on. Button names may vary by version. I wouldn't load the whole project into the first test; I'd start with a small task deliverable in half a day.
Keep the setup restrained, based on your stage
Just starting: If I'm running a solo side project, I probably don't need multi-person collaboration yet. Keeping requirements and version notes in one place offers better value. If I do try it, I'd limit the test to two AI roles reviewing one small feature.
Serving 1–2 clients: If every delivery means repeating the background, I'd start with a pilot combining client requirement breakdown and reply drafting, then check whether shared context genuinely reduces rework.
Scaling up: If I'm leading a 3–5-person squad, I can put task allocation, result checks, and handoff notes in the same space. I'd still keep human approval in place and avoid having multiple roles edit the same thing simultaneously.
Not everyone needs this tool, and even mature teams may not want it connected straight to core projects. It's fine not to try it now. When context handoffs really start slowing me down, testing it with one small task is the cheapest way to find out.