Skip to content
Agentic Craft

Memory

Patterns for persistent memory, cross-session recall, context awareness, auto-detection of preferences, and privacy controls for reviewer data.

Memory Panel

The reviewer's stored preferences and facts — key-value pairs the agent uses to personalize responses across sessions.

Memories6
enterprise release
Workspace

Preferred release tier

Launch review session12m agoExpires 90 days
Launch Policy v2
Project

Default launch policy

Project brief v331m agoExpires 180 days
Launch review team
Team

Review workspace

Workspace settings1h agoExpires Never
Markdown with operating playbook work unit headers
User

Report format

User preferenceYesterdayExpires 90 days
self-serve onboarding flow
Project

product type

Product notesYesterdayExpires 60 days
Internal launch process
Team

Approval team

Approval policy2d agoExpires 180 days
StateContentBehavior
EmptyPlaceholder with guidance textShown when the agent has no stored memories
PopulatedKey-value list with hover actionsEdit and delete icons appear on hover per row
SearchFiltered list with search inputReal-time filtering by key or value
Memory entries are key-value pairs rather than free text — this makes them scannable and editable without requiring the reviewer to parse unstructured prose. Actions appear only on hover to keep the list clean.

Memory Entry CRUD

View, edit, and delete individual memory entries. Each operation uses inline controls so the reviewer stays in context.

Preferred release tier

enterprise release

OperationInteractionBehavior
ViewDefault displayShows key-value pair with edit and delete icons
EditClick edit iconInline text field replaces value, Save/Cancel buttons appear
DeleteClick delete iconConfirmation prompt with warning text and Confirm/Cancel
All CRUD operations happen inline — no modals. The delete confirmation is intentionally low-drama: a text warning, not a blocking dialog. This matches the lightweight feel of key-value memory management.

Auto-Memory

The agent detects learnable information from conversation and offers to save it as a memory — the reviewer always has the final say.

I see you've been consistently requesting enterprise release reviews across the last three sessions. The reference document Launch Policy v2 appears to be your default reference.

I noticed you prefer enterprise release — save this preference?

StateVisualBehavior
DetectedBanner below agent message with Save/DismissAgent surfaces the detected preference with a clear opt-in prompt
SavedBrief confirmation messageFades in, replacing the banner. Memory is persisted immediately
DismissedBanner removed, muted noteAgent will not re-prompt for this particular preference
Auto-memory is opt-in by design. The agent detects patterns but never persists without explicit reviewer consent. This is critical for regulated environments where auditors may need to justify what data the tool retains.

Memory Context Ring

Visual indicator showing how much memory context is loaded into the current session. Details are revealed on hover to avoid visual clutter.

No memory loaded

Start a conversation to load reviewer preferences and context.

StateRing VisualTooltip
No ContextEmpty ring with muted iconNo tooltip — nothing to show
With ContextPartially filled ring, animated on loadLists loaded memories with key-value pairs on hover or focus
No number inside the ring — the icon signals presence, and the tooltip provides detail on demand. This avoids cognitive load for reviewers who don't need to know the exact count at a glance.

Privacy Controls

Category-level toggles for what the agent is allowed to remember. Reviewers working under NDA or handling sensitive product data may need to disable specific categories.

Preferences

release tier, report format, workflow choices

Document History

Previously reviewed briefs, policies, and launch summaries

Project Context

Current product, team, and approval path

Personal Info

Name, timezone, role at review team

PresetToggle StateNotes
All OnAll categories enabledDefault for most reviewers
SelectivePreferences + Documents on, Context + Personal offCommon for consultants working across multiple review teams
All OffAll categories disabled with confirmationFor sensitive reviews or private review sessions
Privacy controls are category-level, not per-entry — this keeps the mental model simple. Disabling a category does not delete existing memories, it just prevents the agent from reading or updating them. This distinction matters for complex review workflows where data retention policies may differ from data access policies.