spawn/e2b
A 0835b35a36
fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534)
~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
2026-02-11 14:37:43 -08:00
..
lib fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
aider.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
amazonq.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
claude.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
cline.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
codex.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
continue.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
gemini.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
goose.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
gptme.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
interpreter.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
kilocode.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
nanoclaw.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
openclaw.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
opencode.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
plandex.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
README.md fix: Improve CLI error handling, fix bash compat, and update cloud READMEs (#90) 2026-02-09 09:33:57 -08:00

E2B

E2B sandboxed cloud containers via CLI/SDK. E2B

No SSH — uses E2B CLI for exec. Sandboxes start in ~150ms. Requires npm install -g @e2b/cli.

Agents

Claude Code

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/claude.sh)

OpenClaw

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/openclaw.sh)

NanoClaw

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/nanoclaw.sh)

Aider

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/aider.sh)

Goose

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/goose.sh)

Codex CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/codex.sh)

Open Interpreter

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/interpreter.sh)

Gemini CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/gemini.sh)

Amazon Q CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/amazonq.sh)

Cline

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/cline.sh)

gptme

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/gptme.sh)

OpenCode

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/opencode.sh)

Plandex

bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/plandex.sh)

Non-Interactive Mode

E2B_SANDBOX_NAME=dev-mk1 \
E2B_API_KEY=your-key \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/e2b/claude.sh)