wtm

Highlights

• A worktree per branch, ready to code: .env files copied and your hooks run, from any base.
• Its own stack: shifted ports, its own Compose project and database, a named URL.
• Stacked branches stay in order: a whole chain rebased onto its parents in one command.
• Gone once merged: never with uncommitted, unpushed or open work.
• Configured once, run by everyone: one person writes run.toml, the team imports it.
• Built for agents: a skill, --output json, --yes, a live event stream.

Install

brew install LucasPcq/tap/wtm
echo 'eval "$(wtm shell-init)"' >> ~/.zshrc

macOS, Linux and WSL2. Other ways to install, and a specific version: Installation. Then wtm init once in your repository, or follow Getting started.

The life of a branch

Created, ready to code

A worktree from any base, its .env files copied and your on_create hooks run.

wtm create feat/login

Running, each with its own stack

Its own ports, Compose project, database and URL. An agent starts the whole app in its worktree and checks its own work while yours keeps running. One person writes the run.toml that describes the stack, the team imports it.

wtm run up

Kept in order

Every worktree knows the branch it came from. When main moves, the whole chain is rebased, parents first.

wtm sync --all

Gone once merged

Every worktree whose pull request merged, removed with its jobs and its data. Uncommitted, unpushed or open work is refused until --force.

wtm prune

Built for agents

Every change takes --yes, every data command --output json, and wtm events streams what every shell and agent does. One command teaches your agent the rest:

wtm agents install

Integrations · The event stream · herdr-wtm

Learn more

Getting started · Guide · Commands · Compared to · Changelog · Contributing

MIT licensed.