Git worktrees

When you have several agents working a repository at once, you don’t want them stepping on each other’s files. Git worktrees give each line of work its own checkout on its own branch — and Termio surfaces them natively.

How Termio sees worktrees

Termio derives worktrees directly from git (git worktree list), so any worktree you create — from the command line or elsewhere — shows up in the sidebar automatically. Each one appears as a nested folder under its project, labeled with its branch, forming a three-level tree: project → worktree → sessions.

The list stays in sync: Termio reconciles it when a project loads, when the app regains focus, and when the git directory changes.

Working in a worktree

Open a session inside a worktree and it starts in that worktree’s directory on that worktree’s branch. Point one agent at your main checkout and another at a feat/… worktree, and their edits never collide — each has its own working tree, its own index, its own branch.

An empty worktree still appears in the tree. Open its context menu and choose New Terminal or New Agent Session to start there.

Reviewing the work

The inspector’s git pane is read-only by design: three tabs — Changes, Compare, and History — let you read the diff, see what the branch would merge, and browse commits per worktree. Committing, pushing, and opening pull requests happen in the terminal, where you (or the agent) already are — see the inspector guide.