Conflicts - memloom docs

conflicts

memloom conflicts

Lists pending contradictions: the new memory and the existing ones it clashes with. Both stay active until settled. Resolving by hand lives where a human is: the viewer’s Conflicts tab, or an agent relaying your choice through resolve_conflict. The four actions are keep new, keep existing, keep both, and merge. Every resolution is reversible.

conflicts auto

memloom conflicts auto

Re-judges every pending conflict, one call each. The classifier that filed them saw two isolated pieces of text; this adds what it could not see: when each memory was recorded, and for imported ones the transcript excerpt it came from.

[1/3] keep new: the deploy target is railway  (the newer session shows the change)
[2/3] left for you: staging runs on Postgres  (times are too close)
[3/3] keep both: prefers pnpm here, npm in the legacy repo  (different scopes)
resolved 2 of 3; 1 left for you

Only a decisive verdict resolves anything. The model is told to answer unsure rather than guess, and an unsure conflict stays exactly as it was. Resolutions land in the same revertable history as manual ones, so this is safe to re-run over a growing queue.

Needs a model, so it is unavailable offline. How detection works and what each resolution does to the version chain is in Conflicts.