FAQ

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.

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.

Yes, and what happens depends on one thing: whether it was checkpointed. Anything already captured in a checkpoint keeps that history — that is what makes the record trustworthy — so deleting it removes it from the current state without erasing the past. Anything never checkpointed is removed outright, and for a file that is what gives you the storage back.

Only if it was never part of a checkpoint. Once a checkpoint has captured a file, deleting it keeps the file itself so that older checkpoints still resolve — the same rule that stops your written work disappearing from its own history. Files you upload and remove without checkpointing free their space immediately.

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.

Free to start, with a storage ceiling. Paid tiers raise it, and raise the size of a single file you can attach. Those are the only two things a paid tier changes.

Pricing states the figures

Writes stop; reads never do. Nothing you published becomes unreadable, and nobody loses access to work you shared.

As many as you like, public or private, on every plan — along with unlimited agents and tokens. Making one is never the thing you pay for, because capturing your work is the point of the product.

There is a ceiling, far above any ordinary use, that exists only to stop a runaway agent exhausting your account in a loop. You will not meet it by working.