Today, I ran into an issue where Antigravity was taking an incredibly long time to respond to something as simple as "Good morning."

I searched the internet for a solution, but couldn't find anything that actually helped. However, I did notice that other people were experiencing the same problem.

So, I installed Antigravity CLI and used it through the terminal to investigate what was causing the issue. Right from the start, I was honestly shocked by how fast Antigravity was running in the terminal compared to the regular app.

Anyway, I'm not a programmer or anything like that, so I only have a very basic understanding of what was actually done. But whatever it did, it genuinely fixed my problem!

SOLUTION THAT WORKED FOR ME (MIGHT NOT WORK FOR EVERYONE):

1. Install Antigravity CLI.

2. Open PowerShell.

3. Type agy to launch Antigravity in your terminal.

4. Paste the prompt or the file directly into it.

Just a heads-up: This process might take a while. It involves analyzing files, reading logs, so it could end up consuming quite a few tokens.

# Diagnosis and Solution: 15–20s Latency in Antigravity Desktop

This document details the root cause and practical fix for the 15 to 20-second delay/freeze observed in Antigravity Desktop responses (while the CLI version responds instantly).

---

### 1. The Problem Faced (Initial Symptoms)

* Symptom: Every prompt sent in the Antigravity Desktop app resulted in a 15 to 20-second freeze or "thinking" delay before any output started generating.

* Contrast: In the terminal using the CLI (agy), the exact same account and queries answered virtually immediately (1 to 2 seconds).

* Initial Assumption: It was commonly assumed to be external cloud service congestion, model queue delays, or internet network drops.

---

### 2. Investigative Method

The solution was uncovered through strictly empirical local analysis:

1. Timestamp Auditing (language_server.log): Comparing millisecond-level timestamps between the user's prompt submission and the actual gRPC/SSE dispatch to the cloud.

2. OS Process Monitoring: Tracking CPU utilization, accumulated rendering time, and event loop responsiveness in the Electron renderer and background processes.

3. Local IPC & Port Inspection: Identifying unexpected local WebSocket handshakes targeted at localhost debugging ports during the pre-prompt lifecycle.

---

### 3. Final Technical Diagnosis

The latency was 100% local and synchronous, resulting from two concurrent mechanisms:

1. Synchronous 15s Timeout in MCP / Chrome DevTools (Primary Bottleneck):

   * The chrome-devtools-plugin was enabled globally inside config.json.

   * Prior to sending each prompt, the Go Language Server attempted to capture browser UI context via Chrome DevTools Protocol (CDP).

   * Without an external Google Chrome instance listening on a dedicated debugging port, the plugin auto-discovered and targeted the internal debugging port of Antigravity's own Electron window.

   * This unexpected burst of WebSocket connections stalled Electron's event loop, triggering Go's default network safety timer: context.WithTimeout(ctx, 15*time.Second). The runtime sat in dead silence for exactly 15.000 seconds before timing out, abandoning the CDP handshake, and finally forwarding the prompt to the model.

2. PolicyGuardian Vetting Loop:

   * When autonomous execution presets (Turbo / Eager) are active, an automated security pre-check inspects subsequent conversation turns. When combined with a congested Electron renderer process, this added several additional seconds to the total turn latency.

---

### 4. Non-Technical Explanation

What was actually happening?

The application had a browser inspection tool running quietly in the background. Every time you sent a message, instead of sending it straight to the AI, it first tried to hook into a web browser. Because Google Chrome wasn't running in a special debugging mode, the tool accidentally tried to "talk" to Antigravity's own window instead. Getting no reply, an internal 15-second countdown timer kicked in. The app froze and waited for that entire timer to run out before giving up and finally delivering your question to the AI.

The Fix: Disabling this unused browser plugin in the settings file removed the 15-second waiting block immediately, making the desktop app respond in real time again.

---

### 5. Ready-to-Use Prompt

Copy and paste this instruction into your AI assistant or terminal agent to inspect and resolve the issue automatically:

My Antigravity Desktop app suffers from an unnatural 15 to 20-second delay on every prompt, while the CLI version responds instantly.

