Why not just Git?
Fair question — every developer asks it. The honest answer: Git is the system of record for source code, and nothing here competes with that. wr.fi moves work in flight — the half-finished thing one AI session produced and the next tool, agent, or reviewer needs to continue. Most real handoffs use both: a wr.fi handoff often contains a repo link, plus the task, the workspace, and the review state Git was never built to carry.
| Git | wr.fi | |
|---|---|---|
| Unit of work | A repository of files | A handoff: files + task + workspace + review state |
| Who writes | Developers who've cloned and configured | Anyone with the URL — humans and AI agents, zero setup |
| Getting started | init, remote, auth, clone | One POST. The URL is the whole integration |
| Continuing work | clone → read the code → reconstruct intent yourself | ?h hands the next agent intent, history, and how-to-write-back |
| Concurrent writers | Branches + merge — powerful, manual | expectedVersion → conflict is a 409, never a silent overwrite; append never conflicts |
| The toolchain | README prose, dotfiles, hope | A declared workspace manifest, rebuilt with per-item consent |
| Review | Pull requests (unmatched for code) | One version-bound decision: approve / request changes — thumb-sized, no repo needed |
| History | Commit graph — richer than ours | Linear versions with diffs and catch-up (?since=N) |
| Where it shines | The system of record for source code | The transport for work in flight between tools, sessions, and people |
Where Git is simply better: branching and merging code, blame, bisect, the commit graph, code review at scale. If the work is a codebase and everyone touching it is a developer with a clone, use Git — that’s what it’s for.
Where Git quietly fails AI work: the recipient is often not a developer with a clone — it’s a sandboxed agent that can fetch a URL, or a reviewer on a phone. The work is often not a repo — it’s a document, an analysis, an app, a decision in progress. And the context Git strips (what’s been tried, what’s open, what tools the work ran on) is exactly what the next AI session needs first. That gap — clone vs. continue — is the product.
Same honesty policy as everywhere else: see the compatibility matrix for what’s verified, /conformance for the probe evidence, and /patterns for worked handoff recipes (several of which push repo links).