Run three lines of work in parallel

What you do

1. Create the refactor workspace. Start from main, accept or edit the prchd/… branch, and choose the agent with the right model and effort.
2. Create the bug-fix workspace. It gets a separate worktree, branch, snapshotted base, processes, and setup run.
3. Create the dependency workspace. Use terminal-first when the work is a command sequence rather than an agent brief.
4. Leave the app. Each running session stays on the Mac. PRCHD keeps the machine awake while work or tracked processes are in flight.
5. Return to Activity. Needs you, Running, and Recent combine work across projects and paired Macs. Host chips keep identical project names unambiguous.
6. Review each branch on its own. Read its files and diffs, run its checks, and open its dev server without crossing into another workspace.
7. Land or remove each result. Merge & Close the two that pass. Confirm Discard & Close for the branch you do not want.

What it relies on

The isolation is ordinary git. Every workspace is a worktree and branch made from a recorded base commit. The refactor and bug fix never share a working directory, so an agent changing src/auth.ts in one workspace cannot modify the other copy.

One workspace can also hold several chats and terminals in its own tab strip. Use that when two agents should work against the same branch; use separate workspaces when the lines of work should meet only at merge time.

What Activity changes

Parallel work fails when attention becomes the scarce resource. Activity separates setup failures, unresolved merges, and missing agent sign-ins from work that is still running. Recent holds content-light milestones such as command outcomes, commits, pushes, and workspace closes. You can open the exact workspace from any row.

Optional push notifications can tell you that a turn or automation changed state. They use quiet hours and generic content, and require the Mac to be connected to the notification service. The payload is a route back to the Mac’s authoritative state, not a transcript.

What it does not do

PRCHD does not set a concurrency promise. Your Mac, repository setup cost, and agent provider limits determine how much can run well at once. It also does not solve close-time merge conflicts on the phone. If two good branches conflict when they land, the failed close preserves the later worktree for your normal desktop tools.

There is no offline queue for starting the fourth task when the Mac cannot be reached. Work already running continues and replays after reconnect.

Keep each branch legible.

Start several lines of work, then give each one the same deliberate review.