All Documentation

AI Context: Deciding What Your Assistant Knows

A connected assistant is only as good as its context. Grimoire gives you dials: always-on canon, graphs, a session spotlight, and an audit log.

Once your campaign is connected to Claude, the interesting question becomes what the assistant should know and when. A two-year campaign will not fit in any context window, and would not help if it did: an assistant drowning in every tavern you ever named is worse at answering "what would Lord Blackwood do next?" Grimoire solves this with layers, from a small always-relevant core out to everything-searchable, and gives you a dial for each.

The always-on core: your campaign's canon

Two things are in context for every AI conversation:

  • The Campaign Bible: a living summary document of your world's premise, themes, and current situation. Edit it under Knowledge → Campaign Bible, or ask Claude to update it for you as the story moves. Keep each fact to a sentence; this is the assistant's first impression of your world.
  • World Foundations: the deep-canon graph (creation myths, cosmology, the ancient pacts) from the first tab of the Graphs workspace.

If the assistant gets your world's fundamentals wrong, fix them here, not in a chat message.

Graphs: teaching structure, not just facts

Any graph can be included in AI context: open it, and flip Enable Graph in its settings panel. An included Political Web means the assistant does not just know the Silver Hand and the Merchant Guild exist; it knows they are allies, and it can reason about what a rivalry with one means for the other.

Include the graphs that carry your campaign's active structure. A heist campaign wants the conspiracy graph in; the geography tree can usually stay out (locations are searchable anyway).

The spotlight: what matters right now

Individual entities carry an Include in AI context switch, found in the AI Context card of a graph node's detail panel. Grimoire manages it for you: entities your recent sessions touched move into the spotlight automatically, and drift out as the story moves on. Pin an entity to override the automation in either direction, the villain who must always be in context, or the spoiler who must never be.

This is why logging sessions makes the assistant sharper: the session window (your recent sessions plus every entity they reference) rolls forward with your table, so "context" always means "current."

You can see the result of all these dials in one place: the AI Context Window panel on the Knowledge tab shows exactly what is included right now, layer by layer.

Everything else: searchable, not resident

The rest of the campaign is one tool call away. The assistant searches by keyword, lists by category, and pulls full records on demand. Nothing is lost by being outside the spotlight; it is just fetched when asked for instead of always present.

Who sees what

Context respects roles, enforced server-side:

  • Your connection (as GM) sees the whole campaign.
  • Player connections (if you enable player access) see only what the portal would show that player: no GM Secrets, no session prep, no other players' wikis. The same question gets a smaller, honest answer.

Every call from every connection lands in the Audit Log (Knowledge → MCP & AI → Audit Log), labeled GM or player, so there is never a mystery about what an assistant read or wrote.

Prompts that use the system well

Worldbuilding

"Create five NPCs for the Thieves' Guild, tied into existing factions where it makes sense."

"Generate a backstory for Millbrook that connects to the Sundering."

Session prep

"What loose threads from recent sessions should I address next game?"

"Draft a side quest involving the Merchant's Guild that could resolve the missing-shipments thread."

At the table

"What does Lord Blackwood actually know about the Sundering?"

"Who in the city might fence stolen reliquary items, based on what's established?"

The pattern: prompts that lean on connections, canon, and threads get answers a generic assistant cannot give, because the structure behind them is yours.

Keeping it sharp

  1. Log sessions. The spotlight follows them; an unlogged month means a stale spotlight.
  2. Keep the Campaign Bible current when the big picture shifts, not after every scene.
  3. Enable the graphs that carry your story's structure and leave the rest searchable.
  4. Pin sparingly. Ten pinned entities is a spotlight; a hundred is the flood you were avoiding.
  5. Trust the tiers. Visibility is enforced at the server, so a player's assistant can be handed the connector URL without a second thought.