Skip to content

Add Sandboxes documentation page - #24

Open
mmilutinovic371 wants to merge 3 commits into
mainfrom
docs/sandboxes
Open

Add Sandboxes documentation page#24
mmilutinovic371 wants to merge 3 commits into
mainfrom
docs/sandboxes

Conversation

@mmilutinovic371

Copy link
Copy Markdown

Summary

New docs page for the DeepSands sandbox service (isolated microVMs for running untrusted code), added ahead of general release per mentor feedback that pre-release docs matter — especially the non-obvious details (lifespan, /workspace-only persistence, isolation boundaries).

  • New page: sandboxes/overview.mdx, added to nav between GPU Instances and Hosted Agents
  • Content verified directly against the backend implementation (deep-sands service) and the deepinfra-python SDK source, not just the marketing blog post — plans/pricing table, lifecycle states, three independent timeout clocks (idle / 24h hard age / 7-day stopped retention), filesystem persistence model, isolation/networking, quotas, typed errors, Python SDK usage, and raw HTTP API examples
  • Note: docs use /workspace (not /work) for all paths — the backend only accepts /workspace; the SDK's own README/examples currently use /work, which is a separate bug worth fixing in that repo

Test plan

  • Validated docs.json is well-formed JSON
  • Ran npx mint broken-links — no broken links
  • Visual check with mint dev (not run in this environment)

mmilutinovic371 and others added 3 commits August 14, 2026 12:37
Documents the DeepSands sandbox service ahead of release: plans/pricing,
lifecycle and timeouts, filesystem persistence (only /workspace survives
stop/start), isolation/networking, quotas, errors, Python SDK, and HTTP API.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Exact specs and hourly rates can change; link to the dashboard and
catalog endpoint/SDK method instead of a table that will go stale.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The backend branch merged main since the page was first written, and
fixed the fs-path-outside-/workspace bug from a 500 to a proper 400 --
update the docs to match instead of describing a bug that's gone.
Also: drop the unreachable 403 row from the errors table, add the 400
row that's now common (bad path, empty command, timeout out of range),
note the read-side 100 MiB cap symmetric to writes, and mention the
fail_reason field GET/list now returns for a failed sandbox.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant