Launch with context.
Start a configured CLI such as Claude Code, Codex, or Aider inside a worktree. Canopod writes your task, branch, ports, and database to a handoff file.
Terminal sessions & handoffsTHE CANOPOD WORKSPACE
All the moving parts.
One place to manage them.
Git worktrees are the starting point. Canopod brings the setup, services, terminals, and agent context together so you can actually work in them.
01 / GIT WORKTREES
Leave your work
right where it is.
Check out another branch in its own folder. Canopod finds existing worktrees and helps you create new ones from a branch or tag, so you can run a review, a feature, and a hotfix side by side.
- Discover worktrees you created outside Canopod.
- Create worktrees and initialize submodules.
- Run the setup your repository defines.
02 / SERVICES & PORTS
Know what’s running.
Know where to find it.
Keep the frontend, API, and other configured services with their worktree. Start or stop them, open their local URLs, and read their output in a shared log stream.
- Stable port offsets for each worktree.
- Per-service port overrides when you need them.
- Logs and terminal sessions in the same window.
Another repository or process can still use the same port. Canopod makes your assignments visible and editable.
Explore services and ports
03 / POSTGRES WORKFLOWS
Try the migration.
Keep a way back.
Configure a Postgres database for each worktree, then snapshot or restore it as you work. Branch-specific data is especially useful when two branches expect different schemas.
- Snapshot, export, restore, and switch databases.
- Run your configured migration and reset commands.
- Keep your main branch’s data separate from experiments.
Database tools need local Postgres and compatible client binaries. Other databases can run as services.
See the database workflow
04 / WORKING WITH AGENTS
Two ways to bring
your agent into the workflow.
Connect through MCP.
Let a local MCP client ask Canopod about the workspace and use the operations you enable. Share selected repositories and start with read-only access.
Explore Canopod MCP05 / REPEATABLE SETUP
Put the setup
in the repository.
A committed .worktreemanager.json records the files, commands, and environment overrides each worktree needs. The next branch can use that same recipe.
New worktree
- 01 Seed the configured files
- 02 Apply environment overrides
- 03 Install dependencies
- 04 Run configured setup & migrations
You define the commands. Canopod runs the recipe.
Keep the stack you use.
Canopod detects Node services from package.json. For other stacks, provide the commands your project needs.
Node.jsRailsDjangoGoRust
See configuration examplesYour next branch is waiting.
Download Canopod, add a repository, and give it a workspace of its own.