Memory Workspace 🎭

The memory workspace is the web UI's home for the memory loop. Use it to inspect saved captures, follow source imports, and run synthesis interactively. Inspection is optional: users do not need to review each memory entry or clear a queue for automatic processing to run.

It lives at the protected /memory route. Earlier releases called this surface the cockpit; it is now the workspace.

What's in the Workspace

Surface	Route	Purpose
Overview	/memory	Activity feed of recent memory writes
Captures	/memory/captures	Saved captures and optional inspection
Imports	/memory/imports	Source import jobs and their progress
Sources	/memory/sources/[id]	A single import source and its records
Synthesize	/memory/synthesize	Interactive plan, draft, and verify

Activity Feed

The overview shows a unified feed of memory activity across the org: what was remembered, what was reflected, what was imported, and what synthesis ran. It is the fastest way to answer "what has the team's memory been doing".

Captures

Captures are raw, low-friction memories created with sibyl capture or the remember flow. The captures surface lists them so you can:

• Read the original content and inspect linked memories
• Follow processing state and provenance
• Make an optional correction or remove an unwanted capture

The dream-cycle handles automatic validation and promotion of eligible candidates. Captures with no graph links are still saved; the unlinked count is not a request for manual approval. Open a capture when you want to inspect or correct it.

Starting with 1.3.2, a newly projected memory appears once in the capture list. Sibyl keeps the verbatim raw memory and its projection, but hides the raw row after recording their relationship.

Existing raw memory and projection pairs can still appear twice after an upgrade. Startup does not backfill those pairs: the operation scales with stored captures and can delay readiness and other database clients. Operators can schedule the optional CONTENT_RAW_CAPTURE_PROJECTION_FOLD_BACKFILL operation from sibyl_core.backends.surreal.content_schema during a quiet maintenance window. The backfill marks matching pairs for the same organization and principal without deleting either record.

Imports

The imports surface tracks source import jobs. Source import ingests structured external records, such as a mailbox archive, into raw memory. Because imports are resumable, the surface shows checkpoint progress and lets you see exactly which records landed.

Transcript ingestion (sibyl ingest claude-code/codex) and document collections (sibyl docs) are additional memory-feed paths that land records here.

Synthesize

The synthesize surface runs source-grounded synthesis interactively. Set a goal, pick scope, and run plan, draft, and verify with the verification report rendered inline. It is the same engine as sibyl synthesis, surfaced for review instead of scripting.

Memory Spaces

Memory is scoped. A memory has a scope (private, team, shared, and similar) and the workspace respects it, so you see the memory you are authorized to see. Preview what an agent could recall from a given set of spaces with:

sibyl admin memory space preview-agent

This makes sharing boundaries explicit before you widen a scope.

Access

The /memory route is protected. Reaching it requires an authenticated session with access to the organization. Memory is org-isolated like every other Sibyl surface; see Multi-Tenancy.

Next Steps

• The Memory Loop - The cycle the workspace supports
• External Sources - Crawling and source import
• Synthesis - The synthesize surface in depth