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

# memanto conflicts

> Interactively resolve memory conflicts detected for an agent.

# memanto conflicts

Reads the conflict report generated by [`memanto detect-conflicts`](/cli/ai/detect-conflicts) and walks through each unresolved conflict, letting you choose how to resolve it.

```bash theme={null}
memanto conflicts [OPTIONS]
```

**Options:**

* `-d, --date TEXT` - Date in `YYYY-MM-DD` format (defaults to today, UTC)
* `-a, --agent TEXT` - Agent identifier (defaults to active agent)
* `-l, --list` - List conflicts without interactive resolution

**Examples:**

Resolve today's conflicts interactively:

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

List conflicts for a specific date without resolving:

```bash theme={null}
memanto conflicts --date 2026-03-01 --list
```

Specific agent:

```bash theme={null}
memanto conflicts --agent customer-support
```

**Interactive Flow:**

For each unresolved conflict, Memanto shows both memories side by side with an AI recommendation, then prompts for an action:

```
Conflict 1/2
[CONTRADICTION]  Database preference changed

Memory A (old):  ID: abc-123 · 2026-05-01
  Customer is in finance team

Memory B (new):  ID: def-456 · 2026-05-08
  Customer moved to marketing team

AI Recommendation:  Keep B (new)

Delete the loser (permanent):
[1] Keep A (old memory) — deletes B
[2] Keep B (new memory) — deletes A  << recommended
[3] Keep both
[4] Remove both
Expire the loser (reversible):
[5] Expire A (old memory)
[6] Expire B (new memory)
[7] Expire both
[8] Manual: type replacement
[s] Skip  [q] Quit

Choose: 5
  OK Expired A (old). Restore it any time.
```

The menu is split deliberately. Options **1–4** and **8** delete the losing memory
permanently. Options **5–7** retire it instead: the content is kept, it stays
recallable labelled `[EXPIRED]`, and it is stamped
`expired_by: conflict-resolution` so the audit trail shows a conflict retired it.
Undo one with [`memanto memory restore`](/cli/data/restore).

See [Memory Lifecycle](/reference/memory-lifecycle) for the full model.

After any conflicts are resolved, the local `memory.md` cache is automatically re-synced.

**Notes:**

* Requires a conflict report to already exist for the date — run `memanto detect-conflicts` first (or enable `memanto schedule enable`, which runs both automatically).
* Interactive resolution requires an active agent session. `--list` mode does not.
* Backed by the [List Conflicts](/api-reference/data/list-conflicts) and [Resolve Conflict](/api-reference/data/resolve-conflicts) API endpoints.