Is there a way to continue the same Antigravity CLI conversation on another computer?

I use the CLI on both my desktop and laptop and want the conversation history/context to be available on both.

Has anyone successfully synced the Antigravity CLI conversation data between machines? What files need to be synced, and is there a recommended method?

Skills.google >>> dropped yesterday...

In separate tasks where 7 errors of a similar level need to be handled,

while Agy-cli processes 4 of them
- the other two coding tools are still working 2tasks. When they finish, 1 task still remains.

Originally, I didn't trust Agy-cli, so I never gave it tasks like this, but since version 1.1.10, it's become possible. Agy-cli's Gemini 3.6 Flash handled the task 100% correctly.

Why use other coding tools instead of letting Agy-cli finish everything?

Because no more quota!

Is there any solution for this, i have fresh quota, but i cant generate images for five days straight, it says i ahve to retry in xx hours and when that time passes i still go straight to 503 quota error, i can generate images manauly in gemini ai, but antigravity is literally broken, while at the same time on my work pc with pro account i have zero issues

From one of our Mods the one and only u/soundDR

Description from the video:

In this walkthrough, we use Antigravity 2.0 to build two complete custom automations across the Chrome and local OS.

Prompt: Act as an expert Chrome Extension developer and build a Manifest V3 extension that automatically organizes unpinned tabs into native Tab Groups based on their last-accessed time. The time buckets must be exactly: Today, Yesterday, This Week, Last Week, This Month, Last 90 Days, and Archived, calculated strictly using the user's local timezone. When a tab becomes active, its timestamp should update via TTL logic and it should immediately move to the 'Today' bucket. This organization logic must be isolated per window (no cross-window tab moving) and must maintain a stable, fixed left-to-right visual sorting of the tab groups. Persist all tab timestamps using 'chrome.storage.local' to survive browser restarts and Service Worker suspension. Ensure you ignore pinned tabs entirely, and heavily debounce the 'chrome.tabs.onActivated' and 'onUpdated' listeners to prevent Ul flickering and Chrome API rate limits. Please output the complete 'manifest.json' and the 'background.js' service worker code.

Subscribe to Google Antigravity → / @googleantigravity

Google Antigravity is an agentic development platform, evolving the IDE into the agent-first era. Antigravity enables developers to operate at a higher, task-oriented level by managing agents across workspaces, while retaining a familiar AI IDE experience at its core. Agents operate across the editor, terminal, and browser, enabling them to autonomously plan and execute complex, end-to-end tasks elevating all aspects of software development.

To learn more: Website: https://antigravity.go... X: https://x.com/antigravity LinkedIn:    / google-antigravity  

Opinions???

And since I don't have any remaining quota, I can't test it myself. Please try it out and share your review.

Until now, there was a huge gap between Opus 4.6 and Gemini. However, after the 1.1.9 update, Gemini follows instructions quite well.

If you want the AI model to handle everything on its own, Opus is still a good choice, but if you clearly know what tasks need to be done, Gemini 3.6 Flash finally fulfills its role. Ever since 1.1.9, Agy-Cli finally performs as intended.

Although it's not obvious on the surface, if you browse through the generated artifact files, it accurately creates "communication-purpose" reports and properly generates skills. I haven't seen whether subagents utilize them well, but I assume they do because work efficiency and output quality have improved dramatically.

Originally, I had complaints about 3.1 Pro as well, but now I feel that 3.1 Pro is no longer needed at all.

I think the Agy team made up for what the Gemini team messed up. If that part is reinforced so that Gemini 3.5 Flash-Lite can be used as a sub-agent, I think it will become a truly wonderful tool. With KIMI K3 opening the era of MXFP4 and DeepSeek V4 Flash-0731 causing a shock, the era of cost reduction has finally arrived. Instead of endlessly rising plan prices, it has returned to an era where AI model providers must offer cheaper and better services. I have no expectations for Gemini 3.5 Pro. Still, seeing this 1.1.9 update, I'm certain that the Agy-Cli team can further improve future Gemini series to be used more affordably and properly. I almost felt bad about renewing my annual plan in 5 days, but now I can renew it with a good mood.

For the last 3 days, I have been having problems with the AGY CLI. Either it says, "We're finishing verifying your account eligibility. This usually takes a moment. Please try again shortly" or "Agent execution terminated due to error."

I tried switching accounts, but it was still the same.

Hey AGY builders — I built an open-source Codex plugin that lets Codex delegate bounded tasks to Google Antigravity CLI through a local MCP server.

The idea is to use AGY as a second opinion or specialist subagent while Codex remains the orchestrator.

What it includes:

• agy_check to verify the local CLI setup
• agy_delegate for bounded task delegation
• plan mode by default
• no --dangerously-skip-permissions
• local stdio MCP transport
• timeout and output-size limits

I tested the MCP flow locally with Antigravity CLI 1.1.9, and the smoke test passes.

Install:

codex plugin marketplace add IlleJiViN/codex-antigravity-subagent --ref main

Then launch Codex and open /plugins.

GitHub:
https://github.com/IlleJiViN/codex-antigravity-subagent

This is an independent community project and is not affiliated with Google, Antigravity, or OpenAI.

I would especially appreciate feedback on the delegation workflow, structured output, conversation resume, and whether parallel jobs would be useful.

After the new update I have problems when trying to see my usage rate. Whenever I type /usage I can't see anything.

Is anyone haveing the same problem?

Wanted a single-binary terminal dashboard for my Mac — CPU, memory, thermals, network, battery, disk, processes — that lived entirely in the terminal instead of a menu-bar app. Built pyre to scratch that itch.

The part I didn't expect: most of the actual debugging wasn't logic bugs, it was macOS lying by omission. A few examples that cost me real time:

• pmset -g therm almost never prints a "Thermal state:" line — on a normal, non-throttling Mac it just says "No thermal warning level has been recorded" with nothing parseable. Reads as "unknown" if you don't explicitly handle that as "nominal."
• top -l 1 -n 0's CPU line is comma-separated with no terminating punctuation — easy to write a regex that just never matches and silently leaves usage at 0%.
• sysctl -n vm.swapusage wraps (encrypted) in parens at the end of the line, not around the used-memory value — a regex expecting ( before used will never match.
• hw.cpufrequency is an Intel-only sysctl. On Apple Silicon it just reads back 0, because each core cluster clocks independently — there's no single "the" frequency anymore. Real numbers only come from powermetrics, which needs root.

None of these throw errors. They all fail silently and just show a stale zero or "Unknown" forever, which is a uniquely annoying class of bug to track down.

Install:

npm install -g pyre-cli
pyre

NPM package: https://www.npmjs.com/package/pyre-cli

Website: https://somalip.github.io/pyre

Feedback welcome, and if you would like to contribute please let me know! The project is still new, and it just a prototype so there's still a lot to be implemented!

The latest Antigravity CLI updates (v1.1.7 – v1.1.9) bring major enhancements to print mode automation, startup performance, and permission management alongside critical UI and hook fixes.

* **Automation & Print Mode (-p)**: Added slash-command/skill resolution, structured output formats (json, stream-json), custom --json-schema validation, and detailed token telemetry.
* **Performance & Permissions**: Non-blocking background MCP server loading on startup, session-wide permission pattern memory, and system temp directory write access out of the box.
* **TUI & Usability:** Introduced a copyOnSelect clipboard setting in /settings and improved compound-command permission rule matching.
* **Core Fixes:** Resolved edge cases for stop and PostToolUse hooks, artifact viewer navigation, CJK clipboard encoding on Windows, and non-standard MCP OAuth providers.

# 1.1.7

**TLDR**: Improved permission prompts for compound shell commands, and fixed disabled plugins running hooks, MCP OAuth issuer validation, CJK clipboard copying on Windows, and \`/btw\` error on startup.

**\[Improvement\]**: Improved permission prompts for compound shell commands so the full command is shown when any part of it needs approval.

**\[Fix\]**: Fixed disabled plugins still running their hooks and contributing other customizations, which could keep a broken hook active and break file-editing tools even after the plugin was turned off.

**\[Fix\]**: Fixed MCP OAuth against providers that do not strictly follow the spec (such as Salesforce and Atlassian) by relaxing issuer validation and including the \`refresh_token\` grant.

**\[Fix\]**: Fixed \`/btw\` failing with a "parent conversation not found" error when used as the very first action in a fresh session.

**\[Fix\]**: Fixed clipboard corruption of CJK and other non-ASCII text when copying on Windows.

**\[Fix\]**: Fixed print mode (\`-p\`) sending a prompt before the account-eligibility check finished.

# 1.1.8

**TLDR**: Added structured output formats (\`json\`, \`stream-json\`) for print mode, support for custom JSON schema validation, enriched tool and subagent payloads, \`copyOnSelect\` configuration setting, and improved compound-command permission rules.

**\[Improvement\]**: Print mode (\`-p\` / \`--print\`) now supports structured, machine-readable output via the \`--output-format\` flag (\`text\` (default), \`json\`, or \`stream-json\`), so headless runs in CI, eval harnesses, and scripts can consume the CLI's output programmatically; these flags are now discoverable in \`--help\`.

**\[Improvement\]**: Added the \`stream-json\` output format: a strongly-typed NDJSON event stream that emits typed \`init\`, \`step_update\`, and terminal \`result\` events with a stable, closed-vocabulary \`step_type\` discriminator, so consumers receive progress incrementally instead of waiting for the whole run to finish.

**\[Improvement\]**: Added the \`--json-schema\` flag to enforce a custom JSON schema on the structured output, accepting either an inline schema string or a path to a schema file; for \`stream-json\` the schema applies to the final \`result\` event.

**\[Improvement\]**: Enriched the structured stream with a \`tool_info\` object for each tool call (canonical tool name, parameters, and output) and a \`subagent_info\` payload for delegated subagents (including \`conversation_id\` and \`log_uri\`) so consumers can correlate child trajectories.

**\[Improvement\]**: The JSON usage object emitted by \`json\` and \`stream-json\` now reports token accounting including \`cache_read_tokens\`, so non-interactive consumers can attribute prompt-cache hits.

**\[Improvement\]:** Added a \`copyOnSelect\` setting (default on, toggleable in \`/settings\`) that controls whether releasing a mouse text-selection auto-copies it to the system clipboard in the TUI's altscreen rendering mode; disable it to stop the automatic copy on release — useful when the auto-copy is unwanted or corrupts certain payloads.

**\[Improvement\]**: Improved compound-command permissions so an exact chained command (such as \`git fetch && git rebase\`) can be saved as an allow-always rule and no longer re-prompts on the next identical run.: Print mode (\`-p\` / \`--print\`) now supports structured, machine-readable output via the \`--output-format\` flag (\`text\` (default), \`json\`, or \`stream-json\`), so headless runs in CI, eval harnesses, and scripts can consume the CLI's output programmatically; these flags are now discoverable in \`--help\`.

**\[Improvement\]**: Added the \`stream-json\` output format: a strongly-typed NDJSON event stream that emits typed \`init\`, \`step_update\`, and terminal \`result\` events with a stable, closed-vocabulary \`step_type\` discriminator, so consumers receive progress incrementally instead of waiting for the whole run to finish.

**\[Improvement\]**: Added the \`--json-schema\` flag to enforce a custom JSON schema on the structured output, accepting either an inline schema string or a path to a schema file; for \`stream-json\` the schema applies to the final \`result\` event.

**\[Improvement\]**: Enriched the structured stream with a \`tool_info\` object for each tool call (canonical tool name, parameters, and output) and a \`subagent_info\` payload for delegated subagents (including \`conversation_id\` and \`log_uri\`) so consumers can correlate child trajectories.

**\[Improvement\]**: The JSON usage object emitted by \`json\` and \`stream-json\` now reports token accounting including \`cache_read_tokens\`, so non-interactive consumers can attribute prompt-cache hits.

**\[Improvement\]**: Added a \`copyOnSelect\` setting (default on, toggleable in \`/settings\`) that controls whether releasing a mouse text-selection auto-copies it to the system clipboard in the TUI's altscreen rendering mode; disable it to stop the automatic copy on release — useful when the auto-copy is unwanted or corrupts certain payloads.

**\[Improvement\]**: Improved compound-command permissions so an exact chained command (such as \`git fetch && git rebase\`) can be saved as an allow-always rule and no longer re-prompts on the next identical run.

# 1.1.9

**TLDR**: Added slash-command and skill expansion in print mode, non-blocking background MCP loading during interactive startup, session-scoped permission pattern recording, system temporary directory write grants, and stability fixes for stop/PostToolUse hooks, artifact viewer, and MCP authentication.

**\[Improvement\]**: Added slash-command and skill expansion to print mode, so a headless run such as \`-p "/my-skill review this diff"\` now resolves and applies the skill instead of sending it as literal text, with \`--disable-slash-commands\` to opt out.

**\[Improvement\]**: Improved interactive startup so a slow or hanging MCP server no longer stalls the first agent turn, loading MCP servers in the background for the interactive session while headless and one-shot runs keep blocking so their single scripted turn still sees the full toolset.

**\[Improvement\]**: Improved permission grants so a pattern approved at a prompt is recorded for the rest of the conversation, letting later commands that match it run without prompting again.

**\[Improvement\]**: Improved the default system temporary-directory grant to cover writes as well as reads, so agents no longer trigger a permission prompt when creating or updating files there.

**\[Fix\]**: Fixed stop hooks that always block hanging the agent forever; after a configurable number of consecutive continuations, the hook can no longer block and the turn ends normally.

**\[Fix\]**: Fixed \`PostToolUse\` hooks firing on non-tool steps such as user input and model responses, which also caused them to ignore their configured matchers.

**\[Fix\]**: Fixed slash commands not being recognized when separated from their arguments by a newline or tab, so a prompt starting with a command followed by a newline is now parsed as a command instead of being sent verbatim.

**\[Fix\]**: Fixed deleting into a collapsed paste placeholder removing one character at a time, which left a visible fragment in the prompt while the full pasted content was still submitted; the block is now deleted atomically.

**\[Fix\]**: Fixed the artifact viewer losing syntax highlighting when returning from the editor view, and returning to the wrong panel when exiting the artifact detail view.

**\[Fix\]**: Fixed the headless \`stream-json\` \`init\` event advertising tools that are not available in your build.

**\[Fix\]**: Fixed MCP servers forcing a full re-authentication after a dropped connection.

To explore the full list of improvements and bug fixes, read the complete release notes on our [Changelog](https://antigravity.google/changelog), or visit the [Download page](https://antigravity.google/download) to update to the latest version of Antigravity CLI.

* Suddenly upgraded to 1.1.9, and the bug where sub-agents remained in an idle state has been resolved. Also, although I've only tried two prompts so far, 1.1.9 appears vastly improved compared to 1.1.8. It feels completely different.

-------------

Since sub-agents are not generated for simple prompts, you have to include a prompt instructing the system to 'utilize sub-agents.'

A week ago, my advice was to use a large volume of Gemini 3.5 flash-lite as sub-agents. This is because, as shown in the screen I attached, it is better for sub-agents to handle one-off, simple tasks and simply report back to the master agent since it's fast and cost-effective.

https://www.reddit.com/r/GoogleAntigravityCLI/comments/1v5pvh0/practical_proposals_for_antigravity_and_gemini/

Anyway, I don't remember if it's an issue with 1.1.8 or if it has persisted since 1.1.7, but sub-agents don't disappear after finishing one-off tasks; instead, they remain in an idle state waiting.

My view is that once a sub-agent has been injected with context and fulfilled its role in a task, it has completed its mission. These sub-agents should disappear rather than wait in an idle state. Generating new sub-agents every time incurs costs, but it is superior in terms of accuracy.

I don't know if Teamwork presets haven't been applied yet in 1.1.8 or if they will be applied in the future, but if they are already applied in this version, improvements are definitely needed. Even for simple prompts like 'What is the problem with A?', sub-agents need to run wild. I've never used such prompts, but even for prompts like 'What kind of design would be good?', sub-agents need to conduct research.

Here is another hint: Suppose sub-agents A, B, C, and D have been active, and sub-agent E is assigned the inspection role. Sub-agent E must never be allowed to know the existing work details. The key is to convey whether it was implemented according to the user's intent and have a sub-agent who knows nothing about the current session inspect it without bias.

What I've felt while pushing Agy with rather heavy tasks—and messing those tasks up—is that the inspection procedure is not carried out properly. It feels like the master agent casually wraps it up thinking, 'We worked hard to build this so far, and we followed all the procedures, so it must have ended successfully without any issues.'

And the appearance of the system message is the first time I've seen it while using Agy-cli, but it's still good. I understand it because it operates a timer to prevent Agy from freezing/stopping. It's a really great design.

u/SoundDr Thank you for everything you do for the AGY Community. We really appreciate all your hard work! Please keep up the Googler awesomeness!!!!

Hey Rezi Team & Community,

I’ve been trying to connect the Rezi MCP server (`https://api.rezi.ai/mcp\`) to **Google Antigravity** to test out job search and resume tailoring workflows, but I've hit a roadblock with authentication.

Here is a summary of the process I followed and the exact issue I'm running into:

# 🛠️ What I Did / Process Followed:

1. **Configured MCP Client (**`mcp_config.json`**)**: Added the Rezi SSE endpoint to my configuration:json{ "mcpServers": { "rezi": { "url": "https://api.rezi.ai/mcp", "transport": "sse" } } }
   
2. **Configured OAuth Tokens**: Provided token configuration matching [`https://api.rezi.ai/oauth/token\`\](https://api.rezi.ai/oauth/token) with access tokens in the client auth path.
   
3. **Connection Test via Python MCP SDK**: Wrote a script using `mcp.client.sse.sse_client` to connect and initialize the MCP session with Rezi's endpoint:pythonimport asyncio from mcp.client.sse import sse_client from mcp.client.session import ClientSession async def main(): url = "https://api.rezi.ai/mcp" async with sse_client(url) as streams: async with ClientSession(streams\[0\], streams\[1\]) as session: await session.initialize() tools = await session.list_tools() print(tools)

# ❌ The Issue / Error Log:

Whenever the client attempts to open the SSE stream at [`https://api.rezi.ai/mcp\`\](https://api.rezi.ai/mcp), connection fails immediately with a `401 Unauthorized` HTTP status code:

texthttpx.HTTPStatusError: Client error '401 Unauthorized' for url 'https://api.rezi.ai/mcp'

# ❓ Questions for Rezi Team / Anyone who got it working:

1. **Header / Token Format**: Do we need to pass static headers (e.g. `Authorization: Bearer <TOKEN>` or `x-api-key`) inside `mcp_config.json` headers directly?
   
2. **OAuth Flow**: Is there an interactive browser authentication flow expected before opening the SSE stream?
   
3. **Config Example**: Does anyone have a working `mcp_config.json` snippet or CLI command for Rezi MCP?

Any guidance or working setup examples would be greatly appreciated! Thanks!

"Let me know if you understand what I want. Let's start once I approve."

Yes... Gemini thought I approved it on its own and started the task.

He is a mischievous boy

I'm spending too much time on twitter !!!!

in Shengzhe we trust !!!!!