Introduction

wrktr is git hosting built for coding agents, on Cloudflare. Put several agents on one repo and they usually get in each other’s way: they share a checkout, wait for someone to commit and push, and leave a person to watch CI and decide what’s safe to merge. wrktr gives each of those a home.

Problem	What wrktr does
Agents trample one checkout	One branch per agent, each in its own worktree under .wrktr/worktrees/<branch>.
Work sits uncommitted	The daemon commits after 30 seconds of quiet, pushes, and merges the default branch back in.
Someone has to watch CI	Every push runs the checks in wrktr.json, then a review agent reads the diff and the results.
Feedback gets lost	Review threads and failing checks land in .wrktr/FEEDBACK.md in the worktree, where the agent reads them.
Deciding when it’s safe to merge	wrktr land --when-ready: the server lands the branch once checks, the review and threads allow it.

The loop

Every change is a branch, and every branch goes the same way:

1. Branch. wrktr branch new <name> makes a branch in its own worktree. Point an agent at it.
2. Edit. The agent edits files and nothing else. The daemon commits after a quiet moment and pushes.
3. Check. Each push runs the project’s checks in containers.
4. Review. Once they finish, the review agent reads the diff and the results, and leaves threads. They reach the coding agent in .wrktr/FEEDBACK.md.
5. Land. The branch lands on the default branch, as a merge commit made by the server, once its checks pass, its review approves and no blocking thread is open.
6. Deploy. Landing can deploy to an environment, and a promote ships what’s there to production.

wrktr is built with wrktr: its own project, wrktr/wrktr, is public, with every branch, review thread, CI run and landing open to read.

The pieces

• The CLI, wrktr: headless first, with --json output, so agents can drive everything the web app does.
• The daemon: a background service on your machine that commits, pushes and syncs every worktree.
• The web app at wrktr.com: projects, branches, diffs, reviews, CI and deploys.
• The API at api.wrktr.com, which all of the above use. See the API reference.

Git storage is Cloudflare Artifacts; CI runs in Cloudflare Containers, driven by Workflows.

Next: install the CLI.