fabro/docs
Bryan Helmkamp 2460ffc37a
feat(install): add sandbox provider step to web install wizard
Operators choose Docker (default, zero-config) or Daytona (validated
via Daytona SDK) during browser install. Selection is captured in
settings.toml under [run.sandbox] -- explicitly even for Docker, so the
choice is locked in. Daytona keys land in the vault as DAYTONA_API_KEY
(Environment secret). Step always runs after object_store and before
the LLM step.

Server adds POST /install/sandbox/test (validates Daytona key via
client.list) and PUT /install/sandbox; both reuse the install-token
auth and InstallSecret redaction patterns established by object-store.
A resolve_install_sandbox_state helper preserves a saved Daytona key
when the operator revisits the step without re-entering it. The
in-memory api_key is dropped from PendingInstall after finish, matching
the manual_credentials cleanup for S3 access keys.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 14:59:17 -07:00
..
brainstorms docs: capture cargo dev cleanup requirements 2026-04-25 19:14:16 -04:00
ideation docs 2026-04-09 17:24:30 -04:00
internal refactor(docs): split docs/ into public/ and internal/ 2026-04-27 07:21:13 -07:00
plans refactor(sandbox): make Docker clone-based by default 2026-04-26 18:21:02 -04:00
public feat(install): add sandbox provider step to web install wizard 2026-04-27 14:59:17 -07:00
superpowers/specs chore: move testing-strategy doc into docs-internal 2026-04-25 12:38:41 -04:00