nrepo pull
nrepo pull <id> [options]Writes an idea and its context into a directory as Markdown — the usual way to hand an idea to a coding agent or an editor.
Options
Section titled “Options”| Flag | Type | Default | Description |
|---|---|---|---|
--to <dir> | string | . | Output directory. Created if it does not exist. |
--json | boolean | false | Print the idea as JSON and write no files. |
--human | boolean | — | Force human-readable output. Wins over --json. |
Examples
Section titled “Examples”nrepo pull 391# ✓ Pulled #42 to /Users/you/work/# IDEA.md, CONTEXT.md, .neuralrepo
nrepo pull 391 --to ./ideas/auth-rewrite
# Just the body, no files writtennrepo pull 391 --json | jq -r '.body'What gets written
Section titled “What gets written”| File | Written when | Contents |
|---|---|---|
IDEA.md | Always | Title as an h1, then status, source, creation date, tags, and source URL as bold fields, a --- rule, and the body. An idea with no body gets _No body_. |
CONTEXT.md | The idea has relations | One bullet per related idea: relation type, title, and similarity score where there is one. |
RELATED.md | The idea has attached URLs | One Markdown link per attachment. |
.neuralrepo | Always | JSON: idea_id, api_url, and pulled_at. |
There is no push back
Section titled “There is no push back”Despite the name, nrepo pull and nrepo push are not two halves of a sync — push creates a
new idea, and pull exports an existing one.
Working with an agent
Section titled “Working with an agent”mkdir -p /tmp/idea && nrepo pull 391 --to /tmp/ideaclaude "Read /tmp/idea/IDEA.md and CONTEXT.md, then draft an implementation plan"The Claude Code skill bundled with the CLI does this for you — see Claude Code.
Next Steps
Section titled “Next Steps” nrepo show The same content in the terminal, without touching the filesystem.
nrepo edit Send an edited body back to the server.
Idea to Project The full workflow from a captured idea to a working implementation.
Claude Code Let the bundled skill drive pull, search, and push for you.