Ez Devbox

🤖 ez-devbox 📦

[](https://www.npmjs.com/package/ez-devbox) [](https://github.com/shanebishop1/ez-devbox/actions/workflows/ci.yml) [](https://github.com/shanebishop1/ez-devbox/blob/main/LICENSE)

`ez-devbox` is a small CLI for running coding agents in disposable E2B sandboxes without rebuilding the same shell glue every time.


The closest alternative is usually a homegrown setup: create an E2B sandbox, clone the repo, copy auth files, run setup commands, start `tmux`, SSH in, launch OpenCode/Codex/Claude Code, remember the sandbox ID, and reattach later. This tool packages that workflow into repeatable commands and config.

What This Is

• A workflow layer on top of E2B sandboxes.
• A way to launch and reconnect to OpenCode, Codex, Claude Code, or a shell in the same sandbox.
• A config-driven bootstrapper for cloning repos, setting branches, installing dependencies, and starting in the right working directory.
• A controlled way to pass selected env vars and sync local tool auth/config into the sandbox.
• Optional tunnel setup for reaching local MCP servers, Docker containers, or other services from the sandbox.

Why Use It

Use `ez-devbox` if your current workflow looks like `git worktree` + `tmux` + SSH + custom E2B scripts + copied config files, and you want that to be less manual.

It handles the repetitive parts:

• create or connect to an E2B sandbox
• clone/bootstrap one or more repos
• launch the selected agent mode
• keep SSH sessions persistent with tmux where needed
• save last-run state so resume can reattach
• sync selected OpenCode, Codex, Claude Code, and GitHub CLI auth/config during create
• optionally expose local serv