The Spare Tool

Another has Antigravity in their stack with Codex as a backup, and said Google had made Gemini tokens much cheaper, so they had not been hitting limits recently and might cancel Codex. There the spare is Codex, and the cheaper allowance that keeps Antigravity in use is the reason it might go.

The same logic turns into a division of labor. One person has Claude hand its coding sessions to Antigravity and then audit and correct what comes back, and said it works well and that Google's limits never block them; another keeps Claude, Codex and Antigravity for different tasks so each can stay on its lowest-priced plan, and pasted a description that casts Claude as the "Team Lead" and Antigravity as the "Execution Agent." In both arrangements Claude is the head and Antigravity the hands.

On quality, the verdicts split, and the split follows the model more than the tool. One person called Antigravity a "trash heap" offering "unlimited access to a model that lies, destroys files" and more; another, after a first attempt had wasted their quota and delivered "absolute junk," said an Opus model reached through Antigravity did the same task "flawlessly." The first condemns the model the tool carries. The second credits a model and treats Antigravity as the door.

People weigh crossing over in both directions. One person using Antigravity asked whether to stay or change to Claude, having heard it was far better; another who had run out of Claude and cancelled said they would try Antigravity, expecting to miss Claude Code's technical expertise. Each ranks Claude ahead on quality.

Bluesky sounds different. There the language is of autonomy: the posts say Antigravity can run commands, fix errors and keep working without constant approval popups, and that Gemini runs in a secure sandbox where it can write code and edit files on its own. These read as announcements rather than experience, and neither mentions limits.

What Antigravity is depends on who is asked. One person said the harness matters and that benchmarks should have used Google's own, the Antigravity CLI; another preferred a Google model inside it and found the same model "kinda meh" outside, saying it was designed to work inside Antigravity. Both treat Antigravity as the harness that shapes how a model performs. It also appears as one name among several on lists of tools that other software connects to: usage trackers, connection servers, file-search tools. Being on those lists is a thin kind of presence: it says what the tool connects to, not what anyone made with it.

Its standing is contested: one person asked whether people are using it, and another said no one does. Against that, people are building with it, from a racing game to an extension that gives its agent a browser and lets a person connect their own Gemini key to get past quotas. A claim that no one uses a tool sits awkwardly beside people shipping things with it.

Not everyone who has it reaches for it. One person with a free Google subscription through their SIM card said they use Google's AI only occasionally, and another who had had Antigravity for months said they did not understand it and that it was bad. One describes infrequent use and the other describes dissatisfaction; neither says they have dropped it.

For people who stack tools this way, a tool earns its place by taking over cleanly when another one stops, not by winning a comparison. That makes the hand-off the thing worth getting right, and it is a test a tool can pass without being preferred.