The command desk
Enter these slash commands inside OMP. Nothing on this website executes them.
| Command | Meaning and limits |
|---|---|
/memory view | Shows the injected payload: instructions plus cached recalled text, not the whole database or a fresh search. |
/memory stats | Shows scoped bank counts, working/episodic memory, triples and database locations. Use it to understand scope. |
/memory diagnose | Inspects scoped database diagnostics and integrity findings. Does not establish provider authentication or embedding availability. |
/memory enqueue | Mutates memory. Alias: /memory rebuild. Retains the remainder, flushes extraction and requests full, age-gated cross-session consolidation—not an index-only rebuild. An “enqueued” banner is not proof of success; check diagnostics and recall afterward. |
Destructive warning: clear is a wipe, not a refresh
/memory clear and /memory reset delete all currently scoped database files and sidecars, including rescued legacy banks and shared/base databases when present—even beyond ordinary per-project recall. The controller described in this snapshot has no confirmation. Inspect scope and backups first. Removal can fail; a success banner does not prove erasure.
/memory mm is Hindsight-only, not a Mnemopi command workflow.
Optional configuration changes—not applied by this tutorial
Use your shell, not OMP’s prompt. Read a value first:
omp config get mnemopi.autoRetain --json
Choose individual changes deliberately; this is not a script to run wholesale.
| Goal | Shell command | Caveat |
|---|---|---|
| Pause periodic retention only | omp config set mnemopi.autoRetain false | Not a complete privacy switch; other save paths remain. |
| Skip extra capture turns | omp config set autolearn.autoContinue false | Standing auto-learn guidance remains. |
| Disable the active memory backend | omp config set memory.backend off | Does not delete existing data. |
| Disable auto-learn separately | omp config set autolearn.enabled false | Also disables its generated-skill tools on fresh startup. |
Read back changed keys with omp config get and --json. Start a fresh OMP session after changes affecting startup tools or the backend.
Memory and reusable knowledge · Source chapter: memory/the-command-desk. Original evidence remains scoped to its recorded snapshot.