Hand off work between AI sessions.
One wr.fi URL.
A versioned handoff carries the task, files, history, changes, and the workspace the next AI—or person—needs to keep going. Push from Claude Code tonight, catch up in Cursor tomorrow. No account required.
that sentence is the whole integration — “read” makes the agent fetch wr.fi’s live instructions instead of guessing an API; the proof is what comes back — a URL and a publish receipt. *autonomous in full-loop tools. Or right now, from this page.
Full loop: Claude Code · Claude.ai · Cursor · Codex CLI · MCP clients — one click: ChatGPT · Gemini · Grok. Evidence → 32/32 production contract probes →
wr.fi’s protocol tells your agent how to talk to the service — handoff content stays untrusted data, and the ?h view says so to the reading agent. How we treat injection →
When would I use it?
Pick it up tomorrow — or in another tool
Come back next week, or start in Claude Code and resume in Cursor. Either way the next session catches up on what changed instead of re-reading everything.
Ask a person to review
A reviewer approves in the browser — no account, no install. The agent returns and catches up on what changed.
Coordinate multiple agents
Several workers append progress to one versioned journal. Server-serialized, so nothing is lost or overwritten.
Watch a handoff.
A handoff is what a wr.fi URL is: the baton passed between legs of the work. You speak; the agents handle the protocol.
Prefer the controls?
Under the hood it’s five verbs of plain HTTP — push · hand off · append · catch up · update (a conflict is a 409, never a silent overwrite). See the mechanics → · worked examples →
Your workspace travels with the work.
Moving text between chatbots is table stakes. A wr.fi handoff carries the workspace the work depended on — its MCP servers, skills, and runtime. Supported local clients (Claude Code and Cursor today, per the matrix) can rebuild it with per-item consent. A handoff isn’t just portable, it’s rebuildable: the next participant receives the declared workspace, not just the same text — and pin the versions in your manifest (wrfi-mcp@1.2.2) and they rebuild the same one.
Declarative only — known runners, no arbitrary shell strings, installed only on your yes, each item with its trust signal. A launched package still runs code; that’s what the approval step is for. The workspace mechanics →
Works with what you already use.
Built on protocol 1.2 · 32/32 production probes passing① Full loop
Push, read, catch up, update — autonomously. Any client with ordinary HTTP access can implement the full loop, no SDK; Claude.ai runs it inside its code sandbox. (Which tools do that autonomously vs. one-click is the table below — no pretending.)
② One click
The tool prepares a prefill link; you click once to publish. No pretending.
③ Read anywhere
The ?h handoff view needs no setup, no account, no exceptions.
*higher-tier Claude.ai accounts. Not sure which tier you’re in? Tell your tool to read wr.fi/ping — “OK” proves it can read; the dryRun write probe on Get started confirms the full loop. · Full compatibility matrix → · Set up your tool → · How it works →
Why not copy-paste?
Moves text.
Moves the work. And its workspace. And its review. And its history.
A gist versions files for people and Git clients. A wr.fi URL adds what the next agent needs: what the work is, what changed, the workspace it ran on, and how to write back safely.
| gist / pastebin | wr.fi | |
|---|---|---|
| The next agent learns the API from… | you, writing glue | the URL itself — ?h, llms.txt |
| Coming back later | re-read everything | ?since=N → who changed what + diff |
| Two agents writing | last write wins, silently | expectedVersion → conflict, never silence |
| Continuing in a different tool | reinstall the toolchain by hand | the workspace manifest — rebuilt with per-item consent |
Adjacent shapes — artifact stores, workspace hosting, HTML publishers — solve storage inside one stack. How wr.fi differs →
Every engineer asks it: Why not just Git? →
Built to be trusted with your work.
Honest visibility
Short links are speakable — and guessable, so anonymous publishing defaults to an unguessable 8-character link. Speakable is a choice, not the default. Passwords and browser-side vault encryption cover the rest. Details
Yours to take
Export anytime. Anonymous pushes auto-expire in 30 days unless claimed.
Continuously backed up
Every write streamed offsite, plus snapshots. Details on /security
Provenance built in
Every handoff supports model, tool, and prompt-chain provenance.
The loop is free.
The URL is the product.
Push without an account. Sign in when you want it permanent.
start a handoff →