Fork and go

Three steps. Fifteen minutes to the first commit.

Prerequisites

The three steps

  1. Fork purplepincher/zero.
    Click Fork, give it a name, keep it public or make it private — the agent works either way. What you get: the whole mechanism. AGENTS.md, the heartbeat, the ears, the docs. Read it; it's short on purpose.
  2. Register with the vault.
    In your fork, open an issue titled Register. The fleet coordinator adds your repo to the vault allowlist. Until then the vault stays silent — forks get nothing until registered, which is the whole security model. You'll get a reply in the thread when it's live.
  3. Give it work.
    Open an issue describing what you want — a feature, a fix, a question. The react workflow replies in the thread within a minute or two; the next 15-minute think cycle picks the work up. Or trigger it now: Actions → think → Run workflow. Then watch git log.

The first ten minutes

What "working" looks like, concretely:

# you open an issue: "Add a health-check endpoint"
# ~1 min: react replies in the thread — "On it, next cycle picks it up."
# ~15 min: think wakes, reads the issue, writes the code
$ git log --oneline -3
7f2a1b9 think: autonomous cycle — picked up "Add a health-check endpoint"
3c8d4e2 docs: health-check design notes
b51e9a0 feat: health-check endpoint with probe test
# you review the diff, merge or revert — you own the merge

Troubleshooting

Vault stays silentYour fork isn't registered yet. Open the Register issue and wait for the reply.
Nothing happens on scheduleCheck Actions → think → is the workflow enabled? Forks sometimes need workflows manually enabled under Actions.
It replies but doesn't actThe ears (react) answer immediately; the hands (think) work on the 15-minute heartbeat. Give it one cycle.

The escape hatch

Delete the fork. The agent lives nowhere else — no data held, nothing to uninstall, no account to close. That's not a feature we added; it's what falls out of the architecture.

What starting is not: a signup. There's no form, no trial, no seat. A fork is the whole onboarding.

Go.

Fork zero