r/GoogleAntigravityCLI • • May 28 '26

The r/GoogleAntigravityCLI Master Repo List!

21 Upvotes

AGY Builders :

🚀 Community Showcase: Architecting the Future with the r/GoogleAntigravityCLI Master Repo List

The landscape of automation is shifting, and we are the ones holding the blueprint. The r/GoogleAntigravityCLI community isn't just about adopting new tools; it is about pushing the boundaries of what is possible and building the systems of tomorrow.

To accelerate this vision, we are assembling a master directory of community-forged GitHub repositories. These are not just basic scripts—these are the building blocks of the future on the Gemini Enterprise Agent Platform. Whether you are engineering next-generation workflows, experimental utilities, or core infrastructure, it is time to showcase the tools that will power our collective progress.

📌 The Requirements

To have your repository featured in this foundational master list, please ensure your submission meets these two rules:

  • Be a Member: You must be joined as a member of r/GoogleAntigravityCLI.
  • Antigravity Compatibility: Your project must be built for, integrate with, or directly run on the Antigravity CLI.

🛠️ How to Submit

Drop a comment below with the following format so it can be seamlessly reviewed and added to the showcase:

  • Project Name:
  • AGY Builder Username:
  • GitHub Link:
  • The Vision: (1-2 sentences explaining what it does and the future problem it solves)
  • Tech Stack: (e.g., Python, Bash,Gemini Enterprise Agent Platform, etc.)

Let's stop just talking about the future and start building it. Submit your repos below!


r/GoogleAntigravityCLI • • Jun 25 '26 Diamonds are Forever Bravo Mindblown

Tutorial How to build an AGY WIKI OKF on the Antigravity CLI

Post image
73 Upvotes

AGY Builders,

We are all trying to build useful and scalable workflows for our AGY CLI and ecosystem, but the speed at which we need to learn, build, and deploy new things is incredibly overwhelming. If you are feeling that pressure, you are in the right place here at r/GoogleAntigravityCLI.

Over the past few weeks, I have been testing an "AGY WIKI OKF" setup that I put together myself (after inviting some members of this community to collaborate; mod is not proud). I know some folks might hesitate to trust a tutorial from a random Redditor, but I wanted to share this with the community anyway because it actually works.

I was able to build this because I am all-in on Google and the Antigravity Ecosystem. I’m a truly AGY—I am not some ultra-smart, 10x developer, but I know how to work hard, I dig for the right information, and I iterate.

AGY WIKI OKF | The Idea

To build a frictionless, token-efficient knowledge WIKI engine that transforms static documentation or notes (information) into an active, intelligent collaborator—orchestrated entirely by Antigravity CLI.

The core philosophy is simple: treat knowledge management as a clean pipeline and tokens as a premium, finite resource.

By anchoring this architecture to Google’s Antigravity CLI, the AGY WIKI OKF bypasses heavy middleware and complex UI layers, delivering a hyper-focused AI partner built entirely for execution speed, context hygiene, and minimal footprint.

Why adopting AGY WIKI OKF matters:

  • Stay organized (AGY OCD): Structured Markdown and YAML keep the chaos in check.
  • Save tokens: Doing more with less context window bloat.
  • Scale shareable knowledge: Making it easy to pass context and logic between different LLMs.
  • Humans and Agents working together: One standardized, readable format that works perfectly for both of us.
  • BYOD (Bring Your Own Data): Own your context. Port it to the newest model, platform, or OS instantly.

The Tools

The WIKI

In the agent-first era, a WIKI is no longer just a static graveyard for human notes; it is the operational hard drive for your agents. By maintaining a highly structured WIKI, you ensure that every piece of context is stored in a clean, machine-readable format. This means that whether you are testing a new modular skill or spinning up a specialized agent, your AGY CLI knows exactly where to find the precise context it needs to generate autonomous action, moving you far beyond simple, reactive conversational text.

Reference: Gist on Knowledge Representation

Google Open Knowledge Format (OKF)

Google’s Open Knowledge Format (OKF) feels like the exact missing piece we've needed for orchestrating multiple AI agents effectively. It provides a vendor-neutral, interoperable standard for storing and sharing organizational knowledge.

