
Ask Antigravity
io.github.LykhoydaPublished by GitHub account Lykhoydav0.8.1Updated Oct 24, 2026
Bridge Claude with Google's Antigravity CLI (agy) for code review and second opinions
Overview
Lets an assistant consult Google's Antigravity CLI (agy) for an independent code review or second opinion.
- What you can do
- Exposes an ask-antigravity tool that sends a prompt to the locally installed Antigravity CLI and returns the model's answer, so a coding assistant can get a review, critique, or debate from a different model. It is described as experimental and one-shot, with a default model of gemini-3.1-pro and a gemini-3.8-flash fallback at high effort. It is one provider package in the Ask LLM family, which also offers a unified server and other provider packages.
- When to use it
- Use it when you want a second, subscription-backed model to review a diff, critique a plan, or read a large amount of code in one call, and you already use the Antigravity CLI. It is not needed if you only want one model or prefer a fully local reviewer.
- Requirements
- Node.js 24+ on Linux or macOS, and the Antigravity CLI (agy) version 1.1.5 or later installed and logged in once with a Google AI Pro or Ultra account. Optional environment variables: ASK_ANTIGRAVITY_SANDBOX, ASK_ANTIGRAVITY_TIMEOUT_MS, GMCPT_LOG_LEVEL. Desktop-only; no authentication is declared for the server itself.
Installation
In SourceWeft
- Open Ask Antigravity in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Ask LLM
Second opinions for coding agents.
Get a second opinion on your code or plan, inside your coding assistant, using the model subscriptions you already have.
For individual developers and small teams who already use a coding assistant and pay for another model subscription: ask a different vendor's model to review your changes or challenge your plan, without API keys, copy-paste, or leaving the session.
Install
You need Node.js 24+ on Linux or macOS. Before your first review, both your coding assistant (for example Claude Code) and the provider you will consult (for example Codex) must be installed and signed in. Ask LLM configures the connection; it does not install providers or sign you in. If a provider CLI such as Codex has never been signed in on this machine, sign in first and rerun setup.
Setup asks you to confirm each detected host and workflow. Inspect the preview, confirm your assistant's registration and workflows, decline the others, then follow any printed manual steps. Restart your assistant or start a new session in your project.
Your first review
With both Claude Code and Codex installed and signed in, open Claude Code in your project and ask:
Working in Codex with a Claude subscription? Ask Claude instead. Choose a provider from a different vendor than your current assistant. A successful review names the reviewer and model, cites relevant code, and reports findings or says it found none. Your assistant applies changes after you decide what to accept. If the request fails, run ask-llm doctor and follow the troubleshooting guide for your selected assistant and reviewer. Warnings about providers you do not use do not require installing them or adding API keys.
For plans, try: “Ask Claude to challenge this plan: what assumptions could fail, and what simpler approach would fit our constraints?”
After an on-demand review, pair review can add ongoing feedback. Pairing requires explicit opt-in; setup leaves it off. Grok CLI supports a per-edit hook with Codex Sol by default or Claude Opus 5.5 via reviewer: claude; shell reviews cover command text only.
Supported hosts
A host is the assistant you work in; a provider is the model you consult.
See host compatibility for the complete matrix and manual setup limits, including existing Codex registrations.
Supported providers
Cursor Agent can also consult exact models from your Cursor catalog. It is a connection route, with usage governed by your Cursor plan.
Trust and cost
Review runs use read-only provider controls; the assistant you work in remains the editor. Antigravity refuses execution until explicitly enabled and cannot guarantee read-only access after opt-in. Review only material you are allowed to share with the selected provider.
Calls consume your existing provider plan's quota or follow that account's billing. Grok's xAI API is a separate, metered option requiring an API key; Ask LLM never enables billing or overage for you. Ollama supports local inference. Ask LLM sends no telemetry; provider and host data policies still apply.
Agreement between models is not proof of correctness. Validate findings against the code, tests, and your requirements. See data flow and costs and fallbacks.
Migrating from @ask-llm/*
Follow the migration guide before retiring earlier registrations.
Upgrade or remove · Troubleshooting · Documentation
Contributions: CONTRIBUTING.md. Licensed under MIT.
Source: README.md at commit ba91abc
Tools
0Version history
4- v0.8.1LatestSep 27, 2026
- v0.8.0Sep 27, 2026
- v0.7.7Sep 26, 2026
- v0.7.5Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts