> ## 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 detect-conflicts

> Run the LLM conflict-detection pass over a day's session memories and write the report.

# memanto detect-conflicts

Runs the LLM conflict-detection pass over the day's session memories and writes the JSON report to `~/.memanto/conflicts/`. This is the same work the [schedule](/cli/schedule/enable) job performs. Resolve the detected conflicts interactively with [`memanto conflicts`](/cli/ai/conflicts).

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

**Options:**

* `-d, --date TEXT` - Date in `YYYY-MM-DD` format (defaults to today)
* `-a, --agent TEXT` - Agent identifier (defaults to active agent)

**Examples:**

Detect conflicts for the active agent, today:

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

Detect conflicts for a specific agent and date:

```bash theme={null}
memanto detect-conflicts --agent customer-support --date 2026-05-08
```

**Output:**

```
Conflict report generated: ~/.memanto/conflicts/customer-support_2026-05-08_conflicts.json
  ! 2 conflict(s) detected
  Run 'memanto conflicts' to resolve interactively
Completed in 2.11s
```

If no session data exists for the date, the command reports `No sessions found for conflict detection.` instead.

**Notes:**

* Requires an active agent, or pass `--agent` explicitly.
* This command only detects and reports conflicts — it does not resolve them. Use [`memanto conflicts`](/cli/ai/conflicts) to resolve.
* Backed by the [Generate Conflict Report](/api-reference/data/generate-conflicts) API endpoint.