Upgrade Antigravity CLI to 1.2.15 and load global rules from ~/.gemini/config
Antigravity 1.2.15 can finally read ~/.gemini/config (AGENTS.md, GEMINI.md, rules/, skills.json, and related files), scopes repo always-allow to the subcommand, and respects permission denials. Upgrade, place standing rules there, and treat denials as final.Why this loop
Release 1.2.15 unblocks the agent from reading global rules and customization files in ~/.gemini/config, including rules/, AGENTS.md, GEMINI.md, skills.json, rules.json, plugins.json, and agents.json. It asks before editing those files; other files in the folder stay off-limits. Symlinked ~/.gemini/GEMINI.md, ~/.gemini/AGENTS.md, or their config counterparts no longer inject the same rules twice. Always-allow for repo is now the subcommand only (e.g. repo status), matching git, hg, and jj. Unapproved permission requests—including from a subagent that cannot prompt—are respected; the agent will not retry via other commands, scripts, or tools. Interactive -p "/usage" shows quota reset times in local time; pipes and --json stay UTC. Low credits now fail immediately with "Your AI credits balance is too low to continue." instead of a ~2.5 minute Working... retry. Android users can run prebuilt native binaries in Termux without proot-distro. Upgrade first so these config, permission, and quota behaviors actually apply.
Proposed actions
- Upgrade Google Antigravity CLI to 1.2.15 now so ~/.gemini/config rule loading, subcommand-scoped repo always-allow, hard permission denials, local-time -p "/usage", and native Termux binaries all apply to the next session.
- Write standing agent instructions to ~/.gemini/config/AGENTS.md, ~/.gemini/config/GEMINI.md, and ~/.gemini/config/rules/, and keep skills.json, rules.json, plugins.json, and agents.json in that same folder. Tell the agent those files are readable and it must ask before editing them. Do not store secrets in other files under ~/.gemini/config—they stay off-limits. If you symlink ~/.gemini/GEMINI.md or ~/.gemini/AGENTS.md to the config copies, 1.2.15 will not inject the same rules twice.
- When the always-allow prompt appears for a repo command, approve only the named subcommand (for example repo status), not every repo command—the 1.2.15 suggestion is now limited the same way as git, hg, and jj.
- Deny any permission request you do not want executed, including requests raised by a subagent that cannot ask you; after 1.2.15 the agent respects the denial and will not work around it with other commands, scripts, or tools.
- In an interactive terminal, run the CLI with -p "/usage" to print quota reset times in your local timezone; keep piped and --json output for scripts that still expect UTC. If a run fails with "Your AI credits balance is too low to continue.", stop retrying—that message is immediate and replaces the old ~2.5 minute Working... spin.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costGoogle Antigravity / agent task
DevAgentRadar → Google Antigravity
Goal: turn this release signal into a safe pilot plan for my stack.
Context
Assistant: Google Antigravity Proposal: Upgrade Antigravity CLI to 1.2.15 and load global rules from ~/.gemini/config Summary: Antigravity 1.2.15 can finally read ~/.gemini/config (AGENTS.md, GEMINI.md, rules/, skills.json, and related files), scopes repo always-allow to the subcommand, and respects permission denials. Upgrade, place standing rules there, and treat denials as final. Primary source: https://github.com/google-antigravity/antigravity-cli/releases/tag/1.2.15
Why it matters
Release 1.2.15 unblocks the agent from reading global rules and customization files in ~/.gemini/config, including rules/, AGENTS.md, GEMINI.md, skills.json, rules.json, plugins.json, and agents.json. It asks before editing those files; other files in the folder stay off-limits. Symlinked ~/.gemini/GEMINI.md, ~/.gemini/AGENTS.md, or their config counterparts no longer inject the same rules twice. Always-allow for repo is now the subcommand only (e.g. repo status), matching git, hg, and jj. Unapproved permission requests—including from a subagent that cannot prompt—are respected; the agent will not retry via other commands, scripts, or tools. Interactive -p "/usage" shows quota reset times in local time; pipes and --json stay UTC. Low credits now fail immediately with "Your AI credits balance is too low to continue." instead of a ~2.5 minute Working... retry. Android users can run prebuilt native binaries in Termux without proot-distro. Upgrade first so these config, permission, and quota behaviors actually apply.
Suggested actions
- Upgrade Google Antigravity CLI to 1.2.15 now so ~/.gemini/config rule loading, subcommand-scoped repo always-allow, hard permission denials, local-time -p "/usage", and native Termux binaries all apply to the next session.
- Write standing agent instructions to ~/.gemini/config/AGENTS.md, ~/.gemini/config/GEMINI.md, and ~/.gemini/config/rules/, and keep skills.json, rules.json, plugins.json, and agents.json in that same folder. Tell the agent those files are readable and it must ask before editing them. Do not store secrets in other files under ~/.gemini/config—they stay off-limits. If you symlink ~/.gemini/GEMINI.md or ~/.gemini/AGENTS.md to the config copies, 1.2.15 will not inject the same rules twice.
- When the always-allow prompt appears for a repo command, approve only the named subcommand (for example repo status), not every repo command—the 1.2.15 suggestion is now limited the same way as git, hg, and jj.
- Deny any permission request you do not want executed, including requests raised by a subagent that cannot ask you; after 1.2.15 the agent respects the denial and will not work around it with other commands, scripts, or tools.
- In an interactive terminal, run the CLI with -p "/usage" to print quota reset times in your local timezone; keep piped and --json output for scripts that still expect UTC. If a run fails with "Your AI credits balance is too low to continue.", stop retrying—that message is immediate and replaces the old ~2.5 minute Working... spin.
Config surfaces this release may change
- agent context files — check your repo before applying
- skills — check your repo before applying
- MCP servers — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/google-antigravity-1-2-15-upgrade-antigravity-cli-to-1-2-15-and-load-glo and mark Applied, Skipped, or Failed. Proposal id: 5ae3c311-355f-44a4-8fc3-6fd3cc0e9514
Please:
- Map the change to concrete pilot steps
- Flag security / permission implications
- Keep the pilot reversible
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.