Run agent-generated code on Fly.io Sprites · Fly

At some point in any session your agent stops handing you scripts to review and starts executing them itself. It would be pretty useless if it didn't. That's also the point where your laptop stops being a sensible place to keep working.

Use a Sprite instead. We've (probably) already built an integration for your agent, so it's easy. Just follow the steps for your agent and immediately forget what it feels like to fear what your agent is doing when you're not watching.

Works with

Pick your agent and go!

Which agent are you using?

Pick one and follow the steps below.

Set up Sprites for Claude Code

  1. Add the marketplace and install the plugin
    $ /plugin marketplace add superfly/sprites-claude-plugin
  2. Install it
    $ /plugin install sprites@sprites
  3. Reload so Claude picks up the new tools
    $ /reload-plugins
  4. Authorize the connector
    $ /mcp
  5. Check the integration
    $ /sprites:status

Set up Sprites for Codex

  1. Install the Sprites plugin from the Codex plugin marketplace
  2. Authenticate when Codex prompts you
    List my sprites.

Set up Sprites for Cursor

  1. Install the Sprites plugin from the Cursor Marketplace
  2. Configure the MCP server 
    {
    "mcpServers": {
        "sprites": {
            "url": "https://sprites.dev/mcp"
        }
    }
}
  3. Ask the agent to prove it's connected
    List my sprites.

Set up Sprites for Antigravity

  1. Install the plugin
    $ agy plugin install https://github.com/superfly/sprites-antigravity-plugin
  2. Authenticate the sprites server
    $ /mcp
  3. List what you've got
    $ /sprites:list

Set up Sprites for Grok Build

  1. Install the plugin
    $ grok plugin install superfly/sprites-grok-plugin --trust
  2. Enable it
    $ grok plugin enable sprites
  3. Run the status check
    $ /sprites-status

Set up Sprites for Cortex Code

  1. Install from GitHub
    $ cortex plugin install superfly/sprites-cortex-plugin
  2. Enable the plugin
    $ cortex plugin enable sprites
  3. Check the connection
    $ /sprites-status

Underneath, it's a whole computer.

The boundary is the hardware.

A Sprite is a Firecracker microVM. It boots its own kernel, and that separation exists from the moment the Sprite does. The agent can install what it likes, misconfigure anything, and delete whatever. All of it can only happen inside the Sprite.

You decide how it reaches the network.

Give a Sprite an allowlist of domains and it can only talk to those.

The disk is still there tomorrow.

Come back a week later and that repo you cloned is still there. The deps are still installed and that half-finished branch is still checked out.

An undo button for the whole machine.

Checkpoint a state you like, and let the agent attempt a sketchy idea. If it breaks the environment, no big deal: just restore the whole filesystem back to the way it was before.

It sleeps when the agent stops typing.

An idle Sprite freezes, then suspends. The next command or HTTP request wakes it, with its filesystem exactly as it was.

The SDKs, and the API they all sit on.

Which language are you building in?

  1. Python
    Install from PyPI
    $ pip install sprites-py
  2. JavaScript
    Install from npm
    $ npm install @fly/sprites
  3. Go
    Add the module
    $ go get github.com/superfly/sprites-go
  4. Elixir
    Add the dependency 
    {:sprites, "~> 0.2"}
  5. Google ADK
    Install from PyPI
    $ pip install sprites-adk

Frequently asked questions

  1. Where should I run code that an AI agent generates?
    Not on your laptop, and not on the server running your production app. Run it somewhere isolated enough that a bad command only costs you that environment.

  2. Is it safe to run agent-generated code?
    Every Fly.io Sprite is a Firecracker microVM with its own kernel, so the isolation is a hardware boundary.

  3. Can I stop an agent on Fly.io Sprites from reaching the whole internet?
    Yes. Each Fly.io Sprite has a network policy that takes an allowlist of domains.

  4. Do Fly.io Sprites keep state between agent runs?
    Yes, and this is the main reason to use one.

  5. Can an agent roll back a change it got wrong?
    Yes. A Fly.io Sprite can checkpoint its whole filesystem.