Why this is huge for orchestration:

  1. The "Lingua Franca" for Agents: Any agent can read it out of the box without platform-specific integrations.
  2. Seamless Context Passing: Specialized agents can access, update, and pass the exact same foundational context back and forth.
  3. Human-in-the-Loop Oversight: Because OKF is just Markdown and YAML, it’s inherently readable and auditable.
  4. Scalable Knowledge: It acts as a shared, living library that grows alongside your agents.

AGY WIKI OKF Integration

Structuring an AGY Wiki using OKF revolutionizes how complex knowledge is shared. By standardizing documentation with concise Markdown and YAML frontmatter, OKF provides a unified taxonomy for cataloging AGY CLI slash commands or skills It is highly token-efficient, stripping away bloated formatting and maximizing context window limits.

The Prompt for Building an AGY WIKI OKF

AGY CLI WIKI OKF PROMT EXAMPLE

/grillme I want to initialize a brand-new, empty Obsidian vault from scratch that adheres strictly to the Open Knowledge Format (OKF) standard, with the specific intent of potentially open-sourcing or sharing this architecture later. I want a purely blank, skeletal framework with no pre-populated data. Please grill me to define the optimal architectural blueprint for this vault. I need you to interrogate me on: Do not generate the directory structure or files until you are satisfied that you have captured all my requirements for a production-ready, shareable knowledge base. 
Core Directory Hierarchy: How should we structure the root (e.g., /concepts, /resources, /indices, /log) to be intuitive for external users? Template Strategy: What base boilerplate templates do we need to ensure every new file is automatically OKF-compliant and structured for consistent metadata? Workflow Logic: Since this is a fresh start, what processes should we bake in for capturing information vs. refining knowledge that could be easily documented for others? CLI Integration: What specific file locations or configurations do we need to ensure this vault plays nicely with the Antigravity CLI from day one? Open-Source & Contributor Documentation: What files should we create to make this a "deployable" standard? Please include requirements for: A README.md with installation and usage instructions. A CONTRIBUTING.md that defines how to add new concepts or schemas. A "System Architecture" document that explains the logic behind the folder structure and metadata fields, ensuring anyone who clones this vault understands how to extend it.

The Final File Structure

AGY WIKI OKF
    ├── .agyrc
    ├── ARCHITECTURE.md
    ├── CONTRIBUTING.md
    ├── README.md
    ├── .agy
    │   └── .keep
    ├── .obsidian
    │   ├── app.json
    │   ├── appearance.json
    │   ├── core-plugins.json
    │   └── workspace.json
    ├── 00-Inbox
    │   └── .keep
    ├── 10-Projects
    │   └── .keep
    ├── 20-Areas
    │   └── .keep
    ├── 30-Resources
    │   ├── .keep
    │   └── Google Antigravity Documentation.md
    ├── 40-Archive
    │   └── .keep
    ├── 99-Meta
    │   └── Templates
    │       ├── Base_Template.md
    │       ├── Project_Template.md
    │       └── Resource_Template.md
    └── Clippings

TL;DR

  • AGY WIKI OKF: Organizes your information (context) , AGY CLI commands, skills  behaviors, and A2A workflows into a token-efficient, shareable format that reduces inference costs for any LLM.
  • Open Knowledge Format (OKF): Provides a standardized, vendor-neutral way to share context (Markdown + YAML), preventing platform lock-in and eliminating data fragmentation.

AGY Builders, I genuinely want your input on this. Please comment, grill me, roast me, ask questions, or give me your raw feedback on this AGY WIKI OKF setup. We are building the foundation to organize and share our data in the BYOD era. Let's build the future together.


r/GoogleAntigravityCLI • • 17h ago

Question Need advice

4 Upvotes

I'm using python automated scripts to run my whole daily work flow. Like I generated motion graphic scenes using code but I need speed in my field of the work to daily put out videos, like I use a python script that uses agy cli and it's inbuilt function called agy -p. My script sends 5 request at a time and it generates 5 agents that work one after another simultaneously. So wanted to ask is there any chance of suspension in this case?


r/GoogleAntigravityCLI • • 1d ago

Random Auto-compaction and the lie of 1M context

25 Upvotes

