Same document,
everywhere.
One live document,
in every app and every agent.
You’re taped in! We’ll email you when it’s your turn.
Early access is free. No spam, pinky promise.
Animation: one document taped up in four places with masking tape: an editor, an AI agent’s terminal, a phone and a team doc. As a person and an agent type, all four change at the same moment, because it’s the same document. Rolf, a roll of tape with a face, sits in the corner.
poke me
How it feels
- 01
Tape it
CLAUDE.md, a spec, a contract, your notes.
- 02
It’s everywhere
Your editor, your agents, your phone, your team.
- 03
Edit anywhere
People and agents, on the same line, live.
RIP, copies.
final_v7_FINAL.docxspec_final_v2_REAL.mdCLAUDE (copy).mdcontract_v7_final_redline.docxnotes from call (1).md
spec.md
One document. Every place you open it.
What would you tape first?
Tap one. It helps us decide who gets in first.
Be the first to tape it.
First up:You’re taped in! We’ll email you when it’s your turn.
Early access is free. No spam, pinky promise.
From the blog
All posts- Study
CLAUDE.md vs AGENTS.md in 596 repos: 1 in 8 keep copies, and 4 in 10 copies differ
We read CLAUDE.md and AGENTS.md in 596 public repos. Most link them; 1 in 8 keep two copies, and 4 in 10 of those copies already differ. - Reference
Which coding agent reads which instruction file (October 2026)
CLAUDE.md, AGENTS.md, .cursor/rules, copilot-instructions.md, GEMINI.md: which file each coding agent reads, and which one wins. Checked October 2026. - Explainer
Why your CLAUDE.md, AGENTS.md and Cursor rules drift apart
Every coding agent reads its own instruction file, in every repo. Why CLAUDE.md, AGENTS.md and Cursor rules drift, and the six workarounds teams use.