Memories are durable notes that Dexter saves about your factory, your preferences, and prior work so that future conversations have context. Over time this creates a structured record of the operational knowledge that traditionally lives only in your most experienced team members’ heads: process rules, naming conventions, data quirks, KPI targets, shift patterns, and decision logic.
How Memories Work
Dexter builds two layers of memory:
- Workspace memories — per-factory, writable by Dexter. These accumulate what Dexter learns about your specific operation: your process rules, terminology, corrections you’ve given, conversion factors, team roles, how your data exports are structured. Each memory is organized by type (user context, operational knowledge, directives, reference definitions) and carries a date stamp so Dexter can keep entries current.
- Organization memories — read-only, shared across everyone in your organization. Curated by tenant administrators, these carry knowledge that applies organization-wide rather than to one factory.
What Gets Saved
Dexter writes memories automatically when you give it corrections, rules, or operational context — it doesn’t wait for you to say “remember this.” You can also tell Dexter explicitly to remember something: “Remember this for all future conversations: Code 7 means scrap.”
Dexter curates its memories actively — updating existing entries rather than creating duplicates, pruning outdated information, and resolving contradictions by asking you before overwriting.
Viewing and Managing Memories
- Open the Memories section in the left sidebar to see everything Dexter remembers about your factory.
- Ask Dexter what it knows: “What do you know about our weekend operations?”
- Ask Dexter to forget a specific entry: “Forget what you know about the old shift schedule.”
- Import memories — use the Import memories from .prdxm button to load a knowledge file (useful when setting up a new factory or sharing operational context between teams).
- Export memories — export your factory’s knowledge base as a
.prdxm file to share with teammates or transfer to another factory. See Export & Import: .prdx vs .prdxm for details.
Dexter reads its memory index at the start of every conversation to orient itself, so knowledge taught in one conversation carries forward into all future conversations.
You don’t have to explicitly say “remember this” — Dexter saves memories automatically when you provide corrections, rules, or operational context. But you can always be explicit if you want to make sure something sticks.
