“Let me stash this first.”
A hotfix shouldn’t put your feature on hold. Keep each branch checked out in its own worktree.
Pick up where you left off
GIT WORKTREES. LOCAL SERVICES. CONNECTED AGENTS.
Every branch.
Its own space.
Canopod keeps your branches, services, and databases organized.
Work from the app, or let your coding agent handle setup through MCP.
ONE REPO. ROOM FOR EVERYTHING.
main :3000 feature/checkout :3010 hotfix/refund :3020
Worktrees, services, and logs in one window.CANOPOD FOR DESKTOP
Free & open source Runs on your machine Claude Code + Codex via MCP
INTRODUCING CANOPOD MCP
Your agent can help
with the setup, too.
Give Claude Code or Codex a clear picture of your workspace. Let it inspect worktrees, run your configured setup, and manage services, using the repositories and permissions you choose.
Claude Code · Codex · Compatible local MCP clients
Claude Code Codex
Canopod MCPOne view of your local workspace
LOCAL Worktrees Services Setup jobs
Connect locally. Share access deliberately.
WHEN ANOTHER BRANCH NEEDS YOUR ATTENTION
A quick review shouldn’t
derail your afternoon.
You just wanted to review a PR.
Now you’re stashing changes, freeing a port,
and wondering which database you migrated.
“What’s using port 3000?”
Give each worktree its own stable service ports. Keep your branches running alongside each other.
Less port juggling
“That migration broke main.”
Configure a Postgres database per worktree. Try a schema change without sharing the same database.
A space to experiment
PARALLEL, WITHOUT THE CHAOS
Keep each branch
ready to work on.
One repository. Independent workspaces.
Each with the services, ports, and context it needs.
acme-webINTERACTIVE EXAMPLE
YOUR WORKTREE
feature/checkout
Running independently- Frontend
- localhost:3010 Its own port
- Server
- localhost:4010 Its own process
- Postgres
- acme_feature_checkout Its own data
✓Checkout is ready. Main and your hotfix keep running.
Select a branch to see its workspace. Example ports and databases; configure your own setup once.
Find the log.
Keep the context.
Start and stop services, read their logs, and open a shell in the right worktree. All together, instead of scattered across your desktop.
Explore terminals & logs Frontend
:3010 Server :4010 Terminal in your worktree
$ git branch --show-current
feature/checkout Service logs
Frontend
GET /checkout200Server
GET /api/cart200Your agent starts
on the same page.
Give Claude Code, Codex, or your favorite CLI the task, branch, ports, and database in a structured handoff. The agent knows where to start.
See how agent handoffs workYOUR TASK
Build the new checkout.
- branch
- feature/checkout
- frontend
- localhost:3010
- database
- acme_feature_checkout
The context to pick up where you left off.
Data, with a way back. Snapshot and restore local Postgres databases.
One setup to repeat. Commit your provisioning steps with the repo.
There when you need it. A lightweight manager in your menu bar.
BUILT FOR THE WORK BETWEEN COMMITS
Your day rarely stays
on one branch.
PR REVIEWSTry the change.
Handle the urgent bit.
Give each task
Try the change.
Keep your work open.
Run a review branch alongside your current feature, with its own services and ports.
Review without the shuffleHOTFIXESHandle the urgent bit.
Then come right back.
Give the fix a separate worktree and leave your unfinished feature where it is.
Make room for a hotfixCODING AGENTSGive each task
a place to work.
Keep agent sessions with the branch, runtime context, and services they belong to.
Work alongside your agentsFROM REPO TO RUNNING
Set up your repo once.
Reuse it on the next branch.
Bring your repository.
Point Canopod at a local repo. Review detected Node services, or add the commands your stack needs.
Add repositoryMake room for a branch.
Choose a branch or tag. Canopod creates its worktree and runs your configured setup steps.
New worktree ⌘ NStart it. Keep going.
Run your services, open the app, and get to work. Your other branches can keep doing their thing.
Start servicesMAKE ROOM FOR YOUR NEXT IDEA
Keep your flow.
Get Canopod.
Your machine. Your branches. A little less friction.
Free & open source No account needed No telemetry
At home in your menu bar.
v0.5.0For macOS on Apple Silicon (M1 and later).
Download for macOSOR INSTALL WITH HOMEBREW
brew install --cask emidhun/canopod/canopodHomebrew is recommended. Installing the DMG? Canopod isn’t notarized yet. Follow the first-launch steps.
For your Linux desktop.
Experimental64-bit x86 packages. Choose your preferred format.
Linux packages build in CI but haven’t been validated on a desktop. Read the Linux install guide.
Share feedback on GitHubA place in your system tray.
ExperimentalWindows x64 installer.
Download for WindowsWindows builds haven’t been validated on a desktop. The installer isn’t code-signed yet, so SmartScreen may show a warning. Read the Windows install guide.
Share feedback on GitHubDo I need to know Git worktrees?
Just the idea: a worktree is another checkout of your repository, on a different branch. Canopod handles creating and managing them, so you can keep several branches open at once. See how it works.
Does it work with my stack?
Canopod detects services and commands from package.json for Node projects. You can configure commands for other stacks, including Rails, Django, Go, and Rust. Database snapshot and restore tools are Postgres-specific. Explore stack examples.
Can I use it with coding agents?
Yes. Launch your configured coding-agent CLI in a worktree with a structured task handoff. Canopod MCP also lets agents inspect worktrees, run configured setup, and start or stop services. You choose the repositories and permissions. Explore Canopod MCP.
Is it free? Where does my code go?
Canopod is free and open source under AGPL-3.0. Your repositories and services run locally, and Canopod sends no telemetry. Release checks and update downloads contact GitHub. Any coding agent you connect follows its own data settings. Read the security notes.
What do I need installed?
Git, plus the runtimes and package managers your project uses. Local Postgres is only needed for Postgres workflows. The primary tested build is macOS on Apple Silicon; Linux and Windows packages are experimental. View the requirements.