Your AI Coding Agent Needs More Than a Sandbox

Your AI Coding Agent Needs More Than a Sandbox

Author
Daniel Botha
Daniel Botha
Writer at Fly.io
Published

Give every agent a full Linux computer it can use, pause, resume, and restore.

AI coding agents are getting better at writing code. The infrastructure around them should not be the bottleneck.

Fly.io Sprites gives agents a persistent, disposable Linux environment with the room to install tools, keep a working filesystem, connect securely to external services, and pick up where they left off.

Try Sprites free

$30 in trial credits included for eligible new organizations. Each user can grant one trial credit and each organization can receive at most one. Usage is billed based on actual resource consumption. See pricing and eligibility

The Problem With “Just Use a Sandbox”

A lightweight sandbox is fine for a quick command. But serious agent workflows often need more: dependencies that stay installed, files that survive between runs, a web server that can be reached, credentials managed outside the prompt, and a way to recover from a known-good state.

When an agent has to rebuild its environment every time, useful context disappears. Setup work repeats. Long-running tasks become fragile. And the developer ends up supervising infrastructure instead of reviewing the result.

That is the gap Sprites is designed to fill.

A Sprite is a full Linux computer designed for agents—not merely an isolated process.

A Persistent Workspace That Can Still Be Disposable

Sprites are designed to be as persistent or disposable as your workflow requires. Your agent can work in a real Linux environment, retain its filesystem between runs, and be recreated or discarded when the task is complete.

That makes Sprites useful for coding sessions, background jobs, previews, experiments, and agent-powered applications where a clean environment and continuity both matter.

Agent workflow Why a Sprite helps
Coding and debugging Give the agent a complete Linux environment for tools, packages, tests, and project files.
Long-running tasks Let the workspace sleep and resume without rebuilding the entire filesystem.
Web apps and previews Run services inside a Sprite and expose them through Sprite URLs when needed.
Tool and API integrations Connect securely to external services through Connectors rather than placing everything in the prompt.
Repeatable experiments Use checkpoints to save a known state and restore it when a task needs a clean retry.

The Features That Make Agent Work Feel Less Fragile

Persistence without giving up flexibility

Reads and writes use a fast local cache, while data is stored durably behind it. A Sprite can sleep, move between machines, and return with its filesystem intact. See lifecycle for how sleeping and waking work.

Checkpoints and restore

Capture a working state, test a change, and restore from a checkpoint when you need to retry from a known point. This is especially useful for iterative coding and automated workflows.

Secure connections to external services

Sprites can connect to external services through Connectors, giving teams a more deliberate way to handle integrations and credentials.

A familiar Linux environment

Use the CLI, REST API, or available language integrations to create and control Sprites from the tools your team already uses.

Room for real work

Agents can install dependencies, run commands, execute tests, and operate in a full computer environment instead of a narrowly constrained runtime.

Start in Minutes

The basic workflow is intentionally simple:

curl -fsSL https://sprites.dev/install.sh | sh
sprite org auth
sprite create my-first-sprite
sprite use my-first-sprite
sprite exec -- echo "Hello, Sprites!"
sprite console

Then connect your agent, mount the project it needs, and let it work in an environment that can persist beyond a single invocation.

Create your first Sprite · Read the API reference

Built to Fit the Agent Ecosystem

Sprites supports official plugins, SDKs, and native integrations across a growing ecosystem of coding agents and developer tools. That means you can choose the agent you prefer and give it a more capable place to work.

Explore integrations

Pay for Usage—Not an Oversized Always-On Machine

Sprites pricing is based on actual CPU, memory, and storage usage, billed hourly.

Resource Published rate*
CPU time $0.07 / CPU-hour
Memory time $0.04375 / GB-hour
Hot storage $0.000683 / GB-hour
Cold storage $0.000027 / GB-hour

*Rates and billing terms may change. Confirm current pricing and trial-credit eligibility before starting.

For illustration, Fly.io’s published examples show a four-hour Claude Code session totaling $0.44 and a sample web app totaling $1.89 per month under the assumptions shown on the pricing page. Your costs will vary with resource usage, runtime, storage, and configuration.

A Practical First Test

Choose one workflow that currently feels slow or brittle. For example, ask an agent to clone a repository, install its dependencies, run the test suite, start a preview server, or make a sequence of changes across multiple sessions.

Run that workflow in a Sprite. Notice what changes when the environment can keep its filesystem, sleep between bursts of activity, and return to a checkpoint instead of starting over.

You do not need to redesign your entire stack to try it. Start with one agent, one project, and one repeatable task.

Ready to Give Your Agent a Real Place to Work?

Move beyond throwaway sandboxes. Create a full Linux computer for your agent, connect the services it needs, and keep the environment available for the next run.

Try Sprites free · View documentation

$30 in trial credits. No long-term commitment required to begin. Review the current terms, pricing, and eligibility on Fly.io before use.

Frequently Asked Questions

Is Sprites only for coding agents?

No. Sprites are full Linux computers designed for agents and can support coding workflows, web apps, background tasks, experiments, and other workloads that benefit from a persistent, disposable environment. Choose resources and usage patterns appropriate to your workload.

Does a Sprite stay running all the time?

Sprites can sleep and resume. Billing is based on actual resource usage under the applicable pricing and billing rules, so review the current lifecycle documentation for the details of when a Sprite is billable.

Can I use my preferred agent?

Sprites provides integrations across a growing agent ecosystem, along with CLI, REST API, and language options. Check the current documentation for the latest supported integrations.

How much will it cost?

It depends on CPU, memory, storage, runtime, and configuration. Review the current pricing page rather than relying on the examples above.

Is the trial available to everyone?

Fly.io currently advertises $30 in trial credits, but eligibility and account terms apply: each user can grant one trial credit, and each organization can receive at most one. Confirm the current offer during signup.