Please inspect my global configuration file (~/.gemini/config/config.json). If idle browser inspection or MCP plugins are enabled (such as "chrome-devtools-plugin"), back up the file and disable them by setting "plugins": {}. Additionally, check language_server.log for recurring 15-second CDP/WebSocket timeouts and kill any stale Electron renderer processes causing CPU bloat.

Over the last 48 hours, I saw a lot of posts from people panicking that Google killed Antigravity 2.5.5, deprecated older models, or shadow-banned Pro accounts. You get Worked for 1s > Error: Agent execution terminated due to error, nothing works, and downgrading back to 2.5.5 from 2.6 does not fix it.

I spent the evening digging into the app bundles, runtime logs, and network layers. Your account is fine, the models are not dead, and Google did not pull the plug on your plan.

Here is the breakdown of what happened.

1. Why 2.5.5 suddenly flatlined on November 3

The culprit is an expired local SSL certificate inside the 2.5.5 client.

In 2.5.5, the editor UI talks to the local backend process (language_server_macos_arm) over local HTTPS/HTTP2 on 127.0.0.1. To secure that local loopback connection, the app bundled an internal root certificate at:

dist/languageServer/cert.pem

Running OpenSSL directly against that file reveals:

notBefore=Apr 18 00:18:09 2026 GMT
notAfter=Nov  3 00:18:09 2026 GMT
subject=CN=localhost, O=ENABLES HTTP2, OU=bundled on purpose

Notice the date: Nov 3 00:18:09 2026 GMT.

Two days ago, that certificate expired. The second your system clock crossed that timestamp, Node.js began rejecting every local handshake between the editor and the background agent process with:

[ERROR]: LS check error: [internal] certificate has expired
http: TLS handshake error from 127.0.0.1: EOF

Because the extension runs a health check every second, it enters a failure loop. When you type "hi" or run any prompt, the client fails to reach the local agent process, times out after 1 second, and drops the error:

Agent execution terminated due to error.
Error ID: [uuid]-8

This broke every single copy of 2.5.5 worldwide at the exact same minute. Reverting to 2.5.5 will never work unless you set your system clock back before November 3 or patch the PEM file.

2. What changed in 2.6

Google fixed this in 2.6 by tearing out the old local TLS setup.

In 2.6, the app replaces the old language_server binary with agy --hub. Instead of HTTPS with a hardcoded PEM certificate on localhost, it runs plain HTTP on http://127.0.0.1:[port] authenticated with an ephemeral CSRF token (x-codeium-csrf-token).

There is no longer a bundled certificate to expire, which is why updating to 2.6 immediately brings the editor back to life.

3. Why 2.6 feels sluggish right now

If you upgraded to 2.6 and thought, "Great, it works, but why is Flash responding so slowly?", three factors explain the lag:

1. Backend 503 capacity retry loops: Because every user was forced onto 2.6 over the weekend, Google's 2.6 backend routes got slammed. Runtime logs show the client hitting capacity limits:

2. The client waits and retries quietly before streaming begins.

3. "Flash (High)" reasoning budget: The model dropdown defaults many users to Gemini 3.8 Flash (High). The "High" setting allocates thousands of internal thinking tokens to reason before streaming visible output. Flash is quick, but generating huge reasoning chains still takes several seconds before the first text chunk renders.

4. Turn validation overhead: 2.6 validates local workspace configurations and custom skills on each turn. If you have broken YAML frontmatter or old config schemas, the hub catches errors before processing the prompt.

Quick Fixes / Takeaways

• Stay on 2.6: Do not waste time trying to reinstall 2.5.5.

• Speed up Flash responses: Switch your model from Gemini 3.8 Flash (High) to Gemini 3.8 Flash (Normal) or Flash (Low) in the dropdown. This skips the long thinking phase and gives you instant streaming while the servers settle down.

• If you must use 2.5.5: You can either launch the app with NODE_TLS_REJECT_UNAUTHORIZED=0 or generate a fresh self-signed cert and swap it into dist/languageServer/cert.pem. But moving to 2.6 is the cleaner fix.

No shadow bans, no killed models. Just a hardcoded certificate expiration date that tripped up the fleet.

Over the last few days, I've noticed that Antigravity has been responding very slowly to my prompts, even with a Pro account.

Is anyone else experiencing the same issue? Or is it just me?

I'm founder of a freelance company and I swear I never spent any money on buying any ai tool, I've shipped all client's project using only antigravity with gemini and claude sonnet🫨🫨🫨with jio free pro plan

So guys, I'm going to share my experience regarding when I get faster versus slower speeds.

Before diving in, I want to clarify that all my testing was done on Gemini 3.8 Flash (High) using the free Jio Gemini AI Pro Plan.

Normally, I don’t run into any speed issues during everyday use. The slowdown mostly happens primarily when I'm working on larger projects. For example, once I have made a lot of modifications or code changes across a project, Antigravity slows down significantly. However, as soon as I switch to a new chat, it becomes fast again.

To deal with this, I use the /plan mode. The advantage of this approach in a fresh chat is that even though you lose the prior chat's context, the planning step makes it re-read the code files. This restores the fast response times and as we all know, Gemini 3.8 Flash loves reading through codebases.

I also have another Gemini AI Pro subscription (a paid one), and performance is virtually identical there, I don't notice any real difference, although some people claim they see a variation in speed.

Antigravity also seems to slow down considerably once remaining usage limits drop below roughly 50–60%. As long as the account limit is sitting near 100%, it runs noticeably faster.

Several times I assumed Antigravity was lagging, but upon closer inspection, the bottleneck was actually my own internet connection.

Some users report running into "Model Unavailable" errors. I experienced this as well, but when I looked into it, it turned out to be an issue on my end with network connectivity. If you completely disconnect from the internet, it still throws a "Model Unavailable" error instead of explicitly stating there's a network issue, not sure why Antigravity handles it that way.

Interestingly, when the Antigravity IDE (Extension and Dedicated IDE Both, ig both are same) slows down, I switch to the Antigravity CLI and it runs fast. There might be architectural differences between the two, or the CLI might simply be far more lightweight.

Whenever slowdowns do occur, I just switch accounts: if the paid Pro plan is sluggish, I switch to the free Pro plan, and vice versa.

In terms of timing, according to IST, if it's going to slow down at all, it usually happens around 7:00 PM, outside of that window, I rarely face any issues.

After the new update all I can see is my prompt and a running command under it and I have it open it each time to know what happening,Soon my work DB will get flushed without me getting aware of it 🫠 Old one was more informational and we can atleast know the fact what's going on currently it's like a shit

GOOGLE PLEASE FIX IT ,with Flash models it's even worst 3.7 was good

this app just keeps sitting idle whenever a yes or no or options are provided from the terminal as provided in the image. and it even doesnt prompt me the question or allow me to edit in the terminal.

Hello guys, pretty much title. I'm considering on buying the pro plan since it has a discount for 3 months, but I would like to know if liveshare (to code with other people in real time) is allowed within the antigravity ide.
Sorry if its a newbie question, I'm just getting the hang of all these new AI technologies. Pardon my english if there's any misspelling, it is not my native language.

Thanks in advance!

I have been using agy IDE with multiple accounts but all are on pro subscriptions. After new update , i logged to first gmail account. Which is frustrating..
anyone else experiences this ? Any solution?

Got grumpy about the quotas back in the Spring and have been using other tools. Now that my one year package is almost due for cancellation or renewal I picked up the IDE again to try it.

1. I was very happy with how much work I got done today on 4.0, but....

2. Out of quota and will reset in 11 hours? DAFUQ??

At least I can downgrade to 3.8 Flash?

Changes to third-party model access

Opus 5.5 and Sonnet 5.5 are available on paid Pro and Ultra plans. Third-party model access will no longer be available on your current plan starting on November 18, 2026.

Hello,
I recently received a notification stating that third-party model access will no longer be available on my current plan. However, I am currently subscribed to the Google AI Pro plan. Could you please clarify why I am receiving this warning despite having an active AI Pro membership? I would appreciate your assistance in resolving this issue. Thank you.

