Real isolation, not worktrees
Every instance is its own Docker container — no shared worktrees, no port collisions, no accidentally killing your dev server, and nothing left behind to clean up when you're done.
Point Codebay at a local folder or a Git repo URL and it spins up a fully isolated devcontainer with its own browser-based VS Code — built for running parallel agent workflows without them stepping on each other.
Not another wrapper around an agent SDK — the real thing, properly sandboxed.
Every instance is its own Docker container — no shared worktrees, no port collisions, no accidentally killing your dev server, and nothing left behind to clean up when you're done.
Run it against Docker Desktop or Colima on your laptop, or run it on a remote server and drive every instance from the browser.
No abstractions in the way — it's the actual Claude Code CLI running in each container, so you get the latest features the day they ship.
Existing Claude Code and GitHub credentials are copied into every container automatically — no re-logging in, no tokens to paste.
Agents have become great at working autonomously, but sometimes you want to jump in and help them out. Codebay provides this through a full VS Code experience in addition to Claude Code.
Every agent visible from one dashboard, with live status and notifications built in.
Handled automatically, out of the box.
Copy a folder or clone a repo — .git history comes along either way.
Every instance runs its own code-server, proxied behind your password.
tmux, git identity, and Claude Code aliases, injected automatically.
Agents ping you when done or waiting — a pulsing tab plus an optional chime.
Instance list and health, streamed live over WebSockets.
Declared ports are published automatically — add more anytime.
Ship Codebay itself as a container — Docker-outside-of-Docker.
bunx codebay@latest and you're live at localhost:6969.
Pick a theme — the dashboard and every code-server tab follow along.
From source to a running browser IDE in four steps.
A local folder, or paste a Git repo URL.
code-server, port forwards, and your credentials go into
devcontainer.json.
devcontainer upThe official CLI builds and starts your container.
A unique host port, proxied and password protected.
A cute sprite to keep you company. Use one of the existing ones or draw your own.
One command and you're live.
Requirements