> ## 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.

# Auto-resolve pending conflicts with an LLM judge (NDJSON stream)

> What `memloom conflicts auto` calls. Re-judges every pending conflict with context
the dedup classifier never had: when each side was recorded and, for memories
distilled from a Claude Code import, the transcript excerpt behind it. Only a
decisive verdict resolves anything (`keep_new`, `keep_existing`, or `keep_both`,
applied through the same `resolveConflict` path as the manual endpoint above, so it's
just as revertable); `unsure` leaves the conflict pending. Streams NDJSON: one
`{"type":"item"}` event per examined conflict, then a final `{"type":"done"}` event
with the totals. Needs the LLM; unavailable in offline mode.




## OpenAPI

````yaml /openapi.yaml post /memory/conflicts/resolve-auto/stream
openapi: 3.1.0
info:
  title: memloom local API
  version: 0.1.0
  description: >
    The HTTP API served by the `memloom serve` daemon on your machine. The CLI,
    the MCP server,

    and the viewer all route through this API. The daemon is the single owner of
    the store, so

    every client shares one consistent view of your memories.


    No authentication: the daemon binds to `127.0.0.1` only and is reachable
    solely from your

    own machine. Browser clients on other localhost ports are allowed via CORS.
servers:
  - url: http://127.0.0.1:4319
    description: Local memloom daemon
security: []
paths:
  /memory/conflicts/resolve-auto/stream:
    post:
      summary: Auto-resolve pending conflicts with an LLM judge (NDJSON stream)
      description: >
        What `memloom conflicts auto` calls. Re-judges every pending conflict
        with context

        the dedup classifier never had: when each side was recorded and, for
        memories

        distilled from a Claude Code import, the transcript excerpt behind it.
        Only a

        decisive verdict resolves anything (`keep_new`, `keep_existing`, or
        `keep_both`,

        applied through the same `resolveConflict` path as the manual endpoint
        above, so it's

        just as revertable); `unsure` leaves the conflict pending. Streams
        NDJSON: one

        `{"type":"item"}` event per examined conflict, then a final
        `{"type":"done"}` event

        with the totals. Needs the LLM; unavailable in offline mode.
      operationId: autoResolveConflictsStream
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: NDJSON progress stream ending with a done (or error) event.
          content:
            application/x-ndjson:
              schema:
                type: string
                example: >
                  {"type":"item","conflictId":"...","index":1,"total":3,"verdict":"keep_new","reason":"the
                  newer session shows the change","content":"the deploy target
                  is railway"}

                  {"type":"done","examined":3,"resolved":2,"keepNew":1,"keepExisting":0,"keepBoth":1,"unsure":1}

````