Vibe code with Claude in parallel git worktrees
# Add to your Claude Code skills
git clone https://github.com/sahithvibudhi/vibe-treeVibe code with AI in parallel git worktrees
[!IMPORTANT] 🚧 Active Development Notice: We're currently working on adding cloud support and multi-platform capabilities. For a stable desktop-only version, please use the
release-v0.1branch.
VibeTree is a cross-platform application that enhances your development workflow by enabling parallel development with AI assistance across multiple git worktrees. Work on features simultaneously without context switching. Access from desktop, browser, or mobile devices.


# Development Mode
pnpm install
pnpm dev:all # Run both web and server
# Docker Deployment (Production)
npm run deploy # One-command deployment
# Or run services separately:
pnpm dev:server # Socket server on random 3XXX port
pnpm dev:web # Web app on :3000
pnpm dev:desktop # Desktop app
Download the latest release for your platform from the Releases page:
.dmg file (supports both Intel and Apple Silicon)No comments yet. Be the first to share your thoughts!
.exe.AppImage or .deb fileBuild custom versions (macOS): ./build-custom-mac-version.sh [VARIATION_NAME] to create a custom build with the variation name included in both the app file name and displayed app name (e.g., ./build-custom-mac-version.sh Nov2 creates VibeTreeNov2.app which displays as "VibeTreeNov2" when opened)
bin/launch-with-project /path/to/project [--name "CustomName"] - Launch app with auto-opened project. Optional --name sets window title for easy identification.
pnpm dev:allDeploy VibeTree on any VM or cloud instance with one command:
npm run deploy
This automatically builds and runs VibeTree in a Docker container. Perfect for deployment on EC2, Digital Ocean, or any Docker-enabled environment. See DOCKER.md for detailed instructions.
Access VibeTree:
Deploy on AWS EC2, Digital Ocean, or any cloud VM:
# On your cloud instance
git clone <your-repo>
cd vibe-tree
npm run deploy
Configure security groups to allow ports 3000 and 3002, then access via http://your-vm-ip:3000.
Safari/iOS Requirements:
When opening from a phone on your Wi‑Fi, the web UI loads over LAN and the web app automatically discovers and connects to the socket server via WebSocket. In development, enable LAN WebSocket access without pairing:
# Allow LAN connections to the WebSocket server in dev (no auth)
ALLOW_INSECURE_NETWORK=1 HOST=0.0.0.0 pnpm dev:server
pnpm dev:web
Then open the printed Network URL (e.g., http://192.168.1.x:3000) on your phone. If you still see "Not connected", you can explicitly point the web app at the socket server by creating apps/web/.env:
VITE_WS_URL=ws://192.168.1.x:XXXX # Replace XXXX with actual server port
Create .env files as needed:
# apps/web/.env (optional)
VITE_WS_URL=ws://192.168.1.100:XXXX # For custom socket server (replace XXXX with actual port)
VITE_PROJECT_PATH=/path/to/project # Override project path
# apps/server/.env (optional)
PORT=3002 # Socket server port (optional, uses random port by default)
HOST=0.0.0.0 # Bind to all interfaces
PROJECT_PATH=/path/to/project # Default project path
# In dev, allow unauthenticated LAN WebSocket connections (use only on trusted networks)
# Any of these enables it:
# ALLOW_INSECURE_NETWORK=1
# ALLOW_INSECURE_LAN=1
# ALLOW_NETWORK_DEV=1
DEFAULT_PROJECTS=/path1,/path2 # Auto-load projects (first becomes default)
# Authentication (for webapp login)
USERNAME=your_username # Set username for authentication
PASSWORD=your_password # Set password for authentication
AUTH_REQUIRED=true # Enable authentication
# Docker-specific variables
PROJECT_PATH=/workspace # Project directory inside container
WEB_PORT=3000 # Web frontend port
NODE_ENV=production # Runtime environment
Contributions are welcome! Please read our Contributing Guidelines for details on our code of conduct and the process for submitting pull requests.
MIT License - see the LICENSE file for details.