Skip to content

docs(sandbox): include Sprites in provider enumerations #877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlemTuzlak merged 1 commit into from
Jul 1, 2026
+4 −4
Merged

docs(sandbox): include Sprites in provider enumerations #877

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sandbox/harnesses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,6 @@ and protocol coverage). For which agents you can plug in, browse the official

## Where to go next

- **[Providers](./providers)** — where the harness runs (local, Docker, Daytona, Vercel).
- **[Providers](./providers)** — where the harness runs (local, Docker, Daytona, Vercel, Sprites).
- **[Tools](./tools)** — bridge your app's own tools into the in-sandbox agent.
- **[Events & File Hooks](./events)** — stream the agent's edits and activity to a UI.
2 changes: 1 addition & 1 deletion docs/sandbox/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ Start with the [Quick Start](./quick-start) to get an agent fixing a bug in a
sandbox on your laptop. Then dive into the piece you need:

- **[Quick Start](./quick-start)** — from a `chat()` app to an agent fixing a bug, in minutes.
- **[Providers](./providers)** — local process, Docker, Daytona, Vercel: isolation, auth, and capabilities.
- **[Providers](./providers)** — local process, Docker, Daytona, Vercel, Sprites: isolation, auth, and capabilities.
- **[Harnesses](./harnesses)** — which agent runs: Grok Build, Claude Code, Codex, OpenCode, or any ACP agent via `acpCompatible`.
- **[Workspace](./workspace)** — the source repo, clone depth, and serial/parallel setup.
- **[Provisioning](./provisioning)** — secrets, skills, MCP servers, plugins, and `AGENTS.md`.
Expand Down
2 changes: 1 addition & 1 deletion docs/sandbox/quick-start.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ export const repoSandbox = defineSandbox({

Because local-process inherits your host environment, you can drop the
`XAI_API_KEY` secret and let Grok Build fall back to your grok.com login. For that
(and for Daytona, Vercel, and Cloudflare runtimes), see [Providers](./providers).
(and for Daytona, Vercel, Sprites, and Cloudflare runtimes), see [Providers](./providers).

## Run the working example

Expand Down
2 changes: 1 addition & 1 deletion docs/sandbox/tools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ same path the edge/Cloudflare deployment uses; see [Cloudflare](./cloudflare).

### A remote cloud sandbox, driven from your laptop

With a cloud provider (Daytona, Vercel) in **local dev**, the sandbox is a remote
With a cloud provider (Daytona, Vercel, Sprites) in **local dev**, the sandbox is a remote
VM. It **cannot dial your machine's `localhost`**, and your laptop has no public
URL, so bridged tools can't reach the host until you expose the bridge.

Expand Down