nrepo duplicate

nrepo duplicate list [options]
nrepo duplicate dismiss <id> [options]
nrepo duplicate merge <id> [options]

NeuralRepo compares every new idea against your existing ones a few seconds after capture and records a detection for each near-identical pair. These three subcommands work through that queue.

Subcommand	What it does
list	Show unresolved detections
dismiss <id>	Mark a detection resolved without changing either idea
merge <id>	Fold the pair together and resolve the detection

All three take --json and --human.

Caution

Duplicate detection is a Pro feature. On the free plan the endpoint returns an empty list, so nrepo duplicate list always prints No pending duplicates. Detections are still being recorded in the background, and the backlog appears in full the moment you upgrade.

Listing detections

nrepo duplicate list

2 pending duplicates

  #101 Auth flow redesign ≈ #42 Rewrite auth flow 91%
  #103 Dark mode support ≈ #40 Add dark mode to dashboard 85%

  Use `nrepo duplicate dismiss <id>` or `nrepo duplicate merge <id>` to resolve.

Caution

The <id> those two commands want is the detection’s ID, and the human output does not print it — #101 and #42 are idea display numbers. Use --json to get it:

nrepo duplicate list --json | jq -r '.duplicates[] | "\(.id)  #\(.idea_number) ≈ #\(.duplicate_number)  \(.similarity_score)"'

The JSON form carries both ideas in full — numbers, titles, statuses, sources, creation dates, and the first 280 characters of each body — which is enough to decide without a second lookup:

{
  "duplicates": [
    {
      "id": 17,
      "idea_id": 512,
      "duplicate_of_id": 391,
      "similarity_score": 0.91,
      "status": "pending",
      "idea_number": 101,
      "idea_title": "Auth flow redesign",
      "duplicate_number": 42,
      "duplicate_title": "Rewrite auth flow"
    }
  ]
}

The human list shows only pending detections; --json returns what the API sent, which is also pending-only.

Dismissing

nrepo duplicate dismiss 17
# ✓ Dismissed duplicate #17

Marks the detection resolved. Neither idea changes, and the pair is not flagged again. A detection that does not exist, or has already been resolved, returns API error (404): Duplicate not found or already resolved.

Merging

nrepo duplicate merge 17
# ✓ Merged duplicate #17 into primary idea

Caution

This is not the same operation as nrepo merge, and the difference decides which idea survives.

	nrepo duplicate merge	nrepo merge <keep> <absorb>
Idea kept	The newer one — the capture that triggered the detection	Whichever you name first
Idea archived	The older one it matched	The one you name second
Body	Newer body, ---, older body	Kept body, ---, absorbed body
Tags	Union	Union
Relations	Not transferred — they stay on the archived idea and become invisible	Transferred to the kept idea
Status of archived idea	Unchanged, but archived	Set to shelved, and archived

If the older idea is the one carrying your relations, merge it explicitly with nrepo merge instead, then dismiss the detection.

Both paths keep the earlier of the two creation dates on the surviving idea, and neither can be undone.

Next Steps

Duplicate Detection What the detector compares, the score threshold, and what it does with the pair.

nrepo merge Merge two ideas you chose yourself, with relation transfer.

Review Queue The web app's version of this queue, with connections and stale ideas too.

nrepo diff Compare the two ideas in a detection before you resolve it.