Verification guide
Run these tests in any connected AI tool — Claude, ChatGPT, Codex, Cursor, Lovable, or Gemini. Each one checks a different part of Engrams. Takes about 5 minutes.
0 of 5 passed
Basic memory
Checks that Engrams can save a memory and retrieve it in a new conversation.
remember automatically)Expected result
The AI answers "Rust" — it remembered across conversations via Engrams.
Checks that permanent facts about you are stored and recalled.
Expected result
The AI mentions your name and role. Profile memories persist permanently and load at every session start.
Cross-tool memory
Checks that memories saved in one AI tool are available in another.
Expected result
The second tool knows about Bearer token / JWT auth — the memory was saved in one tool but is accessible everywhere. One brain, any interface.
Getting started
Engrams picks up your existing project context automatically.
Expected result
Your project context is saved to Engrams. Next session — in any AI tool — it all comes back automatically.
Share a project with someone else. Both of you get the same memory.
Expected result
Both of you read and write to the same memory. Decisions, tasks, and context are shared. Each memory shows who created it.
Engrams uses seven memory types, each designed for a different kind of information. Your AI chooses the right type automatically — you don’t need to specify it.
profile
LOADS EVERY SESSION
Permanent facts about you — name, role, preferences, expertise. Saved once, recalled forever. Updated when facts change.
context
LOADS EVERY SESSION
Active project state — what’s deployed, what changed, current status. The AI’s working memory for your project.
decision
LOADS EVERY SESSION
Choices you’ve made with rationale. Why you picked one approach over another. Prevents the AI from re-opening settled debates.
learning
SURFACES WHEN RELEVANT
Insights worth keeping — what worked, what didn’t, patterns discovered. Retrieved via semantic search when the topic comes up.
episode
LOADS EVERY SESSION
Session summaries — what was done, what’s next, open questions. Lets your AI pick up exactly where the last session left off.
instruction
LOADS FIRST, HIGHEST PRIORITY
Rules and protocols for how your AI should behave in this project. Loaded before everything else. Use for format rules, workflows, or constraints.
task
LOADS EVERY SESSION
Structured work items with status, priority, and owner. Create, update, and track tasks across sessions. Your AI knows what’s in progress and what’s done.
Engrams versions your memories. When a memory is updated — a task moves from in_progress to done, a decision is revised, a profile fact changes — Engrams writes a new row and marks the previous one as archived. The archived row is not deleted. It stays in the database with a pointer to the version that replaced it.
The current version of each memory. This is what your AI sees when it calls recall or load_project. The dashboard "Active memories" count is this number.
Older versions that have been replaced. Never returned by recall or load_project. Preserved so you can audit how a decision or task evolved over time.
Why keep archived rows at all? Because the history of a decision is often as useful as the decision itself. If a task was set to done but later reopened, or if a profile fact flipped, the archived row lets you reconstruct what the AI believed at any point.
Does archived count against my plan? No. Plan limits apply to active memories only — updating a task or revising a decision never eats quota.
Engrams is working correctly. From here, everything is automatic — just use your AI tools as you normally would. Memories build up over time.
Questions? Write to hello@engrams.app