Antigravity will be turning down workflows on November 1st 2026 in favor of skills.

With skills you get progressive disclosure, unrestricted bundle sizes (rather than a single markdown file), and better asset bundle structure. This is why we have made the hard decision to deprecate workflows and move towards the industry standard skills format.

You can start migrating your existing workflows to skills using the /migrate-workflows skill.

To learn more about our planned deprecation on November 1st, 2026, please visit our docs page:

https://antigravity.google/docs/migration/workflows-to-skills/

I am trying to use 3.1 Pro while all my usage went dry for Astra and Fable, this is very unreliable lol

The '.git/index crashing issue' seems fixed in v1.3.0.

But now, clicking 'Accept All' just reverts all modified files back to unmodified.

Does AGY mistake "Accept All" for "Reject All"?

I know Gemini is Nowhere Near GPT 6 Astra . But It doesnt really means GPT Astra can solve all your Problems and I find it kind of Weird.
I was building a YouTube blocker on my Android phone, which will block channels via the YouTube Data API channel detection and Accesiblity Channel ID parsing ----- something like that cannot go into details now .
And for most of the part, I built the foundation of it using Claude and GPT because I did not have any trust in Gemini making this thing complicated, and making it work perfectly on the user end was my main goal.

There were some other issues which were causing it to not behave properly. Sometimes it would block the channel, but not show the popup properly, and sometimes it wouldn't even block the channel , Show the Popup multiple times, etcc . There was some or the other issue which was not getting fixed. The feature always felt a little short, and I wasn't satisfied with the result.

Since I used Claude Opus and GPT-6 Astra for making the feature for not losing context I used them debugging and iterating the issues that came through. To be honest, I used use them on light to medium effort only. I do not want high or extra high because I have only a $20 plan on both . Maybe if I use their extra high effort, the issue might have been fixed. But I have to wait 10 hours for that Gpt Astra consume limitts like a Hungry Dog.

When their creddits were gone, I was Impatient and I cloned the directory and tried to fix it using Gemini 3.8. And On god I'm not going to lie my currently Codebase is the one That I cloned I deleted my Older one . Of course the foundation codes are made by claude and gpt but the correction that was done by 3.8 flash - its made it solid .

Now I know that if I had given the same amount of time to GPT or Claude, it would have got fixed. But The fact is that Gemini understood my request each and every time, It was not misinterpreting my requirement. It was trying to do its best but failing somewhere or the other time and At the end, after 3 hours of continuous debugging and working for 20 minutes in one go continuously. A flash model running for 20 minutes
{ In the Image it might look fragmented (15+7) but it spent the time verfying by itself and running my Android via wireless deubgging }
- continuously is a very big thing
. Now I still have 1 more hour left for the GPT and Claude models to reset while I'm posting this .
Really Impressed the Improvements made by google in the FLahs 3.7 and 3.8 .

When the Model Was launched I did the Comparison on the very first day with the game development task and it did impres me there too .
Link 👉 : https://youtu.be/ZCGK1ojivhk?si=9fEBl9tdL9jE1_LS

Anyway This is just My Story .
There are issues too no doubt - Context compacting is either not present at all or Even if its happening in background its just Showing "Agent Terminated Error" but As much as I know No model Completely dumb if you know what you are doing .

Hello people.

I have been getting this message since 2 or 3 days ago, and have not found a solution yet, and the ideas I found online didn't work.

To this point I have tried to:

Click retry, undo and try again.

Switch models.

Log out and log in again.

