Last updated: 2026-09-06
orca memory inspects agent memories and the memory bank that spans every profile in the tenant. Memories are written by agents as they run (or extracted in the dashboard), so the CLI is read, search, and delete only; there is no create or update.
Every subcommand accepts the global flags. delete prompts for confirmation in a terminal; in a script --yes is required or the command refuses (exit code 2).
orca memory list
--all, and neither flag has a CLI default. When omitted they are not sent and the server pages with its own values.
When the server holds more memories than the page returned, the terminal view prints a
Showing X of Y hint on stderr.
id, category, source, confidence, createdAt, summary. The --json output is the array of memory records only, without the page totals.
orca memory search
id, score, category, summary. The --json output is the array of scored results; each has memory (the full record) and relevance (score, recency, usage, topic).
orca memory show
field, value row per field: id, profile, category, source, confidence, staleness, accessCount, isActive, version, createdAt, lastAccessedAt, summary, processedContent. With --json the full memory record is printed.
orca memory delete
orca memory bank
--json the snapshot is printed as the server returns it: total, profilesWithMemory, and memories, a map from profile name to that profile’s memory records.
profile, id, category, summary, createdAt.
orca memory bank stats
profile, count row per profile. The --json output is the stats record: totalMemories, profilesWithMemory, and perProfile, a map from profile name to count.
Verified against orca-cli
cli-v0.5.0.