Skip to main content

​
memanto detect-conflicts

Runs the LLM conflict-detection pass over the day’s session memories and writes the JSON report to the conflicts/ directory under the active backend’s data directory — ~/.memanto/conflicts/ on the cloud backend, ~/.memanto/on-prem/conflicts/ when on-prem is selected. This is the same work the schedule job performs. Resolve the detected conflicts interactively with memanto conflicts.
Options:
  • -d, --date TEXT - Date in YYYY-MM-DD format (defaults to today, UTC)
  • -a, --agent TEXT - Agent identifier (defaults to active agent)
Examples: Detect conflicts for the active agent, today:
Detect conflicts for a specific agent and date:
Output: While the pass runs, a live status line reports the current phase (Starting conflict detection (run …), Loading session memories…, Waiting for Moorche run … (processing)), then the result is printed:
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 to resolve.
  • The report directory follows the active backend, so switching backends with memanto backend changes where reports are written and read from.
  • The Moorche run: line appears only when the backend reports a run id for the detection pass.
  • Backed by the Generate Conflict Report API endpoint.