u/alvmadrigal

Antigravity CLI came to change the game for developers.

Google Antigravity CLI overview by Compa Compila

📑 1. Strict Planning Mode by Default

The CLI doesn't just inject code blindly. It generates a structured markdown plan first. You use the artifact command to inspect proposed changes and must explicitly approve them before it modifies your workspace.

🎤 2. The /grillme Interview

Instead of requiring a flawless initial prompt, the CLI interviews you. After a basic input, it asks targeted engineering questions (e.g., folder structures, power-up mechanics) to map out requirements before a single line of code is written.

⚡ 3. Insane Speed & Metrics

Running on 3.5 Flash, the CLI generated a fully playable game in roughly one minute.

  • The context command reveals token usage in real-time (the entire project used just 7.3% of the 1M window).
  • The quota command tracks your API limits right in the shell.

🔀 4. Multitasking via /BTW

While the agent was actively compiling code, the reviewer used /BTW (By The Way) to ask an architectural side-question. The CLI answered seamlessly without disrupting or pausing the active code-generation loop.

🔄 5. Unified Configuration Sync

Unlike older tools, the CLI and Desktop GUI/IDE share the exact same state. Any theme or keybinding adjustments made via the CLI’s config command instantly update your GUI environment in real-time.

Tags: Google Antigravity CLI | Gemini 3.5 Flash | AI Coding | DevTools |

youtu.be
u/alvmadrigal — 1 day ago
▲ 631 r/GoogleAntigravityCLI+1 crossposts

If you're wondering why Gemini limits have plummeted dramatically, the answer is simple, they are selling compute to other companies, google realized they can make MUCH more money per token selling it to anthropic than using their own models

Instead of investing into strong models, they started releasing countless fluff empty products to mask this transition.
Which explains the "flash" model too.

Google, at least for now, decided to turn into a compute supplier rather than a model maker it seems.

If you were stupid like me and bought for the whole year using the new year offer, you have been RUGGED.

In retrospect the deal was too good to be true, which means they were planning on doing this since then.
Which is why all their pre-train (base models) are STILL working on the 2024 dataset (jan 2025 cutoff).
AND another thing, they invested in anthropic as a way to position themselves to potentially acquire it in the future.
This is more of a conspiratorial thing but it makes sense, they have showed alot of interest in anthropic.

reddit.com
▲ 8 r/GoogleAntigravityCLI+1 crossposts

Last ever task for Gemini CLI...

Ironically, my last ever task to Gemini CLI was to ask it to make a PR for my agentic framework, dropping support for it and adding support for Antigravity CLI + migration etc....

Horrible decision by google, but it is what it is.

u/Cobuter_Man — 1 day ago
▲ 3 r/GoogleAntigravityCLI+1 crossposts

FIRST LOOK into Google Antigravity CLI

What's up Agent builders Google just dropped the official first-look video for the Google Antigravity CLI

They made it explicitly clear: the CLI doesn't try to be a GUI. It’s built natively for lower overhead, blazing-fast speed, and completely molds to your existing dotfiles, themes, and keybindings.

Here is the technical breakdown of the absolute best features shown in the demo:

1. The Power Features: /BTW and /fork

  • /BTW (By The Way): Running a massive, long-tail test suite or a giant code generation task that's locking up your context? Type /BTW to spin up a background thread and ask a completely separate question without interrupting your active, running agent task [01:38].
  • /fork Want to test a chaotic alternative architecture without ruining your progress? Type /fork to instantly branch your current terminal agent conversation into a safe, sandbox experiment [01:45].

2. Multi-Agent Orchestration in the Shell

The CLI natively handles parallel sub-agents [01:04]. In the video, they showed:

  • Agent 1 mapping out the codebase architecture.
  • Agent 2 modifying multiple files simultaneously based on that architecture.
  • Agent 3 silently writing unit tests in the background.
  • Control: The agent presents an implementation plan first [01:25]. Every file change or proposed shell command requires you to explicitly tap Y or N to execute [01:54]. Your sandbox, your rules.

3. Programmatic Automation (-p flag)

For everyone planning to build cron jobs or data pipelines, the native -p flag allows you to pass prompts directly at startup [02:07]. This means you can easily script complete agentic loops directly inside your bash/zsh scripts without having to drop into an interactive session.

4. Custom Slash Commands

You can define a "custom skill" inside your local workspace configurations, and the CLI will automatically register it as a native slash command [02:23]. Yes—that means you get tab-completion for your own team's custom DevOps playbooks and personal automation scripts [02:30].

5. The Escape Hatch to the GUI

If a code migration gets way too massive and you actually want visual context, you aren't trapped. A single command allows you to seamlessly export your entire terminal conversation history straight into the standalone Antigravity Desktop GUI app without losing a single line of progress [02:32].

Check out the full 3-minute video here:https://www.youtube.com/watch?v=WiWDrTujl_w

What are your thoughts on /BTW and /fork? Personally, turning workspace skills into auto-completable slash commands is going to completely change how I manage my dotfiles. Let's discuss!

youtube.com
u/alvmadrigal — 2 days ago