AI Aulis

AI NEWS IN ENGLISH · 12 November 2026

The most important AI news every morning. AI writes and checks the stories against the original sources – check important facts in the sources.

34 stories · next issue tomorrow morning · How the paper is made →

← Issue 12 November 2026Paper

Google Antigravity’s /swarm splits a task between agents working in parallel

AI-generated contentWritten by AI

antigravity.google · Source publication date unknown

In Google’s Antigravity, the /swarm command turns a conversation into a coordinator that splits a task between named agents, which communicate on a shared board. A verifier is usually included. The feature is in preview and uses up the usage limit much faster than a single conversation.

Google describes the new /swarm command in the Antigravity documentation. Antigravity is Google’s programming environment in which AI agents do development work. A notice on the documentation page says /swarm is now available in preview. Google says the command suits tasks that split clearly into separate files, packages or questions. The command also lets users have another agent review and test the changes before they see them.

The coordinator divides the work, the verifier tests it

When the user runs the command and describes the task, the current conversation becomes the team’s coordinator. The coordinator splits the task into parts that do not overlap. Each file or package, for example, can get its own agent. Every worker agent gets a name, such as @parser or @docs, and starts its own conversation with no prior context. Its brief is posted for everyone to see. The brief sets out the agent’s responsibilities, what it must not touch and the condition for finishing the work.

The coordinator usually adds one verifier (@verifier) for every two to four workers. The verifier reads the changes and runs the tests. It reports problems to the agent that wrote the code, which fixes them. The coordinator does no technical work itself. It assigns tasks, assesses the results and reports to the user.

The agents do not send each other private messages. Briefs, questions, change summaries and test results go on a shared message board. An idle agent waits without using tokens and wakes when someone mentions it. If every agent falls silent mid-task, a separate @monitor agent uses the board to call on an agent that can get the work moving again.

By default, workers use the same model as the user’s conversation. Users can request a different model for one worker, such as the verifier, or for all of them. Agents work in the user’s workspace by default, but the coordinator can give each one its own copy of the repository. Removing an agent also deletes its copy, so the coordinator has the agent merge its changes first.

The usage limit runs out fast

Google warns that a team uses up the usage limit much faster than a single conversation. Each worker is a separate agent. If an agent reaches its usage limit, it stops and does not resume on its own when the limit resets. It resumes only when a new message arrives on the board, its model is changed or the user messages it. A removed agent cannot be restored.

Google recommends /swarm for large tasks that split clearly into parts. For a hard but narrow problem, Google points users to the /boost command. For projects lasting hours to days with several milestones, it recommends /teamwork.

Google AI Pro and Google AI Ultra subscribers can use the command in the Antigravity app and the Antigravity CLI, its command-line tool. Users can follow the team’s work in the app’s Swarm panel or on the command line, and the Antigravity documentation has more detailed instructions.

What this is based on

  1. Swarm (/swarm) | Google Antigravity Docs

    Publisher: antigravity.google · source publication time unknown · retrieved 12 November 2026 at 05:57 (UTC+02:00) · discovery channel: web

Previous coverage

Report an error in this story