The wiki plugin
One line turns on a workspace's long-term memory: the voice, the standing rules, who is who, the decisions that hold — as markdown artifacts the agents write above a confidence bar, a researcher answers from, a debrief keeps current after every finished piece of work, and a curator consolidates on Fridays. What it is, who it is for, and what has changed since it shipped.
Status: shipped, at version 1.3.0 in vocion-core (packages/core/templates/plugins/wiki/).
First shipped 2026-09-18 (vocion-core#451, its
first post); the wiki read as pages is
#659 (2026-09-24). Docs:
Wiki.
# workspace.yaml
plugins: [wiki]
What it is
A workspace already has fast memory — learnings, one rule per step — and per-client memory — a data room's rules and notes. The wiki is the slow layer: how we sound, what we never do, who owns what, what we decided and did not walk back. Every agent needs it before it writes anything a person will read.
A page is a markdown artifact in the wiki folder, so versions,
restore, the preview pane, share and citation come free. The index and the pages that fit are
mounted into every agent's context each turn; read_wiki_page fetches one that did not. The
writer is the agent: write_wiki_page proposes a change with a confidence, and above the
plugin's bar (0.6 in its trust.yaml) the page is written at once and shows in Review › Decided
with Undo; below it a person decides on a card. Every save indexes for search. Nobody pastes into
the wiki.
Who it is for
A workspace where the same correction has been made in more than one conversation. Where a person
has said "remember this" about something that is not one small rule. Where an agent had to ask
for the voice, the house style, or who owns what, instead of reading it. Where the repo already has
markdown pages describing how the workspace works and nobody reads them. Those are the plugin's own
recommend.when lines — what the chat reads to suggest turning it on.
What has changed since it shipped
1.1.0 — seeded from the repo, and a researcher. A workspace folder can carry its first pages
as files under wiki/, and workspace:apply seeds them: a missing page is created, a changed
file refreshes its page, and a page anyone has since edited in the app is kept, with a warning
naming it. The Wiki researcher joined the curator: the front door in chat and over MCP, it
researches against the wiki first and then the knowledge index and the web, and offers to write
the page whenever a conversation produces a standing fact or a plan. The router sends it the
questions it handles — wiki, standing rules, research, plan, decision — when nobody names an
agent.
1.2.0 — the debrief. Finished work is read once for what it settled. The wiki-debrief
automation fires on core's completion events — worker_run.completed, mission_run.completed,
conversation.ended, pr.merged — and the researcher reads the run, the conversation or the pull
request, decides whether a standing fact, a decision or a plan changed, and proposes the page
revision under its own ledger. Work that settled nothing writes nothing. This is the piece of the
learning loop that keeps a standards page from drifting behind
what actually shipped.
1.3.0 — read as a wiki. The index reads as pages, not a grid: the title leads with its first paragraph under it; there is a home; one page opens at a time; links open pages. The version and the last author drop first when the screen is narrow (#659). A production crash in the wiki page — a function crossing into the client view — was fixed the same day (#662).
Earned trust, per writer. The researcher's writes key on their own ledger
(wiki.write_page.wiki-researcher) and start at review: a person sees each proposed page until
the Autonomy page shows the evidence to promote it. The curator's and every other agent's writes
stay under the shared rule at 0.6.
What it measures
Pages that exist. Pages written by the agents this week. Edits a person had to decide on — the fewer, the more trusted.
Where it fits with the others
The software factory keeps its per-product standards pages here — the product lens and one block per category the PM reads before deciding (What a week of Slate commits taught the factory). Data rooms keep a client's own material; the wiki keeps what is true of the workspace.
Customise it in the workspace, never by editing the plugin: patch either agent with extends: core, change a bar in trust.yaml, give your lead the wiki-context skill, seed pages under
wiki/. The fixtures in the plugin are fictional.