Memories - memloom docs

save

memloom save "the staging database runs on Postgres"
memloom save --type procedure "to release: bump VERSION, tag, push"

With a key configured the belief pipeline runs: a duplicate merges, a rewording versions, and a contradiction keeps both memories active and reports a conflict id.

Type	Holds	Example
`fact`	A stable truth	the staging DB runs on Postgres
`preference`	How you like things done	prefers pnpm over npm
`episode`	A time-bound event	shipped the viewer on 2026-07-05
`procedure`	Reusable steps	to release: bump, tag, push

Outcomes are added, merged, versioned or conflict.

A conflict is not an error. Both memories stay active until you settle it. See Conflicts.

recall

memloom recall "staging database"
memloom recall "ECONNREFUSED 54329"     # exact identifiers work well

Searches memories and ingested files together, by meaning, exact words and entities, fused into one ranking. Results from files carry their source. Only active memories come back; superseded versions live in history. See Retrieval.

update, history

memloom update <memory-id> "the corrected text"
memloom history <memory-id>

update writes a new version and leaves the old one in history. history prints the whole chain newest first, with * on the current version. Any version’s id works, so an id from an old note still finds the chain.