Google Antigravity CLI can operate a signed-in Tabbit Browser when the local agent can read a Tabbit skill and run the Tabbit CLI on the same reachable machine. If you are moving from Gemini CLI, first migrate its skill and configuration using Google's CLI guide, then test discovery, browser reachability, and the website login separately. We use a release-notes review as the example so the agent reads a page and leaves a named draft for you to check.
A Gemini CLI user described the migration problem plainly: “not everything was automatically moved” in a Reddit migration thread. That is one user’s experience, but it is a useful reason to inventory the paths and integrations you rely on before switching. Google announced Antigravity CLI as the next path for Gemini CLI users and says the new CLI keeps key capabilities such as Agent Skills while changing some configuration and extension behavior. The migration is not a copy-everything operation. Google's migration guide and CLI skill guide are the source of truth for current paths and commands.
Key takeaways
Keep Gemini CLI installed until you have checked the migration output and rerun the workflows you rely on.
Put a skill in an Antigravity CLI skill directory. A skill in the IDE or app path may not be visible to the CLI.
Treat skill discovery, local shell permission, connection to the intended Tabbit browser, and the site's logged-in state as four separate checks.
Use Tabbit CLI for a bounded browser action. Keep the result in a named draft and review its source links before sharing or publishing.
If Antigravity runs remotely without access to the local Tabbit process, hand off a task brief instead of claiming that it can reach your browser.
The migration decision at a glance
| Question | Gemini CLI workflow | Antigravity CLI workflow |
|---|---|---|
| Skill path | Existing Gemini CLI skill path | CLI-specific Antigravity path from Google's current docs |
| Extensions | Gemini CLI extensions | Antigravity plugins; migration may need conversion |
| Invocation | Gemini CLI slash commands and shell flow | Check the installed agy version and its /skills command list |
| Browser access | Depends on installed tools and host | Still depends on a local browser connector; the CLI's own /browser feature is a separate Chrome subagent |
| Migration evidence | Existing workflow and config | Skill appears in /skills, a read-only test succeeds, and the expected page is signed in |
Google's May migration notice said feature parity would not be one-to-one at launch. Its current docs evolve, so confirm the live CLI docs and installed agy --version; do not reuse an old Gemini flag just because a related command exists. Antigravity's /browser command runs its own browser subagent in Chrome. That is useful for public pages and local app checks, but it does not prove the agent can use a particular Tabbit profile or its existing website sessions.
Migrate the skill without mixing client paths
A skill is a directory with a SKILL.md and optional resources. The same format can be shared across compatible clients, but discovery paths and invocation behavior belong to each client. Google's CLI documentation distinguishes Antigravity CLI paths from the App and IDE paths. Follow the CLI section, then run /skills in agy to see what the running client has loaded.
Install or update the Tabbit skill using the Tabbit CLI setup guide. For this client, do not assume /tabbit is a native Antigravity command. Ask the agent to read the installed tabbit/SKILL.md, or give it the documented launcher workflow. The skill is the recipe; the Tabbit CLI is the executable connector.
The local check in this environment found agy version 1.4.9. That confirms the binary is installed here, not that every user's Antigravity account or plan includes the same model, plugin, or browser capability. Keep your previous Gemini setup until your own agy run passes the checks below.
| Check | How to verify | What a pass means |
|---|---|---|
| Skill discovery | Run /skills; confirm the Tabbit skill name and description appear | Antigravity CLI sees the instructions |
| Command access | Ask the agent to locate the installed launcher and read diagnose instructions | The host can invoke the expected local tool |
| Browser route | Run a read-only task against a public page in the intended Tabbit instance | The launcher can reach that browser |
| Site login | Open the target workspace in the task tab and confirm its signed-in page | This selected profile has the required login |
If one check fails, stop at that boundary. A visible skill does not guarantee permission to run shell commands. A successful launcher does not mean it connected to the intended browser. A reachable browser may still be signed out of the site.
Run a release-notes review and leave a draft
For this tutorial, use a non-sensitive release-notes page that your Tabbit profile can already open. Ask the agent to collect only the visible version, date, and changed feature names, with a URL for each item. Have it save the result as Release notes review — draft 01 in a local Markdown file or your normal draft workspace. Do not ask it to publish or update the source page.
Try this bounded prompt after you have installed the skill and confirmed the target page is signed in:
Use the Tabbit skill and Tabbit CLI from this local Antigravity CLI session.
Open the release-notes page in a separate task tab. Read the visible entries for the current version only.
Create a draft named "Release notes review — draft 01" with: version, date, feature, source URL, and one item that needs human confirmation.
Do not edit the source page or publish the draft. Stop and show me the draft and source links for review.
If the Tabbit launcher or login check fails, report which check failed and do not guess.The separate task tab lets you continue using your ordinary browser window. The agent's task is still tied to the selected Tabbit environment. Keep the draft visible in its destination and review the cited page before approving it. A matching test on a localhost fixture can verify the mechanics, but it does not validate a real team's documentation account.
What Tabbit adds to this workflow
Tabbit Browser gives a local agent a route to work with an existing browser session through Tabbit CLI. The setup keeps the browser profile, website login, and agent process on the machine connected to the Tabbit runtime. The user can keep working while the agent uses a separate task tab. See the CLI setup for a concrete host example and the browser integration overview for the difference between a CLI route and an MCP server.
This is a useful route when a release page or internal documentation requires a login already held in Tabbit. It is not a claim that Google Antigravity natively bundles Tabbit, that every Antigravity skill is automatically available, or that a cloud agent can tunnel to a desktop. Compare browser-agent approaches and the browser for agents guide if your execution host is remote.
Pick the right next step
If your task is code work or public web research, Antigravity's own CLI and browser tools may be enough. If a local agent needs the website session already open in Tabbit, add the Tabbit skill and CLI and verify the profile. If the agent runs in a remote environment, prepare a task checklist and hand it to a connected local agent or a person. The agent-to-browser connection guide covers that boundary; the first-task checklist is useful for a safer test.
Keep the migration reviewable. Record the old config, the new skill location, the installed agy version, the browser check, and the named draft. Then ask a person to compare every draft item with its source page. For permission and data boundaries, read agentic browser security, and use the browser automation guide when the task needs a different connector.
Tabbit CLI complete guide, connect an agent to an existing browser, first browser-agent task checklist, browser MCP vs CLI, Codex setup, browser tools for agents, browser agents, browser automation, agentic browser security, and install Tabbit Browser.
FAQ
Is Antigravity CLI the same as Gemini CLI?
Google presents Antigravity CLI as the successor path for Gemini CLI users, but the tools are not identical. Check the migration guide for changed paths, settings, plugins, and commands before moving a workflow.
Where does Antigravity CLI look for skills?
The CLI has its own workspace and global skill locations. Use the CLI-specific section of Google's skill docs because the IDE and app use different paths.
Can an Antigravity skill operate Tabbit Browser by itself?
A skill only supplies instructions. The local agent also needs permission to run the Tabbit CLI on a machine that can reach the intended Tabbit browser instance.
Does Tabbit CLI reuse my website login?
It can use the browser profile selected for that Tabbit environment. Confirm the target page is already signed in, and verify the result in a separate task tab before relying on it.
Can Antigravity CLI run in a cloud workspace and reach my desktop browser?
Not automatically. The CLI process needs a supported route to the local Tabbit runtime. A remote runner without that route should produce a task brief for a local agent or a person to execute.
What should I test after migrating a skill?
Check that Antigravity discovers the skill, then run a read-only browser task and inspect the page title and URL. Discovery, launcher reachability, and website authentication are separate checks.