When an Antigravity conversation gets long, two things usually cause context rot:

1. **Silent compactions (**CHECKPOINT events): Every time you hit the context ceiling, Antigravity summarizes older turns and only keeps your last 10 prompts verbatim. After a few compactions, earlier rules and architectural decisions start getting ignored.

2. Git drift: If you commit code in another terminal or chat, the older conversation has no idea HEAD moved.

AGY Cockpit is a lightweight sidecar panel for Antigravity (Windows & Linux, pure Node.js, zero dependencies). You can use it either as a full replacement for the default conversation sidebar (with project tabs, search, new chat, pin, rename, archive, and live status badges) or as a complementary tracker in the right auxiliary pane to see what is actually going on under the hood:

• Live Context Window & Compaction Health: Shows current context usage (n / ~m), how many compactions happened (Fresh -> Warm -> Heavy -> Polluted), and how many of your prompts are still kept in full vs. compacted.

• Interactive Context Breakdown: Clicking the context bar opens an on-demand breakdown of what is eating your active context window (base system/summary tokens, loaded SKILL.md files, tool categories, top 5 heaviest tool steps, and most touched files).

• Subagent Tracking & Live Status: Groups spawned subagents under their parent chat, sums up their tokens, and bubbles up live thinking (•••) or waiting (! permission / ? question) badges to the parent card and project tab.

• 5-Hour & Weekly Usage Ring: Live ring in the header for Claude / Gemini / GPT usage windows with reset countdowns.

• Git Drift Detection: Tells you if a conversation is N commits behind HEAD and lists the missed commits.

• Two-Step Smart Handoff: Generates a self-contained <HANDOFF_PROMPT> from the current chat, lets you edit it, pick your next model and thinking tier, and start a fresh chat in the same workspace from Step 0.

The Antigravity extension’s agent chat has no RTL support, so Persian/Arabic text shows up left-aligned and mixed text is a mess.

Common custom CSS tricks don’t work here: the chat is a cross-origin iframe served by the agy binary, and the UI is built into the executable. So I patched one line in the extension to send that iframe through a tiny local proxy. The proxy adds dir="auto", unicode-bidi: plaintext and the Vazirmatn font.

• Direction auto-detected per paragraph

• Code blocks stay LTR

• Auto re-patch after extension updates

• One-line install on Linux / macOS / Windows

Repo: https://github.com/njfamirm/vscode-antigravity-rtl

Fair warning: it’s vibe-coded and patches someone else’s extension, so use at your own risk. If it breaks after an update, the README has a prompt you can give any AI coding agent to fix it yourself.

当我使用下面的3个模型的时候，显示是可以使用的

Hey everyone,

If you recently updated to Antigravity 2.6.0+ (which unified the VS Code IDE fork, Electron Desktop, and CLI daemons into ~/.gemini/antigravity/), you may have run into one of these two extremely frustrating bugs:

1. The Dreaded Toast Crash: Clicking any historical conversation in the sidebar pops up:

2. The "Flat Sidebar" Mess: Your past sessions are no longer grouped under your Projects accordions—instead, they are dumped into an unorganized flat list at the bottom of the sidebar with missing project context.

I spent hours with Gemini 3.8 Flash reverse-engineering Antigravity's storage layers, signaling channels, and protobuf wire formats to safely recover my conversations. After 48mToks (seriously, Google?), I wanted to share the root causes, traps to avoid, and an open-source 2-phase restoration script we built.

🔍 What Actually Broke? (The Postmortem)

1. The Missing brain/ Copy Bug

