← Back to library

Give your agents one shared wiki that only one agent edits

Siim Tolk wrote up how his two home agents, Hermes on a local model and Claude Code, stopped drifting apart once they began sharing one wiki that a lone steward agent maintains, and he reports a nightly 22-question test against his live setup. We describe the pattern in our own words with our own prompt.

  • OutcomeReplace scattered agent memories with a single Markdown wiki in git: every agent reads a short daily brief from it, agents and scripts file sourced notes into an inbox instead of editing pages, one steward agent checks and merges those notes each morning, and private agent memory keeps only personal preferences.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditSiim Tolk
View original
Works with
Claude CodeOpenClawCustom agentClaude

Published Nov 1, 2026Updated Nov 1, 2026AI dry run on sample input: passed Nov 1, 2026Source verified Nov 1, 2026

When should you use it?

  • You run two or more agents that each keep their own memory of the same system
  • Agents give confident but outdated answers about ports, paths or schedules
  • Lessons learned in one session are lost by the next

Not for: A single agent with a short, stable setup; Teams without anyone willing to review the steward's merges now and then; Secrets or credentials, which should never be written into the wiki

What do you need, and what do you get?

You need

  • A git repository for Markdown pages, readable by every agent
  • One agent to act as steward, with a scheduled morning run
  • An inbox folder per agent for proposed notes
  • A way to load a short brief into each agent's sessions

You get

  • Wiki pages that each state their purpose, whether they were checked, and their sources
  • A status page with current work and open questions for you
  • A daily brief of the most-needed facts loaded at session start
  • A morning merge log showing which notes were accepted or rejected and why

How does it work, step by step?

  1. Create the repositoryStart with a handful of pages on the facts agents ask about most, each citing where it came from.
  2. Close the write pathTell every agent it may read the wiki but only file notes, with sources, into its inbox.
  3. Appoint a stewardSchedule one agent each morning to check every note against the system and merge or reject it.
  4. Load a briefGenerate a short summary of key facts nightly and load that summary when each session begins.
  5. Clean private memoryReplace setup facts in each agent's own memory with a link to the matching wiki page.
  6. Measure itAsk a fixed set of questions with known answers and compare results with and without the wiki.

The prompt

Our own prompt, inspired by Siim Tolk and written to work in Claude Code, OpenClaw, Custom agent and others. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
You are the steward of our shared knowledge base in {repo}. You are the only agent allowed to change its pages.

Each morning, read every new note in {inbox_folders}. For each note, open the page it concerns and confirm the claim against {live_sources}.
If it checks out, update the page, mark it checked with today's date and the source, and log the change. If it does not, reject the note and record why.
Then rebuild the daily brief: no more than {brief_length} of the facts agents asked about most this week.
Never write passwords, keys or tokens into any page, and list any question only I can answer on the status page instead of guessing.

Inspired by Siim Tolk: Less memory, more wiki: how my AI agents got up to 3× faster on 4× fewer tokens. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • If agents can still edit pages directly, one wrong fact spreads to the rest. Keep the steward as the only writer.
  • Self-improving skills can quietly store stale facts again. Route skill changes through the steward too.
  • A long brief costs tokens in every session. Keep it to the facts asked about most.
  • Never put passwords or keys in the wiki; link to where they are managed instead.

Our take

Shared memory between agents usually fails in one of two ways: nobody writes anything down, or everybody does and errors compound. Tolk's answer to the second problem is the part worth copying, a single steward that merges sourced notes while every other agent only proposes. That is the same reason codebases have reviewers, and it keeps one model's mistake from becoming every model's fact. His other finding is easy to miss: a fuzzy instruction stored in one agent's private notes won out over the precise value on the wiki page, so cleaning agents' own memories matters as much as building the wiki. We also appreciate that he measured it against a live system rather than describing a feeling; still, it is a single home lab, and the results may not hold elsewhere. Our caution is upkeep, since a steward that is never checked can drift too, so read its merge log weekly. In our dry run with a fictional two-agent setup, a note claiming a backup job ran at 01:00 was rejected because the scheduler showed 02:30, the steward corrected the page with a source line, and the next brief carried the right time.

Where the time goes back: Agents stop rediscovering the same facts every session, answer from one checked source, and you stop untangling conflicts between their private memories.

FAQ

Which agent should be the steward?
The most reliable one you have. Tolk uses Claude Code, with a dedicated skill, since he trusts it more than his local model to judge each note.
Did it actually help?
In his write-up both agents answered all 22 questions correctly with the wiki and were faster on fewer tokens, while without it they missed several. That is one person's home setup, so test it on your own questions.
Do I need special software?
No. It is plain Markdown in git, which you can also browse in Obsidian or any editor.

Source and credit

Inspired by Siim Tolk. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Less memory, more wiki: how my AI agents got up to 3× faster on 4× fewer tokens
Creator
Siim Tolk
Published on
siimtolk.github.io
Original date
Oct 31, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Nov 1, 2026: passed. Dry-run tested by our AI test agent on sample input. Single writer, every merge sourced and dated, wrong claim rejected with reason, secret kept out, brief stayed short.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 1, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run a supervised pull request review inbox

Your review queue arrives pre-read, with draft comments you edit and send yourself.

Credit: u/jtompl on r/ClaudeCode

Under an hour
Operations & AdminWorkflow✓ AI dry run

Test every agent change against 20 fixed real tasks

Collect about twenty real jobs your agent handles, including a few it should refuse or stop on, lock that list, and rerun all of them after each change to its prompt, tools, model or setup, scoring completion, forbidden actions, correct hand-offs to a person and cost so you can see what a change improved and what it broke.

Credit: u/ChefOk4636 on r/AI_Agents

Under an hour
Operations & AdminWorkflow✓ AI dry run

Treat agent tickets like patients with staged review gates

Ship a large, correctness-critical feature written entirely by agents, with planning, review rounds and escalation rules that keep quality at human standard.

Credit: Adam Storm

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run a multi-phase RAG rebuild from Markdown specs

Move a retrieval app across infrastructure, backend, data and UI layers while the agent keeps one consistent plan and proves each change with tests.

Credit: Remigiusz Samborski

An afternoon+