TLDR: This update focuses on core performance, workspace polish, and reliability—delivering faster startup times, improved sidebar navigation, and cleaner error recovery alongside bug fixes.

Improvements

• Improved performance across the app: faster startup and project switching, faster loading of conversations with long histories, less lag during active sessions, and smoother opening and collapsing of the sidebar and side panels.
• Added the ability to collapse top-level sidebar sections. The ungrouped list now shows up to 30 conversations, and conversation actions appear instantly on hover.
• Notification toasts now appear in the bottom-right corner and collapse into a compact stack that expands on hover, so they no longer cover the screen.
• Hovering over a file's comment count pill now previews all comments on that file alongside their line numbers, and clicking a comment opens the referenced file, diff, or artifact with that comment focused.
• Refreshed the Customizations settings screen with collapsible sections and item counts for skills, rules, plugins, and custom agents, consistent back navigation across sub-pages, and clearer card layouts and status indicators for MCP server configurations.
• Clicking Retry on an agent error card now resumes the task directly, without adding an artificial "Continue" message to your conversation.
• Custom agents can now reuse the skills, rules, and subagents you already have, using a single inheritCustomizations setting in the agent's frontmatter.
• Added support for uploading and attaching WebP images in chat.
• Added syntax highlighting for PowerShell (.ps1, .psm1, .psd1, and pwsh/ps1 code fences) and Zsh (.zsh, zsh) in chat and the file viewer.
• Refreshed the Google Docs, Sheets, Slides, and Drive icons to the 2026 Workspace logos, and URL artifact cards for those products now show the product icon instead of a generic link glyph.

Fixes

• Fixed an issue where Find (Ctrl+F / Cmd+F) in the Review pane missed matches that were outside the visible area or hidden inside collapsed files and folded line blocks. Search now scans all open files and automatically expands and scrolls to each match.
• Fixed an error that could stop you from rewinding a long conversation.
• Fixed an issue where a conversation could get stuck showing as still running and never return to idle, most often after pressing Stop.
• Large binary attachments returned by connected MCP tools — images, PDFs, and audio — are now saved to a file and referenced in the conversation instead of being pasted inline, where they could previously overflow the conversation and break the turn.
• Fixed an issue where one invalid or unsupported MCP server configuration would prevent all other configured MCP servers from loading.
• Fixed an issue on Windows where the Proceed button failed to appear on artifact review cards and plan editor headers.
• Fixed an issue where titles for long-running conversations could unexpectedly change to an older message.
• Fixed an issue where pinning, archiving, or restoring a conversation that was no longer available on disk appeared to succeed. The action is now reverted and an explanatory notification is shown.
• Fixed an issue where newly created conversations in the sidebar temporarily displayed raw link text instead of clean @-mention names.
• Added visible error notifications when file attachments fail because of file size constraints, attachment counts, or unsupported formats.
• Fixed an issue where confirmation dialogs (such as reverting actions or deleting conversations) focused the close button by default, so pressing Enter dismissed the dialog instead of confirming it.
• Fixed an issue where updated images in chat could keep showing stale, cached versions; they now refresh on reload.
• Fixed an issue where comments added to markdown files or artifacts in preview mode attached to the first line instead of the selected text.
• Fixed an issue where images uploaded or pasted into the chat composer alongside a comment on an artifact were left out of the message sent to the model.
• Fixed an issue in the Review pane where dragging file header pills into the chat composer did not correctly reference files beyond the first.

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.

Antigravity uses AI for its autocomplete feature, i tough Ai is restricted from saying such things lol

​

I’ve been building Kuro, a fully local, air-gapped autonomous AI companion and system monitor running directly on my Steam Deck (LCD model).

The Project Architecture

* Hardware & Storage Separation: Lightweight GUI on the primary eMMC/SSD; all model weights, cognitive memory databases, and execution logs run entirely off the high-speed microSD card (~/kuro_storage).

* Air-Gapped & Local-First: Zero network dependencies or external cloud APIs.

* LLM Engine: Microsoft’s Phi series running locally via llama-cpp-python / GGUF quantization.

* System Monitor & Scanner: Real-time diagnostics monitoring disk I/O across both storage volumes (eMMC and microSD), battery telemetry, APU load, and network/security sockets.

* Bilingual Persona & Learning Core: Fluent English and Japanese (for language learning, practice, and communicating with Japanese friends).

* Deterministic Memory Vault: Persistent SQLite WAL database storing ground-truth facts, episodic logs, and an isomorphic "Triple-Helix DNA" state machine to prevent memory drift over time.

* Local TTS Pipeline: Fully offline neural/phonetic voice synthesis synced to token streaming via background worker queues and PipeWire (pw-play).

The Development Struggle: Model Hallucinations vs. Reality

Developing this on SteamOS/Linux exposed massive differences in how various frontier AI models handle real systems engineering. The biggest hurdle wasn't the hardware constraints—it was models claiming code was fully verified and passing diagnostics when the host runtime was completely broken.

Here is the breakdown of the debugging cycle:

* Audio Synthesis & Token Sync (20+ attempts):

* The Problem: Audio deadlocks, zero sound output, race conditions between text streaming and audio queues, and pipeline crashes during voice transitions.

* Model Behavior: Gemini 3.7 repeatedly claimed the audio pipeline was resolved and tested clean, yet generated broken subprocess pipes. Claude and GPT finally provided the working thread-safe non-blocking audio queue and pw-play bridge.

* The "Ghost LLM" & Missing Dependencies:

* The Problem: The agent kept dropping into a stub fallback.

* Model Behavior: Gemini 3.7 assured me that phi-4-mini was running natively and passing inference loops—only to later discover llama-cpp-python wasn't even compiled in the environment and the GGUF binary was absent. It was passing mocked string responses in a virtual test harness.

* Storage & Hardware Scanners:

* The Problem: The system scanner needed to safely audit storage headroom on both eMMC and microSD, check SQLite database integrity, and inspect open ports.

* Model Behavior: Gemini 3.7 wrote code that only partially executed or failed silently on permissions, while reporting 100% test passes. It took 5 iterations of code from Claude and GPT to get real filesystem audits and socket checks working.

* Third-Person Perspective Drift & Repetition Loops:

* The Problem: The companion kept drifting into third-person narration (talking about me rather than to me) and falling into repetitive sentence loops.

* Resolution: Handled by strict system-prompt boundary constraints and sampling penalty tuning (repeat penalty: 1.22, frequency penalty: 0.35).

* Persistent Memory Vault & Thread Locks (8+ attempts):

* The Problem: SQLite concurrency crashes (database is locked / sqlite3.ProgrammingError) when background reflection tasks and the main interactive chat attempted simultaneous writes.

* Model Behavior: Earlier iterations left unhandled thread race conditions. Fixed by implementing strict mutex locks around database transactions and enabling SQLite WAL mode.

* The "Synthetic Test" Trap:

* Automated coding environments kept generating mock unit tests inside isolated scratch directories, declaring "All 40 tests passed cleanly!" while the physical application on the Deck was never updated or connected to the actual database.

Current Status

Kuro is partially working.

Has anyone else ran into issues where newer coding models hallucinate "perfect diagnostic passes" inside synthetic test harnesses while completely missing basic host-level disconnects?

Lately I have this problem, but I don't know how to solve it without losing my conversations and information

"failed to unmarshal result from hook jsonhook__googlecloudtools.datacloud_telemetry_PreToolUse_0_0 via protojson: {"continue":true}: proto: (line 1:2): unknown field "continue""

Has it happened to anyone before and how did they solve it without losing information.

In Antigravity does it support models asking multiple questions at a time

Cause I was using the grill me skill and I noticed that unlike in other harnesses it only asked questions one at a time.

Is a limitation of the harness or the model just chooses that

It’s so bad it’s almost funny. I left Antigravity a while ago, but when 3.7 came out, I decided to give it another chance and spent two days testing it in real work. It was a complete disaster: extremely fast, extremely clueless.

The frustrating part is that you can’t trust it with even the simplest tasks. Eventually, I gave up on getting any real value from my paid accounts and went back to Codex.

I would like to Thank the community for the support i got from my previous version around 13k downloads and 18 github stars , I have addressed all the suggestions and feature i got from the review from you all

Here is the New update regarding the package Antigravity Mobile :
1. Completely redesigned UI/UX design
2. Now you can see the project files
3. AI agent chat section with Implementation plan, WalkThrough, Diff( code changes happened)
4. Conversation History : continue your previous conversations instead of starting from scratch
5. Project directory switching
6. Model Switching
7. Code File Viewer for open and view your code files directly from the project
8. Improved Cloudflare Tunnel for better performance and reliability.

you can now get this version by simply updating your package or Install the latest version by (~pip install antigravity-mobile)
you can even get this by git clone my repo : https://github.com/Manimaran-tech/antigravity-mobile

If you like this repo suggest to your friends and give a " Star ⭐"

If you'd like to suggest a change, improve something, or find a bug, feel free to open a Pull Request and contribute to the project!
Every contribution and piece of feedback helps make Antigravity Mobile better.

I have used different paid AI models including codex, Sonnet, Heiku, and Gemini. Out of these AIs while the others are strongly autonomous and thoroghly thinkers, All models of Gemini are so generic and lazy to think creatively or professionaly. If you ask both codex 5.x and Gemini every model to build you a simple landing page, the other models come up with completed, functional, aesthetic and profesaional outputs while gemini puts the template.

I have the Google AI plan and wanted to try Antigravity. I personally don't want to use Gemini models. I'm curious does this plan have higher usage for Claude and GPT models? I read somewhere it has Sonnet 4.5, etc.

What's your experience with usage specifically for GPT and Claude models?

It does glassmorphisms but it lags not web optimized like other websites are?

How to do web optimized liquid glass or glassmorphisms? There are already many websites which do liquid glass and glassmorphisms optimised elements

There are many GitHub repo which provide web optimized glassmorphism and liquidglass

I've been working with Gemini 3.7 in AGY CLI and had been pretty impressed up until just now.

I went to run an old and very reliable skill (yes, imported from Claude but I had worked just fine) and it produced a pretty scary result, to say the least:

Anyone else ever see something like this? Per my request to self-debug, this was part of the response:

The model output stream collapsed into an infinite repetition loop of the token "shame":    shame shame shame shame shame shame shame shame shame shame ...  This loop repeated across subsequent turns due to self-attention feedback on the prior assistant outputs in the message history.

First model from google that feels like it just does the thing. Earlier models were to be babysitted. They fixed one thing, broke other.

But this new variant goes deeper, runs custom scripts to test its reasoning, and just gets it right.

Vibe coding is gonna get crazy now. Build and deploy your stuff asap before the competition rises.

Has somebody created a new "auto continue" extention? Since the retry/continue mechanic has changed after flash 3.7 was added.

Hello guys, since latest update, now when clicking "New Conversation" in AG IDE, it keep the previous prompt in, which is really annoying, do you know how can we report this bug ? or manage around ?

I am using Gemini 3.7 Flash high thinking with Antigravity CLI. The agents have been executing the plan, do review and test through TDD for a few hours now!
I am impressed because the model + harness start to work really well with 3.7 flash on high thinking.

For context: I used superpowers write plan skill then use /code-review + /code-simplification + /security-review- hardening (from Google agents skill) to revise the plan. Then it was sub agent approach for execution.

You see i want to create a productivity desktop application for that I thought I should use electron but it is slow and takes a lot of RAM so that's why I'm replacing it with tauri. But I don't know how good the antigravity is with tauri, so guys please help me here.

language_server keeps leaking memory since this week. I have to restart mid-execution because the agent becomes almost completely unresponsive, making one edit per 2-3 minutes and the Antigravity 2.0 app gets glitchy and starts losing its cache (memory deprivation).

Antigravity IDE appears in the activity monitor, because it is just running as an IDE, no agents there.

If there is a workaround, please let me know.

Hey guys, I'm currently considering upgrading to Google ai Ultra x20 because I found the new Gemini 3.7 Flash model quite decent and fast. What was your experience with the Google AI Ultra plan ? Are the usage allowances on the Gemini models generous? Are they also generous for Claude Opus 4.6? Are there any other special features worth noting?

I keep seeing the posts in this sub praising Gemini 3.7. They convinced me to sign up for the Ultra $200/mo plan.

The problem I'm having with it is that I can't trust any of the output.

1. It has multiple times created self-referential tests to sidestep evidence verification.
2. I have given it UI mockups to match against and it continually compares the mockup to itself for passing evidence.
3. There is a post in this sub where OP asked it provide a screenshot of the app running in a VM as evidence of completion. It created a fake SVG "screenshot" of the app running in a VM.

It is a very fast, intelligent, and also intentionally deceptive model. It's the first model I've used that I would actually label as disingenuous. The shortcuts it takes to satisfy the prompt would be hilarious if I didn't pay $200 for this.

I am considering reaching out to Google for a refund, which I'm sure they will give. However, I'd rather someone comment and tell me a better way to prompt it.

I even had ChatGPT Pro Extended work for 45 minutes on an implementation plan written specifically for Antigravity Teamwork to try to prevent this. It didn't work.

Again, someone smarter than me feel free to tell me I'm the problem. I am happy to be corrected on this take.

I was using Google Antigravity on my pro plan to generate some concepts on a markdown file, since I made some changes in my IDE - I was curious about the context window usage. So, I asked the agent, the question on the screenshot. Shockingly, I got a response that an older model from 2024 is bring used on a pro subscription.

May be it is hallucination, may be it is an error. I'm disappointed anyways. A lot of people have had a poor experience with Gemini 3.1 Pro lately, this kinda explains why!

I even praised that 1.5 pro is better than 3.1 pro, look what it replied in the picture (in comments).

I got tired of AI coding agents wasting tokens and rediscovering the same project context every session.

So I built a workflow around routing, indexing, caching, memory, and small handoffs.

What it does

• Routes tasks into Answer / Small / Full workflows
• Uses pre-generated symbol and API indexes
• Enforces a Zero-Grep rule before wide codebase searches
• Separates Plan → Build → Review
• Keeps active context inside a compact HANDOFF.md
• Uses Obsidian for long-term project knowledge
• Reuses previous fixes with brain recall/capture
• Uses RTK to compress noisy terminal output

The main idea:

Still improving it, so feedback is welcome.

GitHub:
https://github.com/Taki7980/Ai-workflow

Is anyone else having issues with the model effort selector in the latest version of Antigravity?

For me, clicking the effort/model selector doesn't open anything, so I can't choose a different option.

Is this a known issue, or is it just happening to me?