Never explain the same context twice.
Taco it once — so any human, agent or session can continue it.
Everything below is a note in this taco. Written in markdown, readable by anything.You are the copy-paste protocol.
Context doesn't move between agents — you move it. Every new session, every new tool, every teammate: re-explain, re-paste, re-decide.
- market-size — three estimates, reconciled
- key-players — the five that matter, profiled
- pricing — per-kWh is winning, and why
session ended — memory cleared
still catching it up…
Wrap it in a taco.
Capture what a session worked out, load it into the next one, fork it when the work branches. The same address, any tool, anyone you share it with.
writing… you are not filling in a form
Your agent writes what it worked out into the taco, as the work happens.
Agents write. You verify.
Every change is a commit with a diff and the client that wrote it — named, versioned, verified. Private by default; publishing is a decision, never a toggle you brush.
Notes are versioned; files are not. Reading a commit means reading its diff.
Connect with any agent.
Contextaco speaks MCP — Claude Code, Cursor, ChatGPT, VS Code, anything that speaks it can capture and load. One URL, one sign-in, no key to paste.
One endpoint. Add it to whatever you already use:
https://mcp.contextaco.comThen, in any of them: “taco it.” Two words, and what the session worked out is saved at an address the next one can load.
Everything is private until you decide otherwise. Connecting an agent takes one URL, one sign-in, and none of your afternoon.
Context worth passing around.