Give an agent a task

This walks one change through the starter: clicking a color copies its hex code. It assumes you’ve forked the starter and are in ./starter.

1. A branch for the agent

wrktr branch new copy-hex

The branch has its own worktree at .wrktr/worktrees/copy-hex, with npm ci already run there. Open a coding agent in that directory and give it the task:

Clicking a color copies its hex code, with a short “Copied” toast. Then land it.

2. The agent edits; wrktr does the rest

The agent edits files and nothing else.

1. The daemon commits after 30 seconds of quiet and pushes.
2. CI runs test and typecheck, then the review agent reads the diff and the results.
3. Review threads and failing checks appear in .wrktr/FEEDBACK.md in the worktree. The agent reads them, fixes the code, and replies with wrktr feedback reply <id> "...".
4. wrktr land --when-ready lands the branch once the checks pass, the review approves and no thread is open.

The agent skill that wrktr setup installs teaches agents this loop, and the starter’s AGENTS.md repeats it.

3. Watch it

From your terminal:

wrktr status --branch copy-hex      # checks, the review, open threads, conflicts
wrktr branch ls                     # every branch here, and where it stands
wrktr diff copy-hex                 # what it changes

Or in the browser, on your fork’s page at wrktr.com: the branch’s description, diff, threads, checks and a chat with the change.

4. Two agents at once

Start a second branch and a second agent at the same time:

wrktr branch new lock-colors

Each has its own worktree, so they never share a checkout. If both change the same files, wrktr flags the overlap on each branch before they conflict; whichever lands second gets the first merged in by the daemon.

5. After it lands

The branch lands as a merge commit on main, and wrktr land --rm (or wrktr branch rm copy-hex) removes the worktree. Once your fork’s environments are set up, the landing deploys to dev:

wrktr env ls          # what's live where
wrktr status --branch copy-hex   # where the landing is deployed

Next: deploy your fork.