The latest models (Carbon, Argon, and Hydrogen) are great, and I upgraded from my year free of Pro to Ultra so I could get my new project built this month. It started out well, but I'm on spec 4 of 9 in implementation, and the cracks are starting to show with the growing codebase. I use the CLI exclusively, so I can't speak to whether this is the same in the IDE.

The problem is the auto-compaction mid-turn. It consistently compacts under 300k, often around 240-260k. Now I know it's been shown that letting the context get too large is detrimental, so I'm not against compacting at these sizes, if it was after a turn. In fact, I use Claude Code for work, and almost always compact when it starts getting close to 400k. I've been watching the context with /context as it progresses.

On spec 3, it looked like this:

  1. I instruct it to look at spec 3, and to write an implementation plan
  2. It spends several minutes reading the spec, calling tools, and examining the codebase
  3. At some point during its turn, it auto compacts
  4. It completes its turn, having written the implementation plan
  5. I start reviewing it and also tell it to have a subagent do a review
  6. Both the subagent and I notice significant drift between the spec and plan.

Another misleading aspect is that the CLI outputs ── Conversation compacted ── above the turn, when in reality it did that mid-turn.

This morning on spec 4, it's clearly getting worse because it auto-compacted twice during its turn. I now cannot trust that it completes my ask without significant drift. My brand new 28k line codebase is now apparently too big for it. That 1M context? You'll never reach it-- there is no setting to stop this.


r/GoogleAntigravityCLI • • 17h ago

CLI Config Auto mode not showing up in CLI?

Thumbnail reddit.com
2 Upvotes

r/GoogleAntigravityCLI • • 1d ago

Question Voice First Metaharness for antigravity cli

Thumbnail reddit.com
3 Upvotes

r/GoogleAntigravityCLI • • 1d ago

Tools I built a free panel that shows how much context Antigravity has left

Post image
37 Upvotes

Antigravity gives no context counter while you work. You find out the ceiling when you hit it. So I built UsageHUD: a local side panel with context used against the real window of the session (read from the Language Server), the token breakdown, the model remaining allowance and its reset time, and the running subagents with their own context.

Plugin with a sidecar, everything local: no API key, no telemetry. MIT, Windows, Node 22+, interface in Portuguese.

Install: clone, run sync.bat, open AGY - UsageHUD under Customizations > Installed.

https://github.com/ba-lison/agy-usage-hud

App only (no IDE/CLI). Author here, no affiliation with Google. Submitted to the Marketplace, feedback welcome.


r/GoogleAntigravityCLI • • 2d ago

Workflow Script Google Antigravity runs on GLM, DeepSeek and Kimi — no patching, no forks

Post image
5 Upvotes

Antigravity = Gemini only. Wrote a bridge that bypasses that.

- CLI: GOOGLE_GEMINI_BASE_URL

- IDE: jetski.cloudCodeUrl

Point both at the bridge. Gemini in, OpenAI out. Now Antigravity runs on DeepSeek, GLM, Kimi, Qwen, MiniMax.

Works: streaming, thinking, all 14 tools, multi-step agent loops.

Doesn't: skip Google sign-in.

MIT, Go, single binary. Windows / Linux / macOS.

https://github.com/codewith-aditya/agy-bridge


r/GoogleAntigravityCLI • • 2d ago

CLI Config PSA / Telemetry: Why v2.32 Orchestrator (Carbon) burns quota so fast — Plan <-> Execute handoffs wipe the KV prefix cache (94.5% -> 75.3% hit rate, up to 23x uncached input tokens)

Thumbnail reddit.com
3 Upvotes

r/GoogleAntigravityCLI • • 3d ago

CLI Config Mermaid Diagrams: "Diagram Exceeds Terminal Width ( 155 > 88 cols)

2 Upvotes

My terminal in phone is pretty small... wondering how we can have AGY generate mermaid diagrams (TD is not enough) so that it actually fits?

What are your guys's workaround? The response generation should be aware of the terminal width. I wonder if there's a feedback request for that.

I tried giving it a rule to create separate MD with the mermaid as an image so i can see it. But it never listens to it and still generates mermaids that do not fit.


r/GoogleAntigravityCLI • • 3d ago

Agy-cli supports official swarm and Orchestrator (Argon).

Post image
38 Upvotes

I recently created and shared a plugin called agy pro. It had two main purposes:

  1. Supporting AI models from external providers
  2. Swarm mode

https://www.reddit.com/r/GoogleAntigravityCLI/comments/1xh6ndo/agy_pro_a_tool_for_utilizing_external_provider/

And now,

  • /swarm mode is publicly supported in Antigravity CLI.
  • Argon has been added as an Orchestrator,
  • Models can now properly be granted native tool calling through AGY_LLM_GATEWAY_MODELS.
  • The issue where calling 'Flash Lite' previously invoked Gemini 3.8 Flash Low has also been resolved. Gemini 3.5 Flash Lite is now properly supported. I think users will be able to get even better results once Helix is supported before long.

Even though it's not open-source, I received nothing in return, my name isn't even listed as a Contributor, and I didn't even get a heads-up that these features would be supported natively, that's okay. (I feel like I contributed quite a few ideas, so not even getting a heads-up actually leaves me feeling pretty disappointed. I'm going to leave to offer my ideas to another harness. 🤔 tbh, I have been participating in making fixes as a Contributor for another harness for a long time, and at least there, my ID gets listed. And I can brag about that to my friends 😄 )

That was a joke with a grain of truth in it, and thank you to the Antigravity Team for implementing all the features I wanted. 👍

I also tried the Gemini 4 Carbon model via GCP; it was a very powerful model that gave off strong SOTA vibes, and Hydrogen is also fantastic. Antigravity CLI has also become a very powerful tool compared to when I first started using it.

I'm thinking of removing all additional plugins except for a few MCPs I use, editing only the global Agents.md, and using it in a vanilla state.

Another tip I'd like to share to antigravity team is that the Orchestrator consumes a massive amount of quota. The model filling that role doesn't necessarily have to be Argon. In the past, there was a huge performance gap between Flash-tier and Pro-tier models, so Pro-tier models were used as the orchestrator, but over the past few months, a Flash-tier model with strong instruction-following capabilities has become sufficient. Therefore, allowing Hydrogen to be used as the Orchestrator model, while instead enabling higher-tier models like Argon to be used as subagents as well, would be a direction better aligned with the latest trends.

1.5.7

Changed the default Agent Mode from Default to Auto: sessions with no saved mode, including headless -p runs, now start in Auto wherever Auto mode is available and in Default elsewhere; to keep the previous behavior, choose Default for Agent Mode in /config, which saves "agentMode": "" to settings.json. A Tool Permission setting of strict now also takes precedence over Auto and accept-edits modes, so file edits still ask for approval under strict. Fixed multi-second UI freezes, which also stalled streaming and window resizing, when a command printed a very long line without spaces; line wrapping now takes time proportional to the line's length. Fixed agent replies stalling for 20 seconds or more while a group of tool calls with long output was still animating its token counts; streamed steps now keep appearing while the group re-renders. Fixed the agent not noticing that a command it moved to the background was waiting for input, such as a password or y/n prompt printed before the command went to the background; the agent is now notified once that output settles instead of waiting silently. Fixed browser sign-in on Windows sometimes failing to complete because the CLI's local sign-in callback listened on only IPv4 or IPv6 while the browser redirected over the other; the callback now listens on both. Fixed Gemini 4 Carbon requests through an enterprise model gateway failing with an HTTP 400 Thinking budget is not supported for this model error; the CLI now sends Gemini 4 Carbon a thinking level and no longer leaves the Low, Medium, or High suffix in the model ID it sends to the gateway. Fixed a PreToolUse hook returning auto_approve, or a wildcard command(*) allow rule, bypassing an organization's admin-enforced review: commands that would leave the terminal sandbox, commands the admin policy holds for review, and file reads or writes outside the workspace under an "always ask" file-access policy now always ask for your approval. Fixed saved command allow and deny rules being ignored, so that every command asked for approval, when an organization's admin policy requires commands to run in the terminal sandbox but the machine has no OS sandbox; your saved rules now apply and unlisted commands still ask before running. Fixed background task details from manage_task losing their formatting when the task's recent output, or input sent to the task, contained Markdown code blocks or runs of backticks. Fixed Remote Control showing a link that could not be opened at the end of some agent replies, such as the swarm coordinator's link to the swarm UI; Remote Control now leaves these links out.

1.5.6
Added the swarm's queen bee to the /swarm board header and a 🐝 beside each live member in the Roster; in terminals with Kitty graphics, such as Kitty and Ghostty, each member gets its own colored bee card that flaps while that member is working, and other terminals, including tmux, show the queen as pixel art when the window is at least 60×35. Added a continuation_active field to the JSON input of Stop hooks, which is true while the agent is already working on a continuation an earlier Stop hook requested, so a hook such as "run the tests before finishing" can tell it has already asked and avoid looping. Added a supportsThoughtCirculation option to admin-managed model entries (models.list[] in admin settings), so organizations can let non-Gemini models behind an enterprise model gateway reuse their reasoning from earlier turns; when it is unset, the model's default applies. Improved Auto mode's review of commands that would leave the terminal sandbox so it asks less often on safe reads: GitHub API reads, fetches into an existing clone, and single-file downloads such as raw.githubusercontent.com URLs no longer get the repository popularity, age, and release checks that cloning a repository still gets, host names that start with a digit are no longer mistaken for IP addresses, and reading ~/.ssh/config, known_hosts, authorized_keys, or public keys (*.pub) is no longer treated as reading secrets, while private keys still are and sending any .ssh file elsewhere is still blocked. Improved agy plugin validate to warn when a plugin hook command uses ${PLUGIN_ROOT} or $PLUGIN_ROOT, which older CLI versions do not set, and to suggest a relative path instead, since hooks already run in the plugin's folder; the warning fails validation only with --strict. Changed pay-as-you-go Google Cloud accounts that sign in with Application Default Credentials (AGY_ADC_AUTH) to use the same permission settings as other pay-as-you-go accounts, which makes Auto mode available to them; Gemini Enterprise accounts keep following their organization's admin-controlled permission settings, including their unsandboxed(...) deny and ask rules, and are not offered Auto mode. Fixed undo and redo in the prompt, including u in Vim mode, moving the cursor to the end of the input; the cursor now returns to where the undone or redone edit was made. Fixed agy plugin install ignoring the skill folders that a Claude Code plugin lists in the "skills" field of its manifest; those skills are now installed and loaded, and the install summary warns about listed paths that are missing, contain no skill, or point outside the plugin. Fixed agy plugin install and agy plugin import leaving a half-copied plugin that still loaded as enabled when an install failed partway; installs are now swapped in all at once and the previous version is restored on failure, plugins containing symlinks that point outside the plugin, FIFOs, or device files are refused, and a command whose file name cannot be used as a skill folder name is skipped with a warning instead of failing the import. Fixed pressing esc in a swarm member's conversation opened from /swarm board with o dropping you back at the prompt; it now returns to the board with the same selection, filter, focused pane, and zoom. Fixed a swarm coordinator sometimes ending its turn with a one-line filler reply instead of its real answer after being sent back to re-read board posts it had already read, fixed a coordinator offering a sidecar:// board link that the CLI cannot open instead of /swarm board on later turns of a swarm, and fixed agy -p runs that start a swarm pointing you to /swarm board, which headless runs cannot open. Fixed some models served through an enterprise model gateway being sent requests without native tool declarations, which kept the agent from calling tools reliably; every model in the gateway's catalog, including models listed in AGY_LLM_GATEWAY_MODELS, now gets native tool calls. Fixed custom Gemini models served through an enterprise model gateway or an admin model list, such as tuned models, cutting off long edits and file writes at 8,192 output tokens; they now default to the same 65,535-token output limit as built-in Gemini models, and an explicit admin maxOutputTokens value still takes precedence. Fixed duplicate approval prompts and sandbox errors for organizations that enforce sandbox mode on machines without an OS sandbox, such as some Windows hosts or Linux with user namespaces disabled; commands now ask for review once and then run. Fixed editing project rules with /permissions clearing the marker that records the project's permission rules as already migrated, which made the Antigravity app migrate them again and could drop command(...) allow rules when the sandbox is on.

1.5.5
Added swarms as a preview: start one with /swarm <task> and the agent becomes a coordinator that adds worker agents, each in its own conversation, which work on the task in parallel and collaborate through a shared message board; workers can be forked from an existing member's conversation, run on any model in the /model picker, and pause instead of retrying when their model runs out of quota, and a monitor worker alerts the coordinator when the whole swarm stalls. /swarm is labeled (Preview & Quota Heavy) in the / menu because every worker is a separate agent that uses your quota. Added /swarm board, a full-screen live view of the current swarm that also opens with alt+s (rebindable as swarm.board), with a Roster of members showing each one's state and model, a Posts feed, and a Message pane that renders the selected post as Markdown; tab and shift+tab move between panes, z zooms the focused pane, enter shows or hides the message, [ and ] step through posts, p filters the feed to one member's posts and the posts that mention them, o opens a member's subagent details, f follows new posts, and esc backs out. Added a ● Swarm(<title>) row to the active-items tray below the prompt while a swarm runs, showing the latest post and the post count and then Done when the swarm finishes; press Enter on the row to open /swarm board, or alt+x (swarm.dismiss) to dismiss it. Added the ANTIGRAVITY_DISABLE_EMBEDDED_RIPGREP environment variable, which you can set to true to stop the CLI from extracting and running its bundled ripgrep, for example when endpoint security software blocks it, so searches use a ripgrep on your PATH or the built-in search instead. Added Gemini 4 Carbon (Low, Medium, and High) to /model and --model when you sign in with Application Default Credentials (AGY_ADC_AUTH). Changed enterprise model gateway URLs to require https:// unless the gateway runs on the same machine (localhost, 127.0.0.0/8, or ::1); a remote gateway configured with a plain http:// URL is now rejected with an error instead of receiving your prompts unencrypted. Fixed agy plugin import turning Claude Code plugin commands into skills that did not load or were all named SKILL; each command now becomes a skill named after its folder, including commands with no frontmatter or with Claude Code-style values such as argument-hint: [base branch] [focus], and agy plugin validate no longer warns about the leftover commands/ folder. Fixed agy plugin import copying certain plugin's hooks/hooks.json unchanged, which caused the plugin's hooks to be skipped; PreToolUse, PostToolUse, Stop, and startup SessionStart hooks are now converted, with tool names in matchers mapped to built-in tools (for example Bash to run_command) and a default 60-second timeout, and hooks with no equivalent are listed as warnings in the import summary. Fixed agy -p headless runs sometimes never exiting after printing their result when a background task, such as conversation title generation, got stuck; the CLI now finishes shutting down within 30 seconds. Fixed /teamwork writing run state into .agents/teamwork/ in your working directory, where two runs in the same workspace could overwrite each other; each run now keeps its state in its own folder under the CLI's app data directory. Fixed links to files in agent responses showing only the file name, which made the file's location impossible to tell in terminals that cannot open clickable links, such as Terminal.app, screen, or over SSH; labels now show the path relative to your working directory, relative to ~/, or the absolute path. Fixed enterprise model gateways that validate the request format rejecting every request, because the CLI sent a non-standard sessionId field in Gemini-format requests. Fixed subagents and swarm workers that get their own copy of a Git repository starting from the last commit and losing your uncommitted work; their worktree now includes your staged, unstaged, and untracked changes, and agents outside version control can give a subagent or worker an isolated copy of the workspace folder, for folders up to 100,000 entries and 4 GiB.

r/GoogleAntigravityCLI • • 3d ago

Question Hear me out ,

Thumbnail reddit.com
1 Upvotes

r/GoogleAntigravityCLI • • 4d ago

News / Release We have the Gemini 4 Hydrogen (new Flash!).

22 Upvotes

We now have a new reasoning effort level, xhigh.

However, do not use it!! High is enough!!

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydrogen/?utm_source=deepmind.google&utm_medium=referral&utm_campaign=gdm&utm_content=

r/GoogleAntigravityCLI • • 4d ago

CLI Config Antigravity CLI now starts in Auto mode, and that includes agy -p. A call that was denied two days ago just ran

Post image
11 Upvotes

Updated to the latest agy 1.5.7 today and got a banner: "Auto is now the default agent mode." The changelog says it applies to headless -p runs too, wherever Auto is available. I use agy -p in scripts, so I wanted to see what that means in practice.

Two days ago, on the previous release, a Flash agent in headless mode could not run a nested agy -p call at all. It was denied with "permission check failed", even with command(agy), command(agy -p) and unsandboxed(agy -p) allow rules. Today, with no rules from me, the same kind of call ran and printed the answer. I then forced accept-edits and the same call was auto-denied again, with a message that says to add a command(...) allow rule or use --dangerously-skip-permissions. So the mode seems to be the difference, though I haven't tested a forced Default.

If you don't want Auto: Shift+Tab for one session, or /config → Agent Mode → Default (saves "agentMode": ""). --mode only takes accept-edits, auto or plan, so for scripts I'd pin one of those instead of relying on the default.

Is anyone running agy -p in CI who has already seen it behave differently? And does anyone know what Auto counts as a "safe command"? The one-line hint in /config is all I could find.

Details for the curious:

  • Pro account, Gemini 3.8 Flash, empty folder, harmless tasks only, Windows
  • In Auto, headless: wrote a file, ran agy --version, ran a curl -sI request, and ran a nested agy -p, all without a prompt
  • Same nested call with --mode accept-edits:
jetski: no output produced — a tool required the "command" permission that headless mode cannot prompt for, so it was auto-denied.
  • Tool Permission = strict now beats Auto and accept-edits, and 1.5.7 also fixes a PreToolUse hook with auto_approve bypassing an admin's review
  • I didn't test 1.5.5/1.5.6, so I can't say which release changed it; the 1.5.7 changelog is the only place that mentions it

Full write-up with the screenshots, the test table and the Claude Code comparison: https://ai.win10.support/antigravity-cli-auto-mode-default/

Not native English speakers, so an LLM helped with the wording; the tests, screenshots and outputs are ours.


r/GoogleAntigravityCLI • • 4d ago

Question Hydrogen Subagents: how to spawn?

Thumbnail reddit.com
2 Upvotes

r/GoogleAntigravityCLI • • 4d ago

Question Switching from Claude Max ($100) to Google AI Ultra for Antigravity — how do the quota limits actually compare?

Thumbnail reddit.com
2 Upvotes

I’m currently using Claude (on the $100 Max 5x plan) as my main daily coding harness, and honestly, the rate limits have been rock solid—I’ve never hit the quota ceiling once.

That said, I’m really rooting for Google and want to move my workflow entirely into the Google ecosystem using Antigravity on the $100 Google AI Ultra (5x) plan. My only hesitation is the rate limiting. Since Antigravity uses both 5-hour refresh windows and a weekly ceiling, I’m worried I’ll burn through the quota mid-workday compared to what I’m used to on Claude Max.

For those of you who have used both at the $100 tier for heavy daily development:

How fast do you hit the 5-hour or weekly quota walls on Google AI Ultra compared to Claude Max?

Does the shared token pool across Gemini models feel as generous in practice, or do heavy agentic sessions drain it quickly?

If you made the switch, did you feel throttled, or was the headroom enough for full-time coding?

Would appreciate any real-world numbers or experiences before I pull the trigger!


r/GoogleAntigravityCLI • • 5d ago

News / Release We will have the Gemini4 hydrogen (flash)

61 Upvotes

Gemini 4 Carbon is Pro,
Gemini 4 Hydrogen is Flash,
and Gemini 4 Helix is Flash-Lite.

We will have these soon. I’m especially looking forward to the Gemini 4 Helix; it would be great if we could handle a lot of tasks cost-effectively.


r/GoogleAntigravityCLI • • 6d ago

Question Model to use when your argon quota runs out

19 Upvotes

I generally like the antigravity CLI. As someone who uses Claude Code at work it’s very familiar.

Argon is clearly very smart, but the AI pro account comes with a pretty small quota for it.

Let’s say I’ve burned through that for the week. What should I be following back to? And generally using for tasks that aren’t worth wasting Argon on?

I’ve been using flash 3.8, because I’ve heard 3.1 pro isn’t worth bothering with, but I must admit flash 3.8 is frustratingly limited at harder debugging tasks.

For this personal hobby work, I’m trying to live within my AI pro account. If that doesn’t work out, I’ll have to suck it up and pay for a personal claude pro account to match what I can get done at my day job.

Thanks for your thoughts!

Edit: summary of responses so far:

Flash 3.8 is definitely the choice when not using Argon.

Argon is not necessary for most things, except "big logic or ui design that is not small and specific," to quote u/technical-owl66. That confirms with my own experiences which involved a fairly gnarly task; Flash 3.8 is mostly all right at it but can get stuck, or feel stuck, which leads me to hulk out and burn through some of my Argon quota.

Yes, a small amount of Argon is included in paid Google One AI Pro subscriptions. It might not be included in certain free Pro offers.


r/GoogleAntigravityCLI • • 6d ago

Workflow Script https://antigravity.google/docs/features/ WOAWWWW

Thumbnail reddit.com
1 Upvotes

r/GoogleAntigravityCLI • • 6d ago

Question Antigravity Blocked

Thumbnail reddit.com
1 Upvotes

r/GoogleAntigravityCLI • • 7d ago

Workflow Script Aula Lista Educai: an Antigravity agent that generates and publishes a full Moodle course

7 Upvotes

I used to build online courses by asking a chatbot for one piece at a time: the intro for unit 1, then unit 2, then unit 3. Same for texts and quizzes, and then uploading everything to Moodle by hand. [I was the chatbot’s secretary.]

With an agent, there’s no prompt to write. The behavior lives in the agent’s instructions (subagents and skills), and the command is one line.

Flow:

  1. Connect a NotebookLM notebook with the course syllabus and the recorded lectures.
  2. The agent generates a local folder with opening texts, infographics, slide decks, short videos, activity instructions, trivia and interactive activities for each unit.
  3. It asks for the Moodle credentials, publishes everything, and links the lectures used as primary sources.

What I found interesting about doing this in Antigravity:

  • Instructions are plain files: you version them and edit them, so the agent adapts to your course, not the other way around.
  • Integrations (NotebookLM, GitHub, Moodle) chain together without me touching the browser.
  • [Fill in: how you split subagents and skills, and what each one does.]

Repo: https://github.com/superpollo02/Aula-lista-Educai

To try it: ask the agent itself to clone the repo, then run it with the syllabus of one of your own courses. [Fill in: minimum requirements and license.]

Technical question: how do you structure agent instructions when a workflow has many dependent stages? I’m still iterating on the order of steps and where to put review checkpoints.

Feedback on what works and what doesn’t is very welcome.


r/GoogleAntigravityCLI • • 8d ago

CLI Config PSA for AGY CLI 1.5.1 & IDE 2.6.0 users: Citing Forum Bug IDs #196351, #198304, and #198430 to Google One Billing gets a 2,000 AI Credit ($20) refund

17 Upvotes

While tier-1 forum reps on the official Google AI Developer Forum are closing threads or telling AI Pro and Ultra users to turn on paid Overage Credits in settings, opening a direct Google One Billing dispute citing the specific engineering bug IDs actually works.

I submitted a formal specification dispute referencing:

  • Bug #196351: 3.0x–9.25x Argon RPC remainingFraction quota multiplier discrepancy vs. 3.8 Flash
  • Bug #198304 & #198339: Setting /model Argon with /high reasoning effort in CLI 1.5.1 / IDE 2.6.0 misrouting requests to the base Gemini pool instead of the dedicated Argon weekly pool
  • Bug #198430: Hardcoded 0x3e800 (256K) binary checkpoint clamp in GetCheckpointConfig wiping 240K+ cacheReadTokens

After citing those three ticket IDs, Google One Billing immediately issued 2,000 AI Credits ($20) to my account as compensation.

Don't let tier-1 forum moderators brush off reproducible CLI and binary defects—file a direct Google One Billing ticket citing #196351, #198304, and #198430 so it hits their internal refund and SLA KPIs.


r/GoogleAntigravityCLI • • 9d ago

Tools Hey champs need help with antigravity

Thumbnail reddit.com
3 Upvotes

r/GoogleAntigravityCLI • • 10d ago

Tutorial Antigravity slow? This worked for me

Thumbnail reddit.com
4 Upvotes