nrepo edit

nrepo edit <id> [options]

Updates the title, the body, or both. Anything you do not pass is left alone.

Options

Flag	Type	Default	Description
`--title <title>`	string	(unchanged)	New title. Max 200 characters.
`--body <body>`	string	(unchanged)	New body. Max 50,000 characters.
`--json`	boolean	`false`	Output the updated idea as JSON.
`--human`	boolean	—	Force human-readable output. Wins over `--json`.

nrepo edit only touches those two fields. Status is nrepo move, tags are nrepo tag.

Examples

# Retitle
nrepo edit 391 --title "Add dark mode and a theme picker"

# Replace the body from a file
nrepo edit 391 --body "$(cat notes.md)"

# Both at once
nrepo edit 391 \
  --title "Theme system v2" \
  --body "Complete redesign of the theming layer with dark mode support."

Passing neither flag is an error, and nothing is sent:

Nothing to update. Use --title or --body.

With --json the same case prints {"error":"Nothing to update. Use --title or --body.","code":"no_input"}. Both exit with status 1.

Output

✓ Updated #42
  Title: Theme system v2
  Body updated (312 chars)

Only the fields you changed are echoed. --json prints the full updated idea object.

What happens afterwards

Editing a title or body re-queues the idea for embedding, so its semantic search results and duplicate detections refresh a few seconds later. Until that finishes, nrepo search still matches the old wording.

Next Steps

nrepo show Read the current title and body before you overwrite them.

nrepo branch Keep the original and explore a variant instead of editing in place.

nrepo move Change status — the field nrepo edit deliberately does not touch.

Queue Processing What the background pass does with an idea after you change its text.