Overview

WTmag is for people who already use coding agents but want them to run in real worktrees instead of the main checkout, and want to watch them in tmux instead of hoping for the best.

The basic loop

You run an orchestrator agent (or just use WTmag directly). You tell it what to do. It runs wtmag create. WTmag makes a worktree, opens tmux, writes the brief, and starts the agent. The worker runs in the background. You can attach to it at any point.

you → orchestrator → wtmag create → worktree + tmux + agent
                                         ↑
                                      attach here

The setup

WTmag expects a WorkTrunk-managed repo. Bare clone, then check out the default branch:

git clone --bare <repo-url> project/.git
cd project
wt switch ^

^ is WorkTrunk shorthand for the default branch.

Then start tmux from that worktree:

tmux new -s project-dev

Run your orchestrator inside that session. It calls wtmag create for each task. Workers open as windows in the same tmux session by default.

Defaults

First run creates ~/.config/wtmag/config.toml. Defaults:

• Agent: pi
• Workers open as tmux windows (not separate sessions)
• Both implementation and review work default to window placement

So you need to be inside tmux when you run wtmag create with the default config.

What workers do

Issue workers implement the task, commit, push, open a PR, and report the link back.

PR review workers read the diff and report findings. They don't edit, push, approve, or merge anything.