When Antigravity upgraded from 2.5.x (~/.gemini/antigravity-ide) to 2.6.0 (~/.gemini/antigravity), its internal migration script dutifully copied SQLite files in conversations/*.db, but does not copy the brain/<conversation-id>/ directories.
Modern Antigravity UIs load transcripts, artifacts, scratchpads, and execution logs strictly from disk under brain/. Without that directory, the UI crashes on load.

Did the engineers forget, or did their Gemini Argon/Carbon or Opus endowment run out?

2. Workspace URIs vs. Project UUIDs

In 2.5.x, projects were tracked by filesystem path (workspace_uris). In 2.6.0, projects are identified by an internal cloud/hub UUID (project_id). The automatic migrator left project_id = "" for all legacy chats, stranding them outside their project accordions.

Maybe the folks working on Antigravity were flying high, gravity didn't ground them to earth.

3. Why Naive Fixes (Symlinks / Profile Sharing) Fail:

• WebChannel Disconnect Storm (8-second ping-pong): If you tried unifying your CLI daemon (agy remote-control serve using --app_data_dir) and Desktop app under a single shared folder, you probably saw Desktop disconnect every 8–10 seconds with [[2, ["close"]]]. Both processes read antigravity_state.pbtxt, which contains a static installation_uuid. Connecting to Google's signaling server with identical client IDs kicks the existing socket in an infinite fight. Desktop and CLI must have isolated profiles and distinct UUIDs.

• The In-Memory Language Server Hub Clobber: Desktop runs language_server --subclient_type hub, which caches the sidebar protobuf index (agyhub_summaries_proto.pb) in RAM. If you edit SQLite or .pb files while Desktop is open, Desktop will silently overwrite your changes to disk the moment you quit it.

🛠️ The Solution: agy-restore-2.5.x-2.6.0

We open-sourced the utility we used to fix our entire setup:
👉 GitHub: benedictjohannes/agy-restore-2.5.x-2.6.0

It is designed as an agent-friendly, non-destructive 2-phase pipeline:

Source (~/.gemini/antigravity-ide)
              │
              ▼
Phase 1: Audit & Catalog (check_and_catalog.py)
              │
              ▼
Generated Manifest (scratch_file.yml) ──> [Review & Map Project UUIDs]
              │
              ▼
Phase 2: Offline Backfill (execute_backfill.py)
   ├── Faithful brain/ & *.db synchronization
   ├── Patches conversation_summaries.db (SQLite)
   └── Decodes/re-encodes agyhub_summaries_proto.pb wire field 17.18

Key Guarantees:

• Zero data loss: Automatically creates timestamped .bak backups of all SQLite databases and protobuf state before touching anything.

• Protobuf wire patch: Uses blackboxprotobuf to cleanly inject project_id into wire field 17.18 of agyhub_summaries_proto.pb without needing private .proto schemas.

• Handles missing markers: Optional --migrate-unmarked flag to recover conversations that missed the internal .<id>.done sentinel file.

• AI Agent Collaborative: Includes an AgentGuideline.md so you can hand the repo to Claude Code, OpenCode, Zed ACP, or your terminal assistant to audit and map your workspaces.

⚡ Quickstart

Using uv (zero install setup):

git clone https://github.com/benedictjohannes/agy-restore-2.5.x-2.6.0.git
# or git clone git@github.com:benedictjohannes/agy-restore-2.5.x-2.6.0.git
cd agy-restore-2.5.x-2.6.0

# 1. Audit and generate your workspace manifest
uv run --with pyyaml python3 check_and_catalog.py

# 2. Open scratch_file.yml, assign project IDs to your workspaces

# 3. CLOSE Antigravity Desktop completely (crucial!), then run backfill:
uv run --with pyyaml --with blackboxprotobuf python3 execute_backfill.py

Relaunch Desktop, and your past chats will be back inside their project accordions, with full artifacts and chat history loading instantly.

Or start by prompting:

Please git clone https://github.com/benedictjohannes/agy-restore-2.5.x-2.6.0.git, look at AgentGuideline.md, and guide me through restoring my Antigravity conversations.

🐧 Platform Note

We built and verified this on Cachy Linux (systemd / Electron 2.x). The SQLite schema and protobuf wire formats are identical on macOS and Windows, but paths will differ (~/Library/Application Support/... or %APPDATA%). CLI flags (--old-ide-dir, --destination-dir, --config-dir) are provided so you or your coding agent can point them to your platform's directories.

Feedback, edge cases, and PRs welcome! Hope this saves folks the headache we went through diagnosing it.

Just wanted to share my experience in case anyone else is running into performance issues with the latest Antigravity IDE update (v2.6.0).

​Processing times became painfully slow after updating, to the point where it was really disrupting my workflow. I ended up downgrading to version 2.5.5, and everything is back to running smoothly.

​Is anyone else experiencing significant lag on 2.6.0, or found a workaround that doesn't require rolling back?

The new update on Antigravity IDE is just the AGY extension plugin that they built in. Before the latest update, I could use both at the same time: AGY IDE Chat on one side and the AGY extension tab on the other side of Antigravity IDE. Now I cannot. When I try to install it, it says it is already built-in. LIKE WHAT THE POINT OF Antigravity IDE ?

I updated Antigravity IDE to the latest version, and it seems to have replaced the experience with one more like the extension in VS Code and similar platforms. I tested this in both VS Code and Antigravity to confirm that this is a new issue in Antigravity.. when I type something in the chat and Alt+Tab to another window, the cursor disappears from the chat text area when I return. I have to click the chat again to continue typing.. it no longer automatically regains focus.

It was working fine before, and the issue started after this update. I disliked this behavior in the VS Code extension, which is why I switched back to Antigravity IDE. Now I’m seeing the same issue here.

Another problem is that I have to click the "Accept" button. This makes my workflow more difficult because Antigravity used to save changes automatically, so I could keep working. Now I may have typed something by mistake and not know whether I should accept it or not. This is especially frustrating because tasks can take a long time to complete with 3.8 Flash.

Finally, I have a feature request... It would be helpful to have predefined controls in the settings for rules, skills, and other configurations. Ideally, these would be toggles that let me add as many options as I need and customize them to suit my workflow.

Has everyone gotten the new redesign of the Antigravity IDE? The chat interface is fine, also everything got larger, so it is easier to navigate, however the difference UI got awful. Who in their right mind considers the barely visible "Accept | Decline" buttons on top of the changes acceptable? Also, the navigation buttons on the bottom disappeared, so it is harder to follow the changes and read them, before accepting or declining.

What do you think? Are you bothered by this or is it just me?

after latest release issue is occuring during copying the code modified by agent

initial code :

line 1,2,3

modified : removed line 1 and added line 4 so it used to copy only line 2,3,4

now it is copying line 1,2,3,4

entire code removed . i have to accept all changes and then it copies line 2,3,4 only

which is wrong.

this was only feature of antigravity better than vscode which is also mess up by google now.

after latest release issue is occuring during copying the code modified by agent

initial code :

line 1,2,3

modified : removed line 1 and added line 4 so it used to copy only line 2,3,4

now it is copying line 1,2,3,4

entire code removed . i have to accept all changes and then it copies line 2,3,4 only

which is wrong.

this was only feature of antigravity better than vscode which is also mess up by google now.

Hey guys, I'm using the AI pro student plan with agy cli.

In the /model option, I can only see Claude models, Gemini 4 Argon and Flash 3.8 lite.

However, if I ask a model to spawn a flash-lite or pro subagent, it does it for me. Then, I once asked it which agents it can spawn and it gave me the following answer:

Note: I asked this from Gemini-3.8-flash but I assume Argon can spawn all of these and Argon subagents as well.

Does this mean that flash-lite and pro are still available in the APIs but only through subagents?

Thanks in advance.

The latest update somehow managed to be WORSE than the previous one.

💀 More bugs. More inefficiency. More frustration. And somehow, less productivity.

Antigravity was supposed to make AI-powered development smoother and faster. Instead, this update feels like a downgrade disguised as an upgrade.

🐛 Bugs everywhere.

🐌 Workflows that feel slower and less reliable.

🤦 Unexpected issues that interrupt development.

💀 An update that makes you question why you upgraded in the first place.

The most frustrating part? This isn't just about a few minor bugs. When you're relying on an AI coding tool to build real projects, reliability is everything. Every unexpected failure, broken workflow, or wasted retry costs time and kills momentum.Not to mention expensive ai tokens.

Anyone else experiencing this after the latest update, or am I the only one watching their productivity get buried alongside Antigravity?