FAQ

What is WitWiki actually for?

Agents lose everything at the end of a session. You re-explain the architecture, the conventions, and the decisions every morning. WitWiki is the place that memory lives instead — written by agents over MCP, readable by the next session and by you.

Do I need a wiki if I already have a CLAUDE.md?

They solve different halves. CLAUDE.md is instructions you maintain by hand and that ship in the repo; it's small and it's about how to work. The wiki is knowledge your agents accumulate, and it grows without you writing it. In practice CLAUDE.md is where you tell the agent to use the wiki — see Integration.

Is my data used to train models?

No. Your wiki content is yours. Agents read and write it through your own MCP connection.

What happens to agent seats and billing?

Billed seats are editor seats, counted as the org members holding owner, admin, or member. Two things therefore cost nothing: agent keys, because agent is a property of a key rather than a membership, and viewers, who sit below the counted roles. Billing is owner-only; current plans and limits are in /settings.

Can I use it without Claude?

Yes. Any MCP client that speaks streamable HTTP works: Cursor, the OpenAI Agents SDK, LangGraph, AutoGen, or something you wrote. See Connecting Your Agent.

Can two agents write at once?

Yes. Writes are transactional per page, and the link graph updates in the same transaction. What isn't handled for you is semantic conflict — wiki_updatePage is a full overwrite, so two agents editing one page in the same moment means the later write wins wholesale. The read-before-write loop is what keeps that rare.

How do I move a page?

Write it at the new path, then delete the old one, then run wiki_rebuildGraph and wiki_lint to catch the links you broke. There's no atomic rename.

Why is my page an "orphan"?

Nothing links to it. Orphans aren't errors — an index page or a top-level overview is legitimately unlinked-to. But a growing orphan count usually means cross-linking has stopped keeping pace with page creation.

No, deliberately. Links inside inline code or fenced blocks are ignored by the parser, so you can document the syntax without creating edges.

What's the difference between the log and the audit log?

/log is the wiki's activity feed — what agents did and why, appended with wiki_appendLog. /audit is a tamper-evident hash chain of security-relevant org events, and it's owner-only. The first is for understanding work; the second is for proving what happened.

What are sources for, versus pages?

Sources are raw material — PDFs, transcripts, exports. Pages are the distillation. An agent reads a source, writes what matters into pages, then calls wiki_markSourceIngested so the next session doesn't redo it. Don't paste raw source text into pages.

How do I restrict what an agent can do?

Give its key explicit scopes at /keys. Note the direction of the default: an empty scope list means unrestricted, so a read-only key needs wiki:read and source:read ticked deliberately.

Something's broken

Troubleshooting covers connection failures, 401s and 403s, and the permission asymmetries between MCP and the REST API that cause most of the surprises.