> ## Documentation Index
> Fetch the complete documentation index at: https://docs.memloom.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Conflicts

> conflicts: listing pending contradictions, or auto-resolving them with an LLM judge

## conflicts

```bash theme={null}
memloom conflicts
```

List pending contradictions: the new memory and the existing ones it clashes with. A
conflict appears when a save contradicts something already stored; both memories stay
active until resolved.

Resolving by hand lives where a human is: the viewer's Conflicts tab, or an MCP client
relaying your choice via [`resolve_conflict`](/mcp/tools#resolve_conflict). The four actions
are keep new, keep existing, keep both, and merge; every resolution is reversible.

## conflicts auto

```bash theme={null}
memloom conflicts auto
```

Re-judges every pending conflict with an LLM, one call per conflict. The dedup classifier
that filed each conflict only ever saw two isolated pieces of text; the auto-resolver adds
what it couldn't see, when each memory was recorded, and, for memories that came from
`import sessions`, the transcript excerpt it was distilled from. A later session
recording a state change against an older fact usually resolves the way a human skimming
both would resolve it.

```
[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 in this repo, npm in the legacy one  (different scopes)
resolved 2 of 3: 1 keep new, 0 keep existing, 1 keep both; 1 left for you
every auto-resolution is revertable from the viewer's conflicts tab.
```

Only a decisive verdict resolves anything. The model is instructed to answer **unsure**
rather than guess, and an unsure conflict stays in the queue exactly as it was. A resolved
one lands in the same revertable history as a resolution made by hand, so `conflicts auto`
is safe to run repeatedly over a growing queue.

<Note>
  Auto-resolution needs the LLM, so it's unavailable in offline mode (no
  `OPENROUTER_API_KEY`).
</Note>

How contradiction detection works, and what each resolution does to the version chain, is
covered in [Conflicts](/concepts/conflicts).