Memory Quickstart

Initialize project memory and run the first recall query.

Generate a project profile

From the repository root:

picasso memory init
picasso memory list

Then ask the TUI to inspect the project:

/memory

Expected result:

• The memory inspector opens.
• Project, session, and account scopes are visible.
• The selected memory detail shows provenance and controls.

First memory write

Use a prompt that asks Picasso to remember a stable engineering decision:

remember that this repo treats design/Picasso TUI.html as the locked TUI visual source of truth

Expected result:

• The reflection phase classifies the note as a durable project fact.
• The memory write is namespaced to the current account and project.
• The memory entry includes provenance.

Or save a note yourself, from the shell or the terminal app:

picasso memory add "this repo treats design/Picasso TUI.html as the locked TUI visual source of truth"

/memory add this repo treats design/Picasso TUI.html as the locked TUI visual source of truth

First memory query

what do you remember about the TUI visual source of truth?

Expected result:

• The memory retrieval pipeline searches only the current account/project namespace.
• Matching memory appears as injected context.
• The assistant answer cites the remembered fact rather than rediscovering it.

CLI inspection

picasso memory list
picasso memory inspect <memory-id>
picasso memory pin <memory-id>
picasso memory sync

picasso memory sync sends encrypted memory in size-capped batches and needs a signed-in account. If a sync was interrupted and its cursor lock is stuck, stop Picasso on every machine, then run:

picasso memory recover-sync-lock

Privacy behavior

• Memory entries are scoped by account and project.
• Cross-account retrieval is blocked.
• Deleted memory is excluded from retrieval.
• Pinned memory is protected from eviction.