Memory by use case
AI memory for game characters
Characters that remember what the player did to them.
Why memory matters here
A character who greets the player the same way after being rescued, robbed or ignored breaks the world. Memory lets characters hold a history with each player: favours, grudges, promises. Because a game has many characters and a tight time budget per line, recall must be small and fast.
Who a memory belongs to
One memory per character per player, plus a shared world memory for events everyone would know about.
The moment it shows
The blacksmith brings up the sword the player never paid for, thirty hours later.
What to remember
- What the player did that this character saw or heard about.
- Promises and debts in both directions.
- How the character feels about the player, as a short summary.
What to forget
- Things the character could not have known.
- Small talk, after it has shaped the relationship summary.
- Real personal details a player types into chat.
See recall before you build it
Add a few facts from your own use case and ask a question.
Game characters: common questions
How many memories should a game character keep?
Few. A relationship summary and a short list of key events are usually enough, and they keep each line of dialogue fast to generate.
How do characters learn about events they did not see?
Through a shared world memory. Events that would become common knowledge are written there, and each character recalls from both.
Other use cases
Customer support agents
Stop asking customers to explain the same problem a third time.
What to rememberCoding assistants
Project conventions learned once, applied in every session.
What to rememberPersonal assistants
An assistant that knows your week, your people and your preferences.
What to rememberSales copilots
Every call starts where the last one ended.
What to rememberPack the doko. Ask it anything.
Nine memories, one question, no account. See which facts an agent would carry into its next answer.