Antigravity 2.0 and the CLI That Finally Felt Like a Coworker

By Muhammad Kashif · Draft · AI automation & cybersecurity builder, Pakistan

Antigravity 2.0 showed up as a standalone agent-first desktop with parallel subagents and a free tier with weekly limits — Gemini, Claude, GPT-OSS in the mix — researching a D2C niche, redesigning a live site with cart, even scheduling 9 AM audits of my site versus competitors. Pieter Levels' solo playbook sat in the same notes: ship ugly, find demand, own distribution. The CLI finally felt like a coworker when it combined those energies without hiding the plan.

Agent-first desktop, human-first keys

Parallel subagents for front end, back end, debugging, research are the headline. Google's demos with huge subagent counts are the temptation. I start with three, a shared plan visible in the CLI, and credentials that are not my daily-driver passwords.

Free individual plans with weekly limits are perfect for spikes. Client work still rides contracted accounts with audit trails.

Ship ugly, then instrument

Levels going from five hundred dollars a month to multiple solo businesses without VC — Nomad List, Remote OK, Photo AI, Interior AI — and the twelve-startups-in-twelve-months volume lesson sit above my Antigravity experiments. Volume of shipping matters. Volume of unsupervised production deploys does not.

Avatar AI getting copied, then Photo AI winning on repeat-pay headshots, is a product lesson: move to recurring need. Agents can help build. They cannot choose the need for you.

fly.pieter energy without the amnesia

Vibe-coding a 3D flight game to serious ARR in days is a story about iteration speed. My CLI coworker may iterate that fast on a branch. It may not iterate that fast on main with payments live. I copy the prompt iteration loop and add CI.

2026 stack notes — Claude for code, GPT Image or Nano Banana for images, Gemini Omni for video, ElevenLabs for voice — become defaults only after a tiny arena test on my brief.

Scheduled audits with manners

Daily 9 AM site audit versus competitors with a report ready is a gift if the agent can only read public pages and write to a reports folder. It is a problem if it can also "helpfully" push live CSS changes at 9:05.

Schedulers get read scopes. Push scopes wait for human mornings, not agent mornings.

D2C redesign pilots

Researching a niche, then redesigning a site with campaign visuals, animations, and a working cart — great Antigravity demo shape. On client work I fork a staging theme, use dummy payments, and freeze brand tokens first. Working carts on production with agent-generated checkout copy is how compliance wakes up angry.

Ugly staging first. Pretty production after review.

CLI as coworker means visible plans

The moment the CLI shows the plan before execute, it starts feeling like a coworker instead of a slot machine. I require plan paste into the PR. I require a time box. I require a stop command I actually remember.

Coworkers get feedback. Slot machines get unplugged. I prefer the former.

What I sell from this cluster

Antigravity-style desktop setup with scopes, Levels-inspired shipping cadence for solo founders, and scheduled research agents with read-only manners. I do not sell "93 subagents on your live cart."

Personal sticky note

Ship ugly. Own distribution. Agent on a leash. Plan before execute. Audit at 9 AM, push after coffee. That is Antigravity energy I can defend.

9 AM audit, 11 AM human

Scheduled Antigravity audits land as drafts at nine. I read them at eleven with coffee, never with push scopes enabled. Levels-style shipping speed applies to staging branches. Live carts wait for the human hour.

The CLI coworker earns trust by waiting. Waiting is a feature I configure explicitly so "helpful" overnight pushes cannot happen.

Distribution before decoration

Levels' own-your-audience lesson beats another Antigravity animation pass. I ask solo founders for their distribution loop before I approve a cart redesign sprint. Pretty carts without distribution are expensive hobbies.

Weekly limit honesty

Free Antigravity tiers with weekly limits are for spikes. I write the limit into the project plan so founders do not discover it mid-demo. Levels-style shipping still needs a paid lane when the loop becomes the business.

Staging theme fork

D2C redesigns start on a forked staging theme with dummy payments. Antigravity cart demos that touch production checkouts fail my personal review even if the CLI plan looked tidy. Ugly staging first remains the rule.