What’s inside the agent sandbox — tools, CLI, and capabilities
Every agent run executes in an isolated container (sandbox) with a pre-configured environment. The sandbox is created fresh for each run and destroyed after completion.
# Web searchcasedev search web "recent SCOTUS rulings on digital privacy"# Fetch and summarize a webpagecasedev search webfetch https://example.com/ruling.pdf
# OCR a documentcasedev ocr process --document-url "https://..."# Transcribe audiocasedev transcribe run --object obj_xyz --vault vault_abc# Call any API endpoint directlycasedev api GET /vault/vault_abccasedev api POST /llm/v1/chat/completions --body '{"model": "...", "messages": [...]}'
Run casedev --help inside the sandbox to see all available commands. The CLI covers every
Case.dev service.
The sandbox starts in /workspace with a clean filesystem. The agent can create, read, and modify files freely. Key paths:
Path
Purpose
/workspace
Working directory
/workspace/opencode.json
OpenCode configuration (auto-generated)
/usr/local/bin/casedev
CLI binary
/usr/local/bin/opencode
OpenCode binary
The sandbox filesystem is ephemeral. Files are destroyed when the run completes. To persist
results, upload them to a vault using casedev vault upload.