September 26, 2026
Antigravity separates planning from code: /plan awaits confirmation
On Nov 1, 2026, Antigravity will discontinue support for Workflows. In Antigravity 2.0, the `/plan` command researches a task, writes a plan, and waits for confirmation before execution.
Gergely Orosz
@gergelyorosz
Antigravity is Google's most confusing product. It's as though Google decided it now needs to compete with market leader Kiro. Just kidding, but this feature copies Kiro / GitHub Workflows, and all of them have proven dead on arrival, except among lumbering companies and teams…
Antigravity 2.0 now features a dedicated planning mode, just like the Antigravity CLI. Type /plan and the agent steps back to think through the task, and conduct extensive research, before generating an implementation plan for your review. The agent will ask for your approval before it begins executing on the task. You can also ask for a plan naturally in your prompt, for a lighter version of a plan.
· 8.3K views
Previously, Antigravity stored a Workflow as a single `.md` file in `.agents/workflows/`. The file could hold up to 12,000 characters. Now a workflow will become a Skill: its directory can contain instructions, scripts, references, and assets, while `/migrate-workflows` will migrate the old workflow and leave a `.bak` file.
A familiar pattern. Kiro already has Crew Workflows, but they must first be enabled with a separate command. Antigravity makes planning an explicit step before the agent starts work.
Existing Workflows will continue to work until Nov 1, 2026.