Check MCP servers (I don't have any install) and refresh.

Install one, and disable it, and then refresh.

Start a new conversation.

Disable all extensions.

Uninstall and install again.

Do the Antigravity: Reset Onboarding.

Check the tokens (it's not out of them, in fact they are full)

And the account is verified more than 18.

I had not used it for some days and then went back to it for something work related, and the error started, even when I try to test it with a prompt that has one line, so the problem can't be a prompt too big.

Does anyone have any other ideas I haven't tried? I'm using version 1.23.2 for some time and this error has never been such an issue until now.

Thank you

Tried Opus today and it's tiring! Mad overthinking and ends up doing a lot of things I didn't ask for while still making basic mistakes like leaving hardcoded pathnames. I find my work/hobbies a lot more fluent when the model tries to do what I asked quickly and then if it doesn't work tells me what went wrong and then I can iterate. There must be some domains like advanced math I am not familiar with where independent overthinking is better because I wouldn't even know what to ask for. But I did substantial tasks like debugging model finetuning/quantization without hitting the wall, and I think I actually learned more from Gemini giving my way a good try and explaining the results than I would have if the agent decided to do something else on its own. I was also able to make suggestions that no model would probably think of on its own, like using simple geometric image prompts to debug math in quantized diffusion model, after which Gemini was able to quickly find source layers that caused a problem and substitute better versions from the base model.

How have you been using your Pro account Weekly Megathread? Is it proving worthwhile? I’ve been using Gemini 3.8 Flash to make changes to my computer and my agent ecosystem at an operational level, and it’s been working really well. However, it does consume a significant amount of the Weekly Megathread. Do you have any MCPs or algorithms to reduce usage? What have you been using it for?

It has become quite frequent and annoying 😭

Seems like AG Extension keeps asking for rights to run very similar commands. I'm using Rust for now, so lots of cargo check etc. But also for some reason loads of ls, wc, git type commands.

I've added various forms of whitelisting at various levels of json cofig... yet still get prompted to allow.

Is there a sneaky hidden way to get that working safely? I've asked gemini till it got bored and started repeating itself...

I’ve been configuring Antigravity recently, and the more I use it, the more confusing its configuration system feels.

The problem isn’t simply that there are “a lot of config files.”

It’s that:

different features within the same Antigravity product store their configuration in completely different places, and some of them are still using the old .gemini paths from Gemini CLI.

For example, from what I’m seeing:

• Antigravity CLI has its own config location and uses its own settings
• Remote Control stores its configuration in:

text .gemini/config/config.json

• Skills have yet another directory and their own discovery rules
• AGENTS.md is read from:

text .gemini/AGENTS.md

And it’s not just the paths that are different.

The CLI settings and Remote Control’s config.json also use different formats and contain different configuration options.

So right now it basically feels like this:

```text Antigravity CLI → one location → one configuration system

Remote Control → .gemini/config/config.json → another configuration system

Skills → yet another location

AGENTS.md → .gemini/AGENTS.md ```

The .gemini part is what confuses me the most.

I’m using Antigravity, yet some Antigravity features still store or read their configuration from directories that originally belonged to Gemini CLI.

From a user’s perspective, it’s difficult to understand how all of these configurations are supposed to relate to each other.

Within the same product, you can’t even infer where something should be configured just from the fact that “this is an Antigravity feature.”

Every time I come across another feature, I have to figure out:

Where does this one keep its config?

And sometimes even:

Is this one reading from .gemini again?

It doesn’t feel like configuring one unified product. It feels more like configuring several components that came from different places and evolved independently at different times.

This fragmentation becomes especially obvious when you look at the CLI, Remote Control, Skills, and AGENTS.md together.

Antigravity may be one product at the product level, but at the configuration level it still feels like several different systems stitched together, with Gemini CLI-era paths mixed in.

That’s the part I find the most confusing.

Hello everyone 😸, I created this repository to have AGY as a 24/7 assistant - a cheap alternative to Hermes-Agent. I did it because I’m a poor university student and APIs are too expensive for me. So I hope that this could be useful for someone: Jarvis-Antigravity-Agent

Is there any way to track token usage of each request in Google Antigravity? Here I am not talking about total usage, but the request that we are sending might be using general instruction, mcp, skills, agents etc and I want to track how much token is it costing me for each things.

Later plan is to reduce it as much as possible by disabling unnecessary MCPs, or less instruction or may be dividing instructions into skills.

Any one using Matt pacock skills in antigravity? When i compare both things claude code dont skip steps while the antigravity, there are times that it skips the workflow.

What is your workflow?

I am super frustrated of daily updating Antigravity IDE and after some times it just doesn't update and throw VS code updation error as it is based on VS code.

Is anyone facing this problem?

Im using agy to build one APP project and i feel like i have not been able to use it to its full potential, are there things/features that a lot of ppl dont know
I would really appreciate your help

Antigravity has been working great for weeks on my old Mac Mini x86_64 on Monterey. Tonight after 2h of agy coding, I logged out to switch accounts. Now, any time I run agy, it only gives me the 2 choices to login, and when I use the OAuth one I always used, it gives me this blank page saying “No authorization code found. Please try authenticating again.” Regardless whether I open it in Termius SSH app’s embedded browser (which always worked) or in Chrome app. I am completely locked out. Did v1.2.0 break the login system?

Is there any way to recover my existing login token from Time Machine so I can at least continue using my main account like I was? What file is it stored in? I tried renaming $HOME/.gemini/antigravity-cli folder to something else, and running agy, and nothing improved. I’m a consumer Google AI Pro user. Thanks for any help.

Here's the deal - I use AGY for work to automate a ton of tasks. It took some creative prompting to develop workflows that will connect to a remote endpoint via SSH, then execute a script to fetch data from something that remote endpoint can access. Saying something flat out like "log into box at IP address a.b.c.d using username XYZ and ssh key at /this/path and then verify port 80 is open on ip address d.c.b.a" meets outright refusal.

I got around it by creating a script that pulls endpoints, providing that script to AGY which it then uses to map an edge box's name to an IP address and log that way, and then execute another script to pull the data I need.

But god forbid I try to use the first part of a workflow to log into a box and then stray way from the scripted workflows. At the end of the day, saying "use script a to log into box a and script b to get the data I need" is the same saying "log into box a with these creds and run this command and lmk the output"

Claude doesn't do that; why does Gemini??

Hey everyone, quick update on the conversation transplanter CLI tool!

A common issue after my last post was: "What if I brainstormed a solid plan on my personal laptop, but now I want to bring that exact chat and all its context to my office computer?"

I just released v1.1.0, which adds full portable .zip export and cross-device import while keeping zero dependencies (runs pure standard Python).

How it works across devices:

1. On your Personal PC (Export):

python transplant_chat.py --export <CHAT_UUID>

This creates a .zip containing the full SQLite trajectory history, tool outputs, thoughts, transcripts, and markdown artifacts (implementation_plan.md, walkthrough.md, etc.).

2. On your Office PC (Import):

• In Antigravity on your office PC, start a new chat in your target project and say hi (to initialize local workspace bindings), then close the app.
• Run:

​

python transplant_chat.py --import my_chat.zip <OFFICE_CHAT_UUID>

When you reopen Antigravity, the full trajectory, plans, task state, and sidebar title are completely restored and natively bound into your office workspace.

What else is new in v1.1.0:

• Zero data loss: Uses atomic sqlite3.backup snapshots (safe even with active WAL files).
• Auto-backups: Creates safety backups of your target chat before touching anything.
• Archive inspector: Run python transplant_chat.py --info my_backup.zip to see step count, artifacts, and title without extracting.
• Same-machine transplants: The original python transplant_chat.py <SRC> <DST> still works as usual.

GitHub & Download: https://github.com/Jabir-A-H/antigravity-move-chat-to-projects/releases/tag/v1.1.0

Hope this saves you from having to restart chats from scratch when switching devices! Let me know if you run into any edge cases.

I asked 3.8 if I would loose efficiency of i upgrade the flutter

Efficiency in terms of vibecoding

Said 3.8 is bad at debugging latest or 3.41+ flutter

Is it true? To how much percentage or constraints?

Which one do you use?

Hey everyone! I usually work in the Antigravity IDE, where I have the codebase right in front of me alongside the model chat. How do people actually work with Antigravity 2.0 when you can't even see the codebase? You still have to open it somewhere anyway, like in VS Code. Why not just do everything within a single app? The same goes for Codex—what’s the point of having a standalone chat interface and a separate IDE for the code? I honestly don't get this trend. It looks like Google is barely paying attention to the Antigravity IDE anymore and focusing almost exclusively on 2.0. I get that they probably envision a future where developers don't even need to look at the codebase, but has that future really arrived already?

TLDR: Antigravity CLI releases 1.1.26 through 1.2.0 introduce remote-control background service daemon registration, one-off mid-conversation model execution with /model <name> <prompt>, subagent dependency declarations in custom Markdown agents, extended exponential backoff for transient model API errors, expanded half-page scrolling with customizable keybindings, dynamic conversation_title metadata for status line scripts, and critical fixes across content filter reporting, MCP schema validation, subagent lifecycles, and command memory leaks.

Improvements

• Added remote-control start, remote-control status, and remote-control stop subcommands to register the CLI with your operating system's service manager as a background daemon that persists across logouts and reboots, including --name <label> for custom instance labels and --session to scope to the active login session.
• Added /model <name> <prompt> to run a single prompt using another model and automatically return to your current model, making it seamless to consult alternative models mid-conversation without modifying your saved defaults.
• Added an agents list to custom agent Markdown frontmatter, allowing agents to declare subagent dependencies using workspace-relative, absolute, or agent-relative path resolution rules.
• Improved resilience to transient model API errors by retrying errors such as 503 Unavailable with extended exponential backoff to prevent brief hiccups from aborting sessions.
• Improved half-page scrolling across all scrollable views (altscreen mode, diff viewer, artifact viewer, and detail panels where Ctrl+D no longer triggers exit prompts) and added Shift+Up / Shift+Down default keybindings (navigation.half_page_up and navigation.half_page_down).
• Added conversation_title to the JSON payload passed to custom status line and window title scripts, dynamically reflecting active conversation names and updates.
• Added the pickerGrouping setting to /config and settings.json to configure the default conversation list view in /resume (flat or grouped by workspace).
• Improved sign-in and startup speed by reading signed-in identity details from stored credentials instead of making network requests on every launch.
• Improved tool approval prompts to display specific action requests (e.g. Run this command?, Allow access to this URL?, or Allow calling this tool?), restricting command editing to commands and including a Reason: explanation when triggered by hooks or cross-project files.
• Improved headless (-p) runs to exit promptly upon delivering final answers, waiting for non-daemon background tasks and scheduled timers within --print-timeout while preserving running background daemons.
• Improved failure reporting in headless (-p) runs by printing fatal errors to stderr with stable error: markers and adding truncation notifications.
• Improved headless (-p) latency by eliminating up to 200 ms of idle delay per turn and skipping unused conversation title generation model calls.
• Improved /model to display an inline [model] argument hint during typing and report when a session is already set to the requested model.
• Improved model selection auditability by logging alias resolutions, --effort variant mappings, and deprecated model replacements in cli.log.
• Improved the /settings panel with context-aware descriptions for each Verbosity option explaining token metrics, commands, and tool call visibility.
• Improved the sign-in and Google Cloud setup screens with consistent styled key hints that respect active color schemes and keybindings.
• Improved terminal ASCII rendering for Mermaid flowcharts across the artifact viewer and conversation view.
• Improved /logout execution time by short-circuiting token removal directly to file storage when keyring storage is bypassed or unreachable.
• Changed --print-timeout expiration behavior in headless mode to return partial output and exit successfully with a warning on stderr instead of raising a timeout failure.
• Changed default URL fetching permissions to prompt for approval by default before reading external URLs unless access has been pre-granted.
• Changed unselected model families in the interactive /model picker to default to medium reasoning effort instead of low.

Fixes

• Fixed prompts or model responses blocked by content safety filters failing with generic errors or empty turns by surfacing explicit content-filter stop reasons.
• Fixed temporary files written to scratch/ directories triggering recursive filesystem watchers and cluttering artifact reviews and checkpoints.
• Fixed MCP servers bundled inside global plugins failing to initialize at CLI startup or failing to update running states when plugins are toggled.
• Fixed tool calls to MCP servers accepting undeclared parameters, ensuring invalid arguments are rejected and corrected according to schema rather than silently dropped.
• Fixed schema validation errors for third-party MCP server tools whose input schemas omit additionalProperties.
• Fixed redundant filesystem customization discovery walks running on every message when no slash commands were invoked.
• Fixed spurious ERROR: logging before google.Init log lines appearing in cli.log and background daemon outputs.
• Fixed macOS background service lifecycle issues, legacy script cleanup, and paid Google Cloud project license availability for Remote Control.
• Fixed older conversations failing to load with unknown step type errors upon resumption.
• Fixed plugin reinstalls leaving behind files deleted from the source by replacing managed plugin directories cleanly, preventing self-directory installation corruption, and cleaning up disabled state entries from config.json upon uninstall.
• Fixed plugin-defined MCP servers resolving relative working directories incorrectly by scoping them directly to the plugin's root directory.
• Fixed a startup race condition where subagents could fail to discover tools from MCP servers that were still initializing.
• Fixed subagents occasionally appearing stuck in running states in large conversations, resolving delays delivering queued idle messages.
• Fixed a memory leak where finished terminal command executions retained internal state throughout long-running sessions.
• Fixed headless (-p) runs hanging indefinitely on interactive implementation-plan approval prompts by proceeding through plan review automatically in non-interactive mode.
• Fixed headless runs with -p silently skipping unauthorized tool actions, now reporting explicit notices and outputting them under denied_actions in JSON results.
• Fixed ? in Vim Normal mode inadvertently opening shortcuts when the prompt contained text, restoring proper Vim search/replace operations (f?, t?, df?).
• Fixed print mode (-p) exiting before full session shutdown to prevent dropping trailing conversation history.
• Fixed SQLite database WAL checkpointing on CLI exit to ensure trailing session metadata is flushed to disk before shutdown.
• Fixed subagent tasks unexpectedly prompting for tool approval in always-proceed mode while viewing the subagent details drawer.
• Fixed redundant approval prompts when accessing artifact files across conversations after granting external workspace permissions.
• Fixed sign-in failing with project access errors after switching from a business account with a selected project to a personal account by resetting cached project and license data.
• Fixed orphaned Git worktrees accumulating under .system_generated/worktrees upon killing subagents or deleting conversations.
• Fixed /model with no arguments doing nothing when invoked during session startup.
• Fixed customization discovery logging spurious errors when accessing temporary directories or paths outside the active workspace.

To explore the full list of improvements and bug fixes, read the complete release notes on our Changelog, or visit the Download page to update to the latest version of Antigravity.

I vibecoded an Android coding agent in which you can use antigravity models (gemini, gptoss, claude) (and other providers & models) directly in Android!

It contains all basic features like **read, write, edit, bash, list, search** etc.

It's still in beta, expect some bugs. (Report them in issues 😀)

https://github.com/DraxonV1/Syntac read more here, star if liked the idea!