01
Type @ mid-sentence
Anywhere in a block, on any page, in any of the three wiki spaces. Players get it too, scoped to what they can see.
The wiki with a database underneath
The campaign wiki that knows what its pages are about.
Write lore in sentences. Mention an NPC, a place, or a faction with @ and the page links itself to the record in your campaign database, and the record lists every page that mentions it. Real-time co-editing, GM secrets kept per block, tables, and a wiki for every player, in one place.
Free to start. Players are always free.
What is a campaign wiki?
A campaign wiki is the prose layer of a campaign: the lore pages, handouts, session write-ups, and house rules the table actually reads.
In Grimoire the wiki sits on top of a typed campaign database. A page about a place is linked to the record for that place, and the record knows every page that mentions it. The world gets written down in sentences and stored as fields, and the two never drift apart.
One mention, two directions
The page links to the record. The record links back.
Fourteen typed categories, from NPCs and factions to mechanics and vehicles, are all one keystroke away inside any sentence. Each mention is a real link in both directions, checked against the database, so nothing points at a thing that no longer exists.
02
Pick from typed categories
Fourteen kinds of thing, named in your campaign's own vocabulary. A pantheon in one game is a corporate board in another.
03
The chip stays live
Click opens the record. Hover previews it. Rename the entity and every chip that mentions it follows.
04
The record knows
Every entity lists the pages that mention it, with the sentence around the mention. The wiki and the database agree.
Pages that link to pages
Two brackets, and the page you meant is a link.
Type [[ and pick from the pages you can see. If the page does not exist yet, create it from the same menu: it lands as a child of the page you are writing, inherits its visibility, and the link is already in your sentence.
Every page keeps a "Linked from" list in its right rail, so a lore page knows which recaps, handouts, and journals point at it. Rename a page and every link to it follows. Middle-click a link and it opens in a new tab like any other link, because it is one.
Inside the editor
Blocks built for the table
Every page is a stack of blocks. Headings, paragraphs, callouts, tables, images, and page cards, each one movable, each one able to carry its own visibility.
Slash commands
Type a slash on an empty line and insert headings, callouts, tables, images, or a whole new page without touching the mouse.
Tables with /table
A grid with a header row, rows and columns from the block menu, and mentions and page links working inside every cell.
Per-block visibility
Any block can carry its own tier. The tavern page your players read and the paragraph about who holds its debts can be the same page.
Blocks you can rearrange
Every block drags. Restructuring a lore page is a move, not a rewrite, and a page card moves its whole page with it.
Whose pen, whose eyes
Three spaces, and secrets that stay secret everywhere.
A page inherits its visibility from the page that links it, then from its parents, and the rule holds all the way down. A page a player cannot reach is absent from their tree, their search results, their mention lists, and their backlinks. It does not exist for them, and neither does its title.
Yours
Campaign wiki
The world as you publish it: lore, handouts, house rules. Read-only for players unless you open it up.
The table's
Party wiki
Always player-editable. Plans, theories, the loot ledger, recaps in their own words. The campaign's memory, co-authored.
Each player's
My wiki
A private notebook per player, visible only to them and to you. Character journals and suspicions not ready to be said out loud.
Six hands, one page
Real-time, no locks, no merge.
The whole table can be in one page at once. You see who is on the page and who is typing, every keystroke syncs live, nobody waits for a lock, and undo behaves even when four people are writing.
It runs on conflict-free replicated documents, the same approach the big document suites use, and every editing session verifies campaign membership server-side before a connection opens. A reload mid-sentence keeps the sentence. The recap your player writes while you referee the argument about the plan: that is the wiki working as intended.
From scribble to canon
The note-taking app that remembers forward
Session notes in Grimoire are not a dead end. Capture during play with slash commands and @ mentions; afterward, the notes become a session recap, and the recap's key events can be marked canon.
Canon is what the rest of the system runs on. The campaign journal threads it onto the timeline, and under the Revealed world setting the player portal uses it to reveal the NPCs, places, and items the session actually touched. Because the notes mentioned those entities by chip, the system already knows which ones.
That loop is the difference between a note-taking app for D&D and a notes app that happens to contain D&D: your Tuesday-night scribbles end up driving reveals, timelines, and next week's prep.
Where the wiki fits
Session recap tools vs structured campaign state
Three kinds of tool get called "campaign notes". They store different things.
A session recap tool
What was said
A transcript or a summary of the night. Useful, and gone the moment the world changes.
A notes app
Pages
Prose that mentions your NPCs by name. Nothing in the app knows that "Mira" on page nine is the same Mira as page forty.
A campaign database
What is true
Who leads which faction, where the relic is, what the players have been told. Grimoire's wiki is where that truth gets written in sentences.
The wiki lives beside the campaign knowledge graph and the typed campaign database: structure in the records, prose in the wiki, one campaign underneath. Nothing has to be written twice.
Recently shipped
-
Grimoire 1.5.1: Wiki Page Links, Tables, and a Sharper Grimoire MCP
Inline page links with [[, @ entity mentions with create-on-the-spot, simple tables with /table, visibility that resolves end to end, and a link index that stays truthful.
-
Grimoire 1.5: The UX Revamp
Full-content wiki search with a command-palette Wiki mode, a right rail with page contents and mentioned entities, a safe Home-and-Trash story, and undo/redo that holds up in collaborative sessions.
Optional
Your AI client can read the wiki too
Grimoire runs fully without a single AI feature. If you already use Claude, ChatGPT, or another MCP-compatible client for prep, Grimoire MCP serves it the same world: it can search the wiki by text, read and write pages and tables, and mention entities with the same chips, under the same visibility rules the app enforces.
You bring your own client, so there is no token markup and no model lock-in. Turn it on when you want it. Ignore it forever if you do not.
See how Grimoire MCP works →All three of my players are connected and using Grimoire during our sessions. The wiki and mechanics pages are clear and easy for them to navigate on their own, and combined with Claude on my end for prep and canon tracking, it has made running this campaign so much smoother than I expected.
FAQ
Campaign wiki questions, answered
What is a campaign wiki?
A campaign wiki is the prose layer of a campaign: the lore pages, handouts, session write-ups, and house rules the table actually reads. In Grimoire the wiki sits on top of a typed campaign database, so a page about a place is linked to the record for that place, and the record knows every page that mentions it. Prose and records share one home instead of drifting apart across separate apps.
Do mentions in the wiki link to the campaign database?
Yes. Type @ in any block and pick from the campaign's typed categories: NPCs, player characters, creatures, locations, factions, pantheon, quests, items, lore, world rules, sessions, session prep, mechanics, and vehicles. The mention becomes a chip that opens the record on click and previews it on hover, and the record's page lists every wiki page that mentions it. The link is stored in an index that is checked against the database, so a mention of a deleted entity never leaves a dangling reference.
What happens when I rename an entity?
Every chip that mentions it updates to the new name the next time the page is opened, with no find-and-replace. The same is true for page links: rename a page and every [[ link to it follows. Players see the name the page was saved with until the GM opens it again, which keeps a renamed secret from leaking through the rename itself.
Can my players edit the wiki?
Where you allow it. The party wiki is always editable by everyone at the table, each player has a private wiki only they and the GM can see, and the campaign wiki you author is read-only for players unless you open it up. All three use the same real-time editor, and players can mention entities and link pages the same way you do.
Can I keep secrets on a page my players can read?
Yes. Visibility is per-block, not just per-page. A location page can be player-visible while the paragraph about what sleeps under it is marked GM Secret, and that block does not exist in the player's copy of the page. A page that a player cannot reach is absent from their tree, their search results, their mention lists, and their backlinks, so its title does not leak either.
Is it good for taking session notes?
It is built for exactly that. Slash commands insert blocks without leaving the keyboard, tables drop in with /table, and search plus a command-palette Wiki mode make mid-session lookups fast. When the session ends, the notes become a recap whose key events you can mark canon, which is what drives the timeline and the player portal's reveals.
How is this different from a session recap tool?
A recap tool stores what was said at the table. A notes app stores pages. A campaign database stores what is true about the world: who leads which faction, where the relic is, what the players have been told. Grimoire's wiki is where that truth gets written down in sentences, and because every mention is a typed link, the sentences and the records stay in agreement.
Does it work offline?
No. Grimoire is a hosted, collaborative tool, and the wiki's real-time co-editing depends on a live connection. If offline-first local files are your hard requirement, an Obsidian vault is honestly the better fit; the Obsidian comparison covers that tradeoff.
Hand the table a pen.
The recap they write, the secret you keep, and the NPC you both mention: one page, one record.
Free to start, no credit card. The whole table gets the editor.