resolve_conflict
Keep both memories, replace one, or discard the new one
How to use it
Project documentation lists resolve_conflict for the Menhir MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
FULL MENHIR LISTINGOther tools in Menhir (28)
Stage low-trust context for human review without making it recallable
Queue a memory for enrichment
Queue a memory and stream processing progress
Create a todo with an optional normalized code location
Assemble context within a token budget
Delete a memory under operator control
Protect a memory from normal lifecycle decay
Read one artifact with its current metadata and Git-backed content
Inspect one episode's processing state
Read queue and telemetry history for an episode
Summarize latency, failures, and queue depth
Expand a result into source episodes, evidence, and code anchors
Ingest a document as memory episodes
Index a repository's structure
Record a typed reviews, implements, or informs relationship
Find plans, reviews, investigations, reports, and handoffs by type or status
List grouped contradictions
Mark persistent memory as operator-verified ground truth
Query code context, blast radius, affected tests, symbols, endpoints, dependencies, and cross-project references
Record explicit retrieval feedback
Read memories selected for bootstrap
Retrieve recent and relevant startup context
Search and rerank memories, with optional file context
Ask the configured LLM to review unresolved conflicts
Scan for similarity-based conflict candidates
Replace an artifact while updating status and relationship atomically
Apply a legal status transition for that artifact type
Monitor enrichment changes