BranchBox
Parallel feature workspaces for humans and AI agents.
The Problem
Modern development means parallel work — multiple features, AI agents exploring code, experiments running alongside production work. But nothing was built for this:
- Git branches collide when you switch contexts
- Docker ports conflict across features
- Databases leak data between environments
- AI agents break your main workspace
- Devcontainers drift out of sync
You've felt this. The "which branch am I on?" moment. The port 3000 conflict. The agent that modified the wrong files.
The Solution
One command creates a feature worktree and runs its configured setup:
branchbox feature start "Add OAuth"
That's it. You now have:
- ✅ Dedicated git worktree and branch
- ✅ Compose project identity when configured
- ✅ Database naming configuration when detected
- ✅ Synced devcontainer configuration when enabled
- ✅ Copied environment file when present
- ✅ Optional Cloudflare tunnel for sharing
Work in ../add-oauth/. Your main workspace stays pristine.
See It Work
# One-time setup
branchbox init
# Start an isolated feature
branchbox feature start "OAuth Integration"
# See what's running
branchbox feature list
# Clean teardown when done
branchbox feature teardown oauth-integration
Who It's For
- Engineers juggling multiple features — work on 3 things at once without collisions
- Teams using AI coding agents — give Claude/Copilot a safe sandbox
- Anyone tired of "it works on my machine" — real isolation, not hope
Quick Links
- BranchBox for Mac — Add projects, manage features, review teardown plans, and inspect operations
- Quick Start — Initialize a project and start a feature
- Installation — All install methods
- Use Cases — Common workflows
- CLI Reference — Every command documented
Built in Rust. Open source. MIT licensed.