GlyphKeeper — The campaign memory that stays true

The problem

Long campaigns deserve better than scattershot notes

Experienced DMs on Discord know the pain: the story is rich, the table is invested—and continuity lives in twelve places, none of them trustworthy.

Forgotten NPCs

Names, motives, and half-finished favors vanish between sessions. The table notices before your notes do.

Lost plot threads

Open questions scatter across chat history, voice notes, and “we’ll get back to that.” Months later, nobody owns the thread.

Inconsistent notes

External docs drift from what Discord already said. Two truths appear—and neither is sealed.

Bookkeeping killjoy

Post-session write-ups steal the high of a great night. Momentum dies in a blank document.

Your campaign already has a truth. GlyphKeeper keeps it sealed—and available at the table.

How GlyphKeeper works

From account to grounded summary

A clear loop for live play: subscribe, invite the official bot, bind the campaign, and keep memory under your control—no infra to run.

Create your account & subscribe

Sign in with Discord OAuth, choose a plan, and open the dashboard. One paid account can own multiple campaigns across multiple servers.
Invite the official GlyphKeeper bot

Add the always-on multi-tenant bot to your Discord server(s). You never create a Discord application or host a process yourself.
Bind a campaign & start a session

Create and bind a campaign to a channel, then open play mode when the table sits down. Co-pilot turns and durable extraction stay tied to the active session.
/campaign create /session start
Ask grounded questions; capture durable events

@mention the bot for answers from authoritative records, campaign-scoped semantic recall, and light context only. Important beats extract automatically—with importance, confidence, and name normalization.
Inspect & edit in Discord or the web

Timeline, recall, edit, forget-with-preview, and link/unlink characters & locations. The web Memory UI and entity browser give the same source of truth a richer surface between sessions.
End session → trusted summaries

Session and campaign summaries regenerate from stored truth only—recap, key outcomes, and active threads you can trust next week. Session 0 intake and DM Planning live in the web app.
/session end

Core capabilities

What ships at launch for the table that already exists

Continuity without the bookkeeping burden—and without handing the story to a chatbot that freestyles your world.

Grounded memory & semantic recall

Campaign records are the source of truth. Semantic search stays campaign-scoped so answers pull from your history—not a generic model’s imagination.

Durable event extraction

Importance and confidence filtering keep junk out of canon. Entity names normalize to the spellings already stored for the campaign.

Full memory toolkit

Timeline, recall, edit, forget (preview then confirm), and link or unlink characters and locations. Repair drift without rewriting history by hand in a wiki.

Grounded session & campaign summaries

Summaries only use authoritative stored data—structured recap, key outcomes, and active threads. Regenerate when records change; the fiction stays honest.

Co-DM allowlist

Owners manage who can mutate durable memory. Co-DMs share the load; the public table can still inspect continuity without rewriting it.

Web memory, Session 0 & Absent Player

Dashboard for account, campaigns, and usage. Web timeline & entity editor. Session 0 intake and DM Planning weave into play. Absent Player is opt-in, consent-required, tagged, and reviewable.

Live Discord experience

Slash commands that respect the table

Once the official bot is invited, this is the surface at the table. Mutations stay protected. Inspection stays open.

Permissions at a glance: Public — inspect Mutator — owner or Co-DM Owner — Co-DM allowlist

/campaign create

Channel Become owner & bind the campaign

/session start

Mutator Open the active play session

/session end

Mutator Save grounded summaries & close session

/memory recall

Public Semantic search over campaign events

/memory timeline

Public Browse recent events newest-first

/memory edit

Mutator Correct event text; refresh search vectors

/memory forget

Mutator Preview matches, then confirm delete

/codm add

Owner Authorize a Co-DM on the allowlist

/memory regenerate-summary

Mutator Rebuild session, campaign, or both

Mutations reply ephemerally. Unauthorized users hear a clear “owner required” or “owner or Co-DM required”—not a vague failure.

Philosophy

Not an AI DM. Not another notebook.

GlyphKeeper sits where long-running Discord tables actually need help: live presence, trusted structure, and human control—never a freestyling storyteller, never a wiki that forgets the room.

Full AI Dungeon Masters

Invent & take over

They generate plot, play NPCs as gospel, and slowly replace the human’s creative authority. Fun as toys—dangerous as campaign truth. GlyphKeeper will not run your game for you.

Pure note-taking tools

Outside the table

Wikis and docs live away from Discord. They don’t hear the session, don’t extract durable beats, and drift the moment you’re tired—leaving two competing truths.

GlyphKeeper

Live Discord + sealed memory

Always-on co-pilot in the channel. Structured records as authority. Owner and Co-DMs decide what endures. The human DM stays sovereign; continuity stays sealed.

Memory is the source of truth. The model narrates around retrieved state; it does not invent canon.
The bot is a co-pilot—a continuity engine, never a replacement for the person running the game.
Owner + authorized Co-DMs retain explicit control over durable memory.
Continuity over pure simulation. Long campaigns feel personal and continuous so you can focus on the table—not combat engines or freestyle worldgen.

Not a replacement DM. Not another notebook that forgets what Discord already said. Continuity you can trust.

Launch path

At launch, then next—core first

Public launch ships the hosted co-pilot and continuity surface. Simulation and deep engines stay deliberately later.

At launch

Official always-on multi-tenant bot
Web dashboard — account, subscription, campaigns, usage, invite the bot
Web Memory UI — timeline + entity browser/editor
Session 0 intake — setting, tone, goals, bonds, open threads
DM Planning Session — pre-session co-planning grounded in party history
Absent Player — opt-in, consent required, tagged & reviewable
Full live co-pilot — bind, session, grounded answers, extraction, memory toolkit, summaries, Co-DM allowlist

How you use it

Discord remains the primary live-play client
Web app for account, planning, Session 0, and memory review
One account, many campaigns across many servers
Plans: Adventurer · Keeper · Loremaster (annual savings available)

Deliberately later

Combat assistant (track / log / suggest) before any full combat engine
Deeper simulation only if demanded by real usage
Continuity stays the product; engines are optional later

Get early access

Join the GlyphKeeper waitlist

Be first when the hosted co-pilot opens. Official bot, web dashboard, and campaign memory that stays true—no bots to host, no stack to babysit.

Early waitlist members get first access and a founder-friendly offer when the hosted product opens.

Join the Community Discord

Prefer fully local? glyphkeeper-local (self-hosted + Ollama) is supported for power users and privacy-focused tables via Patreon.

The campaign memory that stays true.