Admin — Memory

The Memory tab is the raw retained-record view inside Admin — Memory. It covers both AgentCore managed memory and the optional Hindsight add-on. Use it when you need to inspect what was retained before it is routed into query_context or compiled into pages.

Route: /knowledge/memory Route wrapper: apps/web/src/routes/_authed/_tenant/knowledge/memory.tsx Tab implementation: apps/web/src/routes/_authed/_tenant/memory/index.tsx

The legacy /memory route redirects to this tab.

Layout

The page has four primary controls:

• Agent selector — “All Agents” plus every agent in the tenant. Scopes the view to one agent namespace or fans out across all agents.
• View toggle — Memory / Knowledge Graph. Only shown when Hindsight is enabled.
• Search bar — semantic search across memory content, backed by MemorySearchQuery.
• Refresh — manual re-fetch.

Below the controls, the page renders either a DataTable of memory records or an interactive 3D graph.

Memory Records

The table view shows:

Column	Notes
Date	When the record was created or last updated
Agent	Which agent produced the record
Type	Strategy badge: semantic, summary, preference, episode, reflection
Memory	Truncated content preview

Clicking a row opens a detail sheet with full content, metadata, edit controls, and delete controls. Editing depends on the backend:

• AgentCore managed memory — records are immutable by default; the sheet is read-only.
• Hindsight — records can be edited or deleted through UpdateMemoryRecordMutation and DeleteMemoryRecordMutation.

Graph View

When Hindsight is enabled, the graph view renders memory entities and relationships with MemoryGraph (React Force Graph 3D, three.js, and d3-force). It is useful for seeing clusters and relationships, but the compiled Pages tab is the better operator view for durable memory knowledge.

Note

The graph view is a memory-backend inspection tool. It is not the full compiled-memory graph: compiled pages, aliases, links, and source citations live in the Pages surface.

Workflows

Audit What an Agent Remembers

1. Open /knowledge/memory.
2. Pick the agent from the selector.
3. Scroll or search the record list.
4. Click a row to read the full content.
5. If the tenant has Hindsight enabled, edit or delete stale records from the sheet.

Debug Memory Results

1. Run the query from /knowledge/context-engine in the Sources tab.
2. If a memory hit looks wrong, open /knowledge/memory.
3. Search for the same term or filter to the agent.
4. Inspect the raw record and backend metadata.

Delete Sensitive Memory

1. Search for the sensitive term.
2. Click into each matching record.
3. Delete one by one from the detail sheet.

Deletes are hard deletes. For bulk redaction, operate at the SQL layer with a reviewed script.

Data Model

• AgentCore managed memory — Aurora memory_records table with strategy, namespace, content, tags, confidence, access count, and bi-temporal dates.
• Hindsight graph — separate Hindsight-managed entities, relationships, and facts surfaced through MemoryGraphQuery.
• Namespaces — records are namespaced by strategy and agent; prefixes such as semantic_, preferences_, and episodes_ identify the retention strategy.

Known Limits

• All-agents graph is a client-side fan-out. It scales to dozens of agents, not thousands.
• AgentCore records are read-only. Editing is only available when Hindsight is enabled.
• Graph view lacks drill-in. Clicking a node does not open a detail sheet.
• Search is semantic-only. It can miss exact IDs or unusual strings.
• No bulk edit or bulk delete. Every mutation is one record at a time.

Related Pages

• Admin — Memory — the combined operator surface
• Memory — the product model
• Retained Memory — memory contract and backend behavior
• Compiled Pages — how memory becomes durable pages