Skip to main content
A sandbox runtime is an isolated workspace for project work. Use it when work needs files, shell commands, or long-running execution.

Use this for

WorkNeeds
Repository inspectionFilesystem and shell access.
Code generationRead, write, and test files.
File transformationWorkspace-local reads and writes.
Browser automationRuntime tools and command execution.
Agent toolsIsolated command and file operations.

Lifecycle

StateMeaning
pendingVeryfront accepted the request.
provisioningThe runtime is starting.
runningThe runtime accepts commands and file operations.
errorThe runtime failed or became unavailable.
deletingThe session is closing.
Close sessions when work finishes so runtime capacity returns to the pool.

Work surfaces

SurfaceUse it for
TerminalInteractive debugging and exploratory commands.
Synchronous commandShort commands with buffered output.
Async command jobLong-running commands with durable status and output.
File accessRead, write, and inspect workspace files.

Agent and tool use

Agents use sandboxes when they need a real filesystem, command-line tools, or external runtimes. Create a session when an agent tool first needs one. Pass project context so billing, isolation, and audit trails stay attached to the right project.

Security

  • Keep auth tokens server-side.
  • Scope sessions to the project that owns the work.
  • Reject paths outside the workspace.
  • Close idle sessions.
  • Store only artifacts the project needs after the session ends.

API reference

APIStart here
RESTSandbox sessions and command jobs.
GraphQLSandbox session queries and mutations.
MCPSandbox tools for assistants.
CodeUse veryfront/sandbox in a Veryfront Code app.