Use cases

Ten shapes of agent memory

One memory, scoped per agent. Each use case ships with a full article, a diagram, and a code snippet you can paste into your own codebase.

Coding agent

The conventions your team agreed on, remembered. The refactor decisions, surfaced. One memory per coding agent, reachable via the REST API or SDK.

Read the full article

Deal stages, objections, contact preferences. One memory per rep, an audit trail per contact, a valid_at date on every fact.

Read the full article

Past tickets, resolution channels, the preferred contact path. A returning customer is recognised before the first message.

Read the full article

Recurring mistakes, learning style, the explanation that finally landed. One profile per student, the lesson builds instead of restarting.

Read the full article

EU residency, audit logs, bi-temporal facts; on-prem available for enterprise. Erase everything about a patient with one call.

Read the full article

A long-term timeline of one person. Color preferences that shift, jobs that change, goals that evolve. Memory that compounds.

Read the full article

Deal terms, precedent, and drafting style, remembered per matter. And Deal A's terms can never surface while the agent drafts Deal B.

Read the full article

The runbook step that works now, not the one retired after your last migration. Service owners stay current as teams reorganise.

Read the full article

Every applicant and interview note, plus the day a past candidate's title or availability changes and they become placeable again.

Read the full article

Each client's portfolio drift and their risk tolerance as it stands now, weighting the recent change over the two-year-old intake form.

Read the full article

Scroll for more, or swipe

Want a use case we haven't covered?

Email me with the shape of memory you need and the agent you're using. If it's a recurring pattern, it ends up on this page.

Or install the SDK and start building today.