nrepo rm

nrepo rm <id> [options]

Archives an idea. The row stays in the database, but the idea disappears from every NeuralRepo surface.

Options

Flag	Type	Default	Description
--force	boolean	false	Suppress the preview block.
--json	boolean	false	Output as JSON.
--human	boolean	—	Force human-readable output. Wins over --json.

Danger

There is no confirmation prompt, and nothing in NeuralRepo can un-archive an idea. --force only hides the preview text; the archive happens either way, immediately. No API endpoint, CLI command, or web control restores an archived idea — recovering one means a manual database operation by NeuralRepo support, and the idea’s search embedding is deleted on archive, so it would come back unsearchable until re-indexed.

If you only want an idea out of the way, nrepo move <id> shelved hides it from your working views while leaving it listable, searchable, and reversible.

Output

nrepo rm 391

Archive preview:
  #42 "Rewrite auth flow" [exploring]

  The idea will be archived (soft-deleted).

✓ Archived #42 "Rewrite auth flow"

nrepo rm 391 --force --json

{ "success": true, "archived": 391 }

archived echoes the ID you passed, not the display number.

What archiving changes

Surface	Effect
nrepo log, nrepo status	Gone from listings and from every status count
nrepo search	Gone — the vector is deleted from the search index on archive
Relations	Relations to and from it are filtered out of nrepo links, nrepo graph, and the mind map
nrepo show <id>	Still returns the idea, because it is fetched by ID directly
Free-plan idea cap	Frees a slot — the 50-idea cap counts unarchived ideas only

Next Steps

nrepo move Shelve an idea instead — hidden from your working views, and reversible.

Status Workflow Where shelved sits among the five statuses, and when to use it.

nrepo merge Fold a redundant idea into another rather than discarding it.

nrepo pull Export an idea to local files before archiving it.