Skip to content

Manage what Quox remembers

Documented Checked against the CLI's current help and source. Not run end to end. CLI 0.3.1, checked 2026-11-04.

Can I see and change what it remembers?

Save a fact your agents can use, find it by a word, correct it, export the lot, and forget one when it no longer holds.

What you get: a memory you control. The facts your agents work from are yours to read, correct and remove. You need: a signed-in profile. About 4 minutes.

stats
quox memory statsMemory Stats (org): 13 valid memories, 2 superseded or deleted (kept for history), 0 pinned, last write 2026-11-04 21:30:10By type: fact 1, observation 12Agent        Memoriesquoxdream    9(none)       4Writer                        Kind       Memories    Agents01M50FWMYCH96ES7AAEVT0TR31    user       8           quoxdreamservice                       service    3system                        system     2           quoxdreamValid = not deleted and not superseded. A writer is the login a memory was saved under: your own, an agent identity, service/system (internal agents), or org-shared beliefs.
From a real run on the demo profile.

The stats split your memories by type, by the agent that uses them, and by who wrote them. Deleted and replaced memories are kept for history, and counted separately.

create
quox memory create --type fact --content "The north region van is serviced every March" --tags fleet,vansMemory saved.
From a real run on the demo profile.

The type is one of fact, preference, decision, entity or observation. Add --agent <agentId> to give the memory to one agent.

search
quox memory search vanID                            Type    Content                                         Score01M6MDAY3ZEP41FX6JH6SGW4YM    fact    The north region van is serviced every March    -
From a real run on the demo profile.

--type fact narrows the search to one type, and --limit sets how many come back.

get and update
quox memory get 01M6MDAY3ZEP41FX6JH6SGW4YMid                       01M6MDAY3ZEP41FX6JH6SGW4YMmemory_type              factcontent                  The north region van is serviced every Marchimportance               mediumtags                     fleet, vansvalid                    yescreated_at               2026-11-04 23:12:04updated_at               2026-11-04 23:12:04quox memory update 01M6MDAY3ZEP41FX6JH6SGW4YM --content "The north region van is serviced every March and every September"Memory updated.quox memory get 01M6MDAY3ZEP41FX6JH6SGW4YMid                       01M6MDAY3ZEP41FX6JH6SGW4YMmemory_type              factcontent                  The north region van is serviced every March and every Se...importance               mediumtags                     fleet, vansvalid                    yescreated_at               2026-11-04 23:12:04updated_at               2026-11-04 23:12:16
From a real run on the demo profile. Some fields left out.

The memory keeps its id, so anything that already points at it now reads the corrected text. The table view shortens long content; add --json to read it in full. --tags replaces the tags in the same way.

export
quox memory export > memories.jsonjq '{memories: (.memories|length), entities: (.entities|length), core_memories: (.core_memories|length)}' memories.json{"memories": 9,"entities": 0,"core_memories": 0}
From a real run on the demo profile.

The export is one JSON file of the memories you wrote, with the entities and core memories alongside, ready to keep or to read in another tool.

forget
quox memory forget 01M6MDAY3ZEP41FX6JH6SGW4YM --yesForgot memory 01M6MDAY3ZEP41FX6JH6SGW4YM.quox memory search vanNo results.quox memory statsMemory Stats (org): 13 valid memories, 3 superseded or deleted (kept for history), 0 pinned, last write 2026-11-04 23:12:04
From a real run on the demo profile.

Forgetting is a soft delete: the memory stops being used and stops turning up in searches, and the stats count it under “superseded or deleted”. It refuses to run without --yes.

Every step read or changed one memory in your organisation’s memory store, the store your agents work from. Each step ran straight away, with no approval to wait for.

Run quox memory search van after each step. The memory appears after step 2 and is gone after step 6. quox memory get <id> --json shows the corrected text in full after step 4.

A forgotten memory is kept for history. quox memory forget <id> --permanent --yes erases one for good instead, and that cannot be undone.