Works with your agent. Yes, that one too.

1. 1

   Install the Sprites plugin from the Codex plugin marketplace

   Codex distributes this one through its own marketplace UI, so there's no install one-liner to copy.

2. 2

   Or add this repository as a marketplace from a local checkout

   $ codex plugin marketplace add .

   Then restart Codex, open the plugin directory, choose the Sprites marketplace, and install Sprites.

3. 3

   Authenticate when Codex prompts you

   The plugin talks to the hosted MCP server at https://sprites.dev/mcp.

4. ✓

   Ask Codex to prove it's connected

   › List my sprites.

   An empty list is a successful, authenticated response.

1. 1

   Install the Sprites plugin from the Cursor Marketplace

   Cursor prompts you to authorize with Sprites over OAuth on first use.

2. 2

   Or wire up the MCP server by hand

   ~/.cursor/mcp.json

   {
     "mcpServers": {
       "sprites": {
         "url": "https://sprites.dev/mcp"
       }
     }
   }

   Drop this in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one.

3. ✓

   Ask the agent to prove it's connected

   › List my sprites.

1. 1

   Install straight from the repository

   $ agy plugin install https://github.com/superfly/sprites-antigravity-plugin
2. 2

   Authenticate the sprites server

   › /mcp

   Use restricted access unless your workflow genuinely needs broader organization control.

3. ✓

   List what you've got

   › /sprites:list

   The plugin also ships /sprites:new, /sprites:run, /sprites:checkpoint, /sprites:service, and /sprites:cleanup.

1. 1

   Install the plugin

   $ grok plugin install superfly/sprites-grok-plugin --trust
2. 2

   Enable it

   $ grok plugin enable sprites
3. 3

   Reload plugins, or restart Grok

   › /plugins

   Then press r to reload.

4. 4

   Complete browser OAuth

   The consent screen defaults to the restricted mcp- name prefix. Full access allows bare names but grants unrestricted access to every sprite in the org.

5. ✓

   Run the status check

   › /sprites-status

   Empty list means you're authenticated. /sprites-smoke does the full list → create → exec → confirm-before-destroy pass, and grok mcp doctor sprites diagnoses a bad install.

1. 1

   Install from GitHub

   $ cortex plugin install superfly/sprites-cortex-plugin
2. 2

   Enable the plugin

   $ cortex plugin enable sprites
3. 3

   Reload inside your session, or restart Cortex Code

   › /plugin reload
4. 4

   Authorize Sprites when requested

   › /mcp

   Complete browser OAuth and select the intended Fly.io organization. No Sprites CLI or pasted API token is required.

5. ✓

   Check the connection

   › /sprites-status

   An empty Sprite list still means authentication succeeded.

The plugin includes skills, commands, safety hooks, and a runner for long builds and tests. It does not copy Snowflake credentials or sessions into Sprites.

1. 1

   Add the plugin to your profile

   $ npx @deepseek-ai/dsh plugin --profile web add github:superfly/sprites-deepseek-plugin

   Swap web for whichever profile you actually use.

2. 2

   Start that profile

   $ npx @deepseek-ai/dsh --profile web
3. 3

   Complete browser OAuth and pick your Fly.io organization

   Restart Harness once if the first tool sync timed out while you were authorizing.

4. ✓

   Confirm the layer loaded

   $ npx @deepseek-ai/dsh --profile web --dump-config

   Output should include the dsh-sprites-plugin layer, sprites-mcp, and sprites-skill-filesystem.

1. 1

   Add the plugin to your OpenCode config

   opencode.json

   {
     "$schema": "https://opencode.ai/config.json",
     "plugin": ["@flydotio/sprites-opencode-plugin"]
   }

   OpenCode 1.18.23 or newer. Plugins install automatically with Bun at startup, so restart OpenCode after saving. Until the package lands on npm, clone the repository and use an absolute file:///path/to/sprites-opencode-plugin entry instead.

2. 2

   Complete browser OAuth

   › /sprites-status

   The first Sprites request starts OpenCode's browser OAuth flow. Pick the Fly.io org you want. If no browser opens, run opencode mcp auth sprites and retry.

3. ✓

   Ask OpenCode to prove it's connected

   › List my sprites.

   An empty list is a successful, authenticated response. /sprites-smoke walks the full list → create → exec pass, and opencode mcp debug sprites diagnoses a bad connection.

1. 1

   Check the requirements

   OpenClaw 2026.8.1 or newer and a Sprites API token are required. The Sprites CLI is not.

2. 2

   Install the plugin on the OpenClaw Gateway host

   $ openclaw plugins install npm:openclaw-sprites
3. 3

   Store the Sprites token

   $ openclaw secrets store set SPRITES_TOKEN --kind secret

   Paste the token into the hidden prompt so it is not written to openclaw.json or your shell history.

4. 4

   Connect the plugin to the protected secret

   $ openclaw config set plugins.entries.sprites.config.token --ref-provider default --ref-source store --ref-id SPRITES_TOKEN
5. 5

   Sandbox every agent session

   $ openclaw config set agents.defaults.sandbox.mode all
6. 6

   Use Sprites as the sandbox backend

   $ openclaw config set agents.defaults.sandbox.backend sprites
7. 7

   Reuse one Sprite per agent

   $ openclaw config set agents.defaults.sandbox.scope agent
8. 8

   Allow tools to edit the copied workspace

   $ openclaw config set agents.defaults.sandbox.workspaceAccess rw
9. 9

   Enable the plugin

   $ openclaw plugins enable sprites
10. 10

    Validate the configuration

    $ openclaw config validate
11. 11

    Restart the Gateway

    $ openclaw gateway restart
12. 12

    Trigger the first sandbox

    › Run `uname -a` and `python3 --version`, then tell me where those commands ran.

    The Sprite is created on the first command or file-tool call.

13. ✓

    Check the Sprite

    $ openclaw sprites status

    No Sprite appears until an agent first uses a command or file tool. After that, look for an openclaw- name and its awake or asleep state.

The OpenClaw Gateway remains on its existing host. The workspace is copied into the Sprite initially and later edits are not automatically synced back. With this per-agent setup, files and installed packages persist across conversations.

1. 1

   Install from GitHub

   $ pi install git:github.com/superfly/pi-sprites

   Not on npm yet. Node.js 24 or later is required by the Sprites SDK.

2. 2

   Export a Sprites token into Pi's environment

   $ export SPRITES_TOKEN='...'

   This integration authenticates with a token, not browser OAuth.

3. ✓

   Ask Pi to list your environments

   › List my sprites.

1. 1

   Install the Sprites extension

2. 2

   Set your API token

   › Sprites: Set API Token

   Run it from the Command Palette and paste your Sprites.dev API token.

3. 3

   Open a Sprite

   › Sprites: Open Sprite

   Its filesystem appears in your workspace, editable in place.

4. ✓

   Open a shell on the box

   › Sprites: Open Terminal

   Sprites: Create Sprite, Sprites: Delete Sprite, and a right-click Download to Local round out the command set.

1. 1

   Log in with the Sprite CLI

   $ sprite login

   Linux or macOS, Node.js 22 or newer, Git, and Herdr 0.9.0 or newer. The plugin drives the sprite CLI you just authenticated, so there is no token to paste.

2. 2

   Install the plugin from GitHub

   $ herdr plugin install superfly/herdr-sprites-plugin
3. 3

   Find the plugin's config directory

   $ herdr plugin config-dir sprites
4. 4

   Choose an organization and an agent

   config.json

   {
     "org": "your-sprites-organization",
     "agent": "claude"
   }

   Save it in the directory printed above. agent is claude, codex, or opencode. Add a command array to run a different agent or pass arguments; namePrefix defaults to herdr-.

5. 5

   Start an agent from a Git worktree

   $ herdr plugin action invoke start-agent --plugin sprites

   Opens a split pane, creates a Sprite, uploads the worktree with its uncommitted edits, checkpoints it, and hands the terminal to the agent. start-claude, start-codex, and start-opencode pick a harness for one launch. Claude Code and Codex reuse your local login when one is available.

6. 6

   Optionally, bind it to a key

   config.toml

   [[keys.command]]
   key = "prefix+shift+s"
   type = "plugin_action"
   command = "sprites.start-agent"
   description = "start agent in a Sprite"

   Herdr's own config file, so the action runs from a prefix key instead of the CLI.

7. ✓

   Show the pane's Sprite and sessions

   $ herdr plugin action invoke info --plugin sprites

   Info reports the Sprite, its checkpoint, and the remote session list. reconnect reattaches a detached agent, pull brings its edits back into your worktree, and stop, checkpoint, restore, and destroy round out the set.

Git history, .env files, and credentials never leave your machine; the Sprite gets a fresh baseline repository. Pull rejects overlapping local edits before touching anything, and reconnect keeps remote files and authentication in place.

1. 1

   Add a remote server entry

   mcp.json

   {
     "mcpServers": {
       "sprites": {
         "url": "https://sprites.dev/mcp"
       }
     }
   }

   Streamable HTTP over JSON-RPC 2.0, authenticated with OAuth 2.1 (sprites:read / sprites:write). Nothing runs locally.

2. 2

   If your client only speaks stdio, bridge it

   mcp.json

   {
     "mcpServers": {
       "sprites": {
         "command": "npx",
         "args": ["-y", "mcp-remote", "https://sprites.dev/mcp"]
       }
     }
   }

   mcp-remote handles the OAuth flow on the client's behalf.

3. 3

   Authorize in the browser on first use

4. ✓

   Ask your agent to prove it's connected

   › List my sprites.

1. 1

   Install the package with any Agent Plugins v1 client

   The client discovers plugin.json, the children of skills/, and mcp.json at fixed locations. Agent Plugins standardizes package contents, not the install UI, so follow your client's own local, Git, workspace, or marketplace flow.

2. 2

   Complete browser OAuth on first MCP use

   Restricted connector tokens may enforce a sprite-name prefix, creation cap, label, or expiry.

3. ✓

   Ask your agent to prove it's connected

   › List my sprites.

Claude Code, Grok, and Antigravity are not on the current compatible-client list. Use their dedicated packages above, which also carry hooks the portable format has no equivalent for.