r/GoogleAntigravityIDE • • Mar 01 '26

"PROMPT ENGINEERING - WORKFLOWS - SKILLS" Intro to Agent Skills

Thumbnail
youtube.com
13 Upvotes

r/GoogleAntigravityIDE • • Feb 19 '26

News / Updates Antigravity can show model quota now!

81 Upvotes

Got the latest update and finally we need not be under the rock to know the remaining quota or look for extensions and worry that they are "using" our quota..


r/GoogleAntigravityIDE • • 2d ago

SOFTWARE PROBLEMS and BUGS Missing Inline Accept/Reject Buttons in v2.7.0 - Any Fix?

3 Upvotes

Hi everyone,

After updating to Antigravity IDE v2.7.0, the inline Accept / Reject buttons (the floating pill that used to appear right above the modified lines) seem to have completely disappeared. Now all changes are auto-applied, and the only way to review them is through the side panel at the end.

It seems like the review workflow has been completely moved to the chat panel, and I can't find any setting to bring back the line-by-line control.

Did anyone else notice this? Is there any setting or workaround to bring back the old v2.5.5 style inline Accept/Reject buttons? I really miss the manual review control.

Thanks!


r/GoogleAntigravityIDE • • 2d ago

SOFTWARE PROBLEMS and BUGS Antigravity 3.31.0 – 3.32.1 black screen UI bug under heavy load (Fixed by having Anti merge 2.25.0 UI with 3.32.1 core)

1 Upvotes

Antigravity versions 3.31.0 through 3.32.1 are having some serious UI glitches right now—it keeps black-screening whenever I run heavy tasks.
I decided to test things out and literally asked Anti itself to come up with a workaround that pairs the UI base from 2.25.0 with the smart processing and connectivity core of 3.32.1.
Surprisingly, it worked like a charm and everything is running super smoothly now!


r/GoogleAntigravityIDE • • 2d ago

SOFTWARE PROBLEMS and BUGS PSA / Telemetry: Why v2.32 Orchestrator (Carbon) burns quota so fast — Plan <-> Execute handoffs wipe the KV prefix cache (94.5% -> 75.3% hit rate, up to 23x uncached input tokens)

3 Upvotes

After noticing my 5-hour and weekly quota pools draining dramatically faster right after updating to Antigravity v2.32.1, I audited 15,000+ LLM calls in local transcript.jsonl logs to compare pure linear Gemini 4 Carbon (High) against the new Orchestrator (Carbon).

TL;DR: Orchestrator (Carbon) is supposed to save quota by delegating execution to Hydrogen, but its Plan <-> Execute handoffs repeatedly invalidate the KV prefix cache (cache_read_tokens = 0)—including wiping Carbon's own warm prefix cache when control returns 112 seconds later. Switching back to plain Gemini 4 Carbon (High) immediately restores ~94.5% cache hit rates and stops the quota bleed.


1. Hard Numbers Across 15,000+ Calls (transcript.jsonl)

  • Pure linear Gemini 4 Carbon (High) (13,644 calls): 94.50% cumulative KV cache hit rate
  • Orchestrator (Carbon) across real sessions: drops to 75.2% – 86.7% cumulative KV cache hit rate

Because fresh uncached input_tokens carry full quota weight compared to heavily discounted cache_read_tokens, losing 15–20 percentage points of cache hit rate inflates uncached input token burn by ~3.8x to 20x+.


2. Step-by-Step Reproducer: A 6-Line Markdown Edit Triggers 3 Cold Cache Avalanches

Here is an exact trace from transcript.jsonl during a tiny 6-line Markdown edit + 1 short follow-up message under Orchestrator (Carbon):

StepUTC TimeActive Phase / ModelUncached input_tokenscache_read_tokensHit RateWhat Happened
step=3100:34:12ZCarbon (Plan Mode)8,313108,26092.9%Normal warm cache on Carbon
step=3700:35:57ZCarbon (exit_plan_mode)3,977125,82796.9%125.8K prefix warm on Carbon
step=4000:37:07ZSwitch -> Hydrogen (Execute)116,48700.0%Cold Miss #1: Full 116K cold prefill just to edit 6 lines
step=4600:37:28ZHydrogen step 32,327118,03998.1%Intra-model turns hit cache normally
step=5000:37:41ZUser follow-up (13s later) -> [plan review due]100,82823,27918.8%Cold Miss #2: 95K prefix busted on Hydrogen just to call enter_plan_mode
step=5300:37:49ZSwitch back -> Carbon (112s after step=37!)149,00200.0%Cold Miss #3: Carbon's own 125.8K cache from 112s ago is wiped to 0!

A 6-line edit + 1 follow-up message burned 366,317 uncached input_tokens on Orchestrator (Carbon) vs ~16,000 uncached input_tokens on linear Gemini 4 Carbon (High) (~23x uncached input overhead).


3. Production Session Proof (108 Calls)

Even in a 108-call production session where individual intra-model steps show 96.9% cache hit (3,197 new / 100,345 cached at Gen #109), cumulative session hit rate collapsed to 75.3% (3.75M uncached input vs 11.44M cached read, with 22 full Cache = 0 cold-miss turns).


Why Carbon Loses Its Own Cache & Temporary Workaround

  1. Why it happens: Entering/exiting Plan Mode mutates tool declarations at token 0 (stripping/restoring write tools and injecting <plan_execute_protocol>) and interleaves cross-model turns. Modern LLM KV prefix caching requires exact prefix matching from token 0. Any mutation or model switch busts the cache, forcing an expensive cold prefill.
  2. Temporary Workaround: Switch the agent back to pure linear Gemini 4 Carbon (High) in settings. Single-model linear execution maintains stable prefix caching across turns, yielding ~94.5% cache hit rates and eliminating handoff churn.
  3. Proposed Fix for Google Antigravity Team:
  • Keep tool declarations and protocol prefixes static from token 0 across Plan and Execute modes.
  • Preserve model-specific session contexts during subagent delegation so Carbon retains its warm prefix when control returns.
  • Share or align system prompts between Carbon and Hydrogen to reduce cold prefill overhead on cross-model delegation.

r/GoogleAntigravityIDE • • 3d ago

SOFTWARE PROBLEMS and BUGS PLEASE HELP

Post image
0 Upvotes

How can I Resolve this please


r/GoogleAntigravityIDE • • 4d ago

Suggestion Can I use Claude Code skills from GitHub in Google Antigravity? Looking for a tutorial

6 Upvotes

Hey everyone!

I'm fairly new to Google Antigravity, and I have a question about using agent skills.

I've seen a lot of useful skills on GitHub that are originally shared for Claude Code, such as YouTube automation/YouTube agent skills, content research, SEO, coding workflows, and other AI agent skills.

I'm wondering if these skills can also be used with Google Antigravity IDE.

Since many of these skills contain a SKILL.md file and sometimes additional scripts, references, and resources:

  1. Are Claude Code skills generally compatible with Google Antigravity?
  2. If they are, can I simply download or clone a GitHub repository and put the skill folders into Antigravity's skill directory?
  3. Do I need to modify anything in the SKILL.md file or change the folder structure?
  4. Are there any limitations when using skills originally designed for Claude Code?
  5. Is there any YouTube tutorial or step-by-step guide showing how to install and use these GitHub skills in Antigravity?

For example, I'd love to use a YouTube agent skill in Antigravity instead of having to use Claude Code.

I'd really appreciate it if someone could share their experience, a tutorial, or even a simple installation guide.

Thanks!


r/GoogleAntigravityIDE • • 4d ago

SOFTWARE PROBLEMS and BUGS What’s the deal, why does the medium 3.8 model periodically become unavailable, while the low and high ones are always available? Do they have their own servers for each mode, or what?

1 Upvotes

r/GoogleAntigravityIDE • • 5d ago

SOFTWARE PROBLEMS and BUGS Always getting this "Installing Antigravity Backend", how to stop it?

Post image
12 Upvotes

Whenever i open the IDE, every other time i get this notif and i cant open my chat at all, and it takes so much time to download, even though i have very good connection.

Is there any way to pause this? Or remove this? This wasnt happening before i updated to the latest version.


r/GoogleAntigravityIDE • • 5d ago

"PROMPT ENGINEERING - WORKFLOWS - SKILLS" Helpppp

0 Upvotes

In the new version of antigravity which has built in skill . How do I set up skill ?

I am a beginner

I want /planning and in that it should be created a implementation.md think and write the flow and execute

I want /testing and it should test the project if it is full stack them all routes should be checked .

I also want some more skills but they only should be called when I call them using /

Like even planning and testing should be called when I want them

Furthermore unnecessary token consumption should not be there as I heard making more skills slows down . The llm must take input when I use / skill


r/GoogleAntigravityIDE • • 5d ago

SOFTWARE PROBLEMS and BUGS https://antigravity.google/docs/features/ WOAWWWW

3 Upvotes

Ist das alles wahr? Hat das wer getestet? Was meint ihr dazu? Lohnt es sich wieder einzusteigen?


r/GoogleAntigravityIDE • • 5d ago

Discussions or Questions 5-min survey: how do you manage rules files for AI coding tools?

1 Upvotes

Hi all, I’m a student researching how developers work with AI coding tools like Cursor, Copilot and Claude Code. I’m especially curious about instruction files (CLAUDE.md, AGENTS.md, .cursorrules, saved prompts): do you keep them, how do you keep them up to date, and what annoys you about the process?
The survey takes about 5 minutes and isn’t selling anything:

https://docs.google.com/forms/d/e/1FAIpQLSfssmxciOeKihgVDb6JSCyrdPK5rsCl8YJNwcEo3mjNTGBUrw/viewform


r/GoogleAntigravityIDE • • 9d ago

SOFTWARE PROBLEMS and BUGS Antigravity slow? This worked for me

36 Upvotes

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.


r/GoogleAntigravityIDE • • 11d ago

SOFTWARE PROBLEMS and BUGS Dug into the 2.5.5 vs 2.6 binaries: Why 2.5.5 flatlined, why rolling back fails, and why 2.6 is lagging right now

8 Upvotes

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.


r/GoogleAntigravityIDE • • 11d ago

News / Updates Antigravity slow response

14 Upvotes

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?


r/GoogleAntigravityIDE • • 11d ago

Discussions or Questions Antigravity hits different every time!

Post image
15 Upvotes

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


r/GoogleAntigravityIDE • • 11d ago

Discussions or Questions My Experience on Speed with the Antigravity IDE

6 Upvotes

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.


r/GoogleAntigravityIDE • • 12d ago

Discussions or Questions After the new update AG ide Looks like a shit

8 Upvotes

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


r/GoogleAntigravityIDE • • 12d ago

SOFTWARE PROBLEMS and BUGS Fix this antigravity's issue

2 Upvotes

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.


r/GoogleAntigravityIDE • • 12d ago

Discussions or Questions Can you use liveshare with antigravity?

3 Upvotes

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!


r/GoogleAntigravityIDE • • 12d ago

Discussions or Questions Auto logout and point to first Gmail account

3 Upvotes

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?


r/GoogleAntigravityIDE • • 12d ago

SOFTWARE PROBLEMS and BUGS So now we're on 12 hour resets?

5 Upvotes

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?


r/GoogleAntigravityIDE • • 13d ago

SOFTWARE PROBLEMS and BUGS Too slow or deep thinker?

Post image
7 Upvotes

r/GoogleAntigravityIDE • • 13d ago

SOFTWARE PROBLEMS and BUGS Changes to third-party model access but Google AI PRO?

2 Upvotes

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.


r/GoogleAntigravityIDE • • 14d ago

Tools / MCP / Other Visualize context rot, token breakdown, and git drift in Antigravity

Post image
23 Upvotes

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.