antigravity-ask

name	antigravity-ask
description	Control the Antigravity IDE chat UI and inspect headless conversations via the Bridge CLI.
allowed-tools	Bash, Read, Grep, Glob

Antigravity Ask (Bridge Skill)

This skill provides a high-level interface to the Antigravity Ask Bridge, allowing external agents and workflows to control the Antigravity IDE, send messages to AI agents inside the IDE, and read their outputs.

Quick Start

Installation

# From the published repository
npx skills add ddarkr/antigravity-ask --skill antigravity-ask -a antigravity -y

# For local development
npx skills add . --skill antigravity-ask -a antigravity -y

The "Golden Path"

Always verify connectivity before attempting to send prompts:

npx antigravity-ask ping
npx antigravity-ask ask "Explain the current project structure."

Core Capabilities

• Connectivity: Check if the bridge is reachable (ping, status).
• Synchronous Interaction: Send a prompt and wait for the final answer (ask).
• Asynchronous Interaction: Initiate a conversation and poll for results later (send).
• Conversation State: Inspect full step-by-step trajectories (conversation).
• Artifact Access: Read output files generated by headless conversations (artifacts, artifact).
• UI Control: Automate IDE actions like starting new chats or approving agent steps (action).

Model Selection

ask and send intentionally use Antigravity's current default/UI-selected model. The legacy --variant flag is accepted for compatibility, but the bridge does not force old hard-coded model IDs.

Prefer omitting --variant unless you are running an older script that already includes it.

Local Port & URL Overrides

If the bridge is running on a non-standard port, use these flags or environment variables:

1. --url <baseUrl> (e.g., http://127.0.0.1:5820)
2. --http-port <port> (e.g., 5822)
3. AG_BRIDGE_URL environment variable

Best Practices for Agents

• Check Ping: Always run ping before long-running tasks to ensure the bridge hasn't timed out or closed.
• Poll stderr: When using ask in scripts, capture stderr to see real-time progress indicators.
• Use Aliases: Stick to canonical commands (ask, send, artifacts) for maximum clarity, though aliases like status and conversations are supported for backward compatibility.
• Artifact Hygiene: After a headless run finishes, check npx antigravity-ask artifacts to see if the agent produced code or reports.

Reference Documents

• Command Reference — Detailed flag and subcommand guide.
• Common Workflows — Step-by-step integration patterns.
• Source Truth: packages/cli/src/cli.ts, packages/cli/src/contracts/bridge.ts.