Continue an Antigravity interaction across turns. Each response carries anDocumentation Index
Fetch the complete documentation index at: https://docs.agno.com/llms.txt
Use this file to discover all available pages before exploring further.
interaction_id; the next turn references it via previous_interaction_id so only the new user message is sent on the wire. The server keeps the sandbox state (files written, packages installed, browser history) attached to the interaction chain. Subsequent turns build on what the agent already did.
Persisting the interaction ID requires a database. The assistant message stores it under provider_data, and the next turn reads it back.
When continuing a chain, the existing sandbox is already attached server-side. Re-sending
environment="remote" is safe; the API treats it as a hint that’s reconciled against the running env. To be explicit, swap to the returned env_<id> after the first turn.Code
cookbook/90_models/google/gemini_interactions/antigravity_multi_turn.py