Google Antigravity's official account announced on September 25 that the 2.0 desktop version has added an independent planning mode, aligning with its CLI: input /plan, the agent first retreats to study the task, then generates an implementation plan for your review, which must be approved before execution; you can also request a lighter plan in natural language.

Almost simultaneously, Thariq from Claude Code's product side mentioned on September 23 that the team is considering shutting down the plan mode to free up Shift+Tab for the effort tier; the reason is that the model no longer requires a dedicated planning mode, while seeking feedback from loyal users on why it should remain. The community quickly reacted with phrases like "plan mode is dead" and "others just removed it while Google just added it." The official documentation still retains /plan and Shift+Tab for read-only planning, which can only be modified after approval.

Antigravity describes /plan as a multi-stage discovery: analyzing prompts, checking the workspace, reading affected files, and then delivering a reviewable proposal; within the same command set, there is also /grill-me for Socratic alignment and the paid tier /boost for multi-agent deep reasoning. When Google released 2.0 in May, commands like /goal, /schedule, and /browser were already available, with planning being more of a "plan when needed" approach, now transitioning to an explicit mode.

The plan mode in Claude Code essentially serves as a system reminder plus the ExitPlanMode tool: it prohibits writing until you confirm after research. Users have long complained that it intrudes, causes session freezes, and conflicts with context compression; some view it as a brake before risk migration. Effort, on the other hand, is another knob that controls how much computation to spend this round, from low to max, with the new model able to write plans itself at higher tiers and rewrite them based on results, rather than freezing plans.

In market mechanics, buyers want to see the developer's proposal before changing code, while sellers offer two sets of agent programming products. The driving force behind this event is the competition for keyboard shortcuts and default workflows, not whether the model can suddenly think. The funding flows towards tokens: the independent plan adds another round of read-only context, while high effort directly extends reasoning. The beneficiaries are those who internalize planning into the model loop and charge by tier; those under pressure are those relying on explicit modes for user security, yet are written off by competitors as outdated rituals. The same functionality is seen as scaffolding to be removed by one company and as a newly added selling point by another.

Source: Public Information