Skip to main content

​
Using it

No, and you are not meant to. Your agent captures as the work happens. If you find yourself maintaining Contextaco by hand, something has gone wrong — the whole point is that you do not keep a second system.
There is one interface: MCP. No SDK, no library, nothing to install. That is deliberate — the consumer of this is an agent, and agents already speak MCP.
It makes no model calls of its own. It stores and serves; your agent does the reasoning.
Markdown, under handles, referencing each other by handle. There is nothing to export because there is nothing proprietary to export from — what you read is what is stored.

​
Privacy and sharing

Yes, by default. Publishing is an explicit act, never a side effect.
Anyone, with no account needed — including forking it. That is the point of publishing; treat it as irreversible in practice, because a fork someone else made stays theirs.
A fork copies what the person forking can already read. Publishing decides what is readable.
Notes can be deleted, but content that already has checkpointed history keeps that history — that is what makes the record trustworthy. Files are different: deleting one is permanent and immediate, which is what makes storage reclaimable.

​
Behaviour that surprises people

Because someone changed that content after your agent read it. You get the current content and a diff back, so the change can be redone on top rather than silently overwriting. See Troubleshooting.
Because forbidden would confirm it exists. Not found is the honest answer to someone who is not entitled to know either way.
It is the first half of every address you have published, and it is chosen once. An agent that could set it could permanently settle something only you should settle. Display name and bio are changeable and an agent can update them.
Forking exists because an intention diverged. Merging would collapse two lines of work that diverged for a reason, and quietly pick a winner. Reading across a family and reporting where they disagree is a different operation, and a better one.
Reading a taco returns its shape — metadata, the overview, and a map of notes — not every body. An agent’s context window is the scarce resource, so bodies are fetched only when needed.

​
Limits and cost

There is one free plan. See pricing.
Writes stop; reads never do. Nothing you published becomes unreadable, and nobody loses access to work you shared.
Unlimited, public or private, along with unlimited agents and tokens. Storage is the only ceiling.