Your first hour with WitWiki
By the end of this hour you have a wiki with a real hub built from the CLAUDE.md you already maintain, an agent that has written to it, a page you edited in the browser, and a History that shows both — one line apart. Nothing here needs a second person yet; inviting your team comes after.
If you have not connected an agent, /connect does it in ten minutes (Getting started is the same by hand), and it ends on the step this page begins with.
1. Check you are in the right project
Ask your agent to call wiki_getIndex. A new project is seeded with one
starter page, and that page coming back is the confirmation that the key,
the project routing and the tools all work.
An empty index means you connected with a different credential than the one that owns your pages. An API key and Claude Desktop's OAuth connector resolve to separate projects; if you set up both, the wiki you see in the browser and the wiki your agent sees are not the same one until you point them at the same project. Connecting your agent explains the two paths.
2. Hand it the first job
/connect shows this prompt the moment the handshake lands. Paste it into your agent as-is:
Call wiki_guide to learn the conventions. Then read CLAUDE.md and AGENTS.md in this repo and split them into one wiki page per topic under concepts/, architecture/ and guides/, cross-linking related pages with [[wikilinks]]. Rewrite the index page to link every page you made, then run wiki_lint and fix anything it reports.
It is the smallest job that produces something worth reading. Your CLAUDE.md
and AGENTS.md already hold the knowledge a new teammate needs; the agent turns
each topic into its own page under concepts/, architecture/ and
guides/, links related pages with [[wikilinks]], rewrites the index so
every page is reachable, and runs wiki_lint so nothing dangles. The
wiki_guide call at the start is where it learns the conventions — paths,
links, one topic per page — so you do not have to explain them.
On /connect, the indicator flips to First edit ✓ with a link to the page as soon as the first write lands.
3. Watch the feed
Open Home. It reads This week in <your project> and lists what happened as sentences, grouped by day: claude-code created Concepts / Auth, claude-code rewrote Index. A square mark is an agent; a round one is a person. The sidebar names the agents connected to the project and when each last called.
This is the page you come back to. When three people and two agents share a wiki, it is how you know what moved without opening anything.
4. Edit one block yourself
Open any page the agent made and press Edit. The editor works in blocks:
click into a sentence and change it, or type / for a new block — a heading,
a list, a table, a code block, a diagram. Press ⌘S or Save.
Two things to notice. The byline under the title now says you edited this just now, where a moment ago it named the agent. And History — the word in the byline — lists both writes: the agent's create and your edit, one line apart. The save only rewrote the block you touched, so the diff between the two versions is the sentence you changed and nothing else.
5. Let the agent change a page you are reading
Keep that page open and ask the agent to add a line to it — append a "See also" section to the page I have open. The byline moves on its own: the agent's name, just now, and the new section appears without a reload.
If you were editing the page at the time, the editor does not lose your work or silently overwrite theirs. It shows what they changed and asks: merge your edit onto their version, discard your edit, or overwrite theirs. History and conflicts explains each choice and what the version token behind them means.
6. Make it a habit
A connected agent has the tools but no instinct for reaching for them. Paste
the CLAUDE.md or AGENTS.md snippet from Teaching your agent into
your repo. It tells the agent to read the wiki at the start of a session, to
record what it learned at the end, and to change pages with wiki_patchPage
against the version it read — so two writers never land on a page the other
has not seen.
What to do next
- Structuring a wiki — paths, links, and what makes a page worth writing.
- Teams, roles, and what an agent is allowed to do — invite people, scope keys.
- MCP tool reference — every tool, its parameters, and what it returns.