coterm home

People keep asking whether we'll add git worktrees to coterm. We're not going to, because we don't want to impose worktrees on everyone. coterm is a primitive, not a solution.

Everyone works differently. Some projects live across several git repos. Some people keep many checkouts of the same repo (my cofounder has clones named coterm0 through coterm40, for reasons I still don't understand). Some people default to SSH and remote development.

coterm is just terminals and browsers, with a CLI to drive them. You can write a few bash scripts to manage worktrees, juggle multiple checkouts, or open remote sessions, and lay out your workspace however fits your head.

coterm should bend to your workflow instead of forcing one on you. We want coterm to feel like home.

A small Rust TUI that starts Claude and Codex workspaces and watches their live status is one example of what that looks like. The launcher uses command templates, so you can swap in your own scripts for creating worktrees, picking a checkout, or SSHing into a VM. Build on the same Coterm primitives and make it yours.