Use Sprites from Antigravity CLI (agy) as persistent, isolated Linux development environments for building, testing, previewing, and debugging code. Sprites keep state between sessions, so Antigravity can work in a real project environment without crowding your laptop with packages, services, databases, or long-running processes.
The Sprites Plugin gives Antigravity reusable Sprites workflows, safety guardrails, and convenient commands for common development tasks.
- Create fresh, named Sprites for risky changes, experiments, or preview environments.
- Run commands and tests inside a Sprite instead of your local machine.
- Manage long-running services such as web servers, workers, and daemons.
- Create checkpoints before migrations, package upgrades, and other high-risk work.
- Inspect running Sprites, services, checkpoints, and likely stale environments.
- Clean up old Sprites safely with confirmation before destructive actions.
/sprites:list: See active Sprites, status, services, exposure, and stale candidates./sprites:new <purpose>: Create a fresh Sprite for a task./sprites:run <command>: Run a shell command inside a selected Sprite./sprites:checkpoint <reason>: Create, list, inspect, or restore checkpoints./sprites:service <command>: Start, restart, expose, inspect, or debug services./sprites:cleanup: Find and safely remove idle Sprites and checkpoints.
Install from the repository:
agy plugin install https://github.com/fly-apps/sprites-antigravity-pluginThen open Antigravity's MCP manager with /mcp and authenticate the sprites server. Use restricted access unless your workflow needs broader organization control.
Sprites are stateful environments, so the Sprites Plugin nudges Antigravity to be careful around actions that can affect durable state. It asks for confirmation before destructive operations such as destroying Sprites, restoring checkpoints, deleting checkpoints, or widening service/network exposure. It also prompts for checkpoints before risky commands like migrations, package upgrades, and broad filesystem changes.
One hook is disabled by default:
sprites-remote-test-routing
Enable it for workspaces that want test commands routed into a Sprite instead of running locally.