Skip to main content
Glama

Continue Antigravity conversation

antigravity_continue

Resume a prior Antigravity conversation for a workspace by using its recorded conversation ID, allowing follow-ups that stay on the same thread even if other conversations were started in between.

Instructions

Continue the Antigravity conversation rooted at this workspace.

Resumes the exact conversation id recorded for workspace (via agy's --conversation flag), not agy's global "most recent", so it stays correct even if agy was used elsewhere in between. On agy 1.1.8+ that id is the one agy itself reported for this bridge's last run in the workspace, so a follow-up resumes THIS thread even if you have since started a separate conversation in the same folder from Antigravity's own interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional model slug for this turn (agy's --model), e.g. "claude-sonnet-4-6". agy's model is per-invocation, not baked into the conversation, so a follow-up can run on a different model than the original ask — omit to use agy's settings.json default. Validated against `agy models`; an unknown slug is rejected (agy would silently ignore it).
watchNoIf true, open a live "watch" view in your browser that streams agy's steps as it works (same return value, best-effort). Default false.
promptYesFollow-up message.
timeout_sNoMax seconds to wait for agy to complete. Default 180.
workspaceNoWorking directory used by the prior conversation. Defaults to cwd.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint=false and idempotentHint=false, but the description adds valuable behavioral context: it resumes the exact conversation ID, stays correct even if agy used elsewhere, and uses the correct ID on newer versions. This goes beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, concise and front-loaded with the core purpose. It is informative without being overly verbose, though it could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the sibling tools and the existence of an output schema, the description adequately covers the tool's behavior and context. It explains the conversation ID tracking and workspace association, which is key for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with each parameter already described in the input schema. The description does not add extra information about parameters beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it continues an Antigravity conversation rooted at a workspace, with specific behavior about conversation IDs. It distinguishes itself from siblings like antigravity_ask (which starts new conversations) and antigravity_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use this tool (to continue a specific conversation) and implies it's for follow-ups, but does not explicitly state when not to use it or alternatives. The sibling context provides implicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SinanTufekci/agent-intern'

If you have feedback or need assistance with the MCP directory API, please join our Discord server