// Use for reusable Daytona sandbox workflows, SSH access, git setup, and isolated command execution.
| name | sandbox-workflow |
| description | Use for reusable Daytona sandbox workflows, SSH access, git setup, and isolated command execution. |
Prefer the top-level disposable run command for evals and smoke tests:
ralph-town run --json -- pnpx my-pi@latest --help
ralph-town run --repo https://github.com/owner/repo -- pnpm test
Use the manual workflow only when you need a kept sandbox.
# 1. Verify snapshot tools
ralph-town sandbox preflight
# 2. Create sandbox
ralph-town sandbox create --snapshot ralph-town-dev --json
# 3. Get SSH access
ralph-town sandbox ssh <sandbox-id> --show-secrets
# 4. Connect and work
ssh <token>@ssh.app.daytona.io
cd /home/daytona
# 5. Cleanup
ralph-town sandbox delete <sandbox-id>
If a kept sandbox needs GitHub push access, pass a sandbox-scoped token:
ralph-town sandbox create \
--snapshot ralph-town-dev \
--env "SANDBOX_GH_TOKEN=$SANDBOX_GH_TOKEN"
Inside the sandbox, Ralph-Town exposes that token as GH_TOKEN.
Do not paste raw token values into prompts, logs, git remotes, or command output.
SSH sessions can have a limited PATH. Use full paths when a command is not found:
| Tool | Full Path |
|---|---|
| git | /usr/bin/git |
| gh | /usr/bin/gh |
| pnpm | /usr/local/bin/pnpm |
| curl | /usr/bin/curl |
Use when working with Daytona SDK - uploadFile(Buffer, path), pnpm setup, CodeLanguage options
Daytona sandbox security. Use for token handling, credential boundaries, and full paths in SSH.
Prepare reusable Daytona sandbox sessions for isolated evals, debugging, or manual command execution.
Manage Daytona sandboxes for isolated evals, smoke tests, and command execution.
Generate sandbox-scoped task prompts for any LLM or tool runner working inside Daytona sandboxes.
Troubleshoot Daytona sandbox runs, SSH access, snapshots, credentials, and command execution failures.