Skip to content
NeuralRepo
Get Support

Core Concepts

NeuralRepo is built around a few core concepts. Understanding them will help you get the most out of the platform.

An idea is the atomic unit in NeuralRepo. Every idea has:

FieldDescription
TitleA short, descriptive name (required)
BodyLonger description or notes in Markdown (optional)
StatusCurrent stage in your workflow
SourceWhere the idea was captured from
TagsUser-defined labels for categorization
RelationsConnections to other ideas
LinksExternal URLs and references

Ideas are designed to be lightweight. Capture first, organize later.

Every idea is in exactly one of five statuses. The usual path runs left to right, but nothing enforces the order — any status can move to any other status.

captured → exploring → building → shipped
(any status) ⇄ shelved
StatusMeaning
capturedJust recorded — hasn’t been evaluated yet
exploringActively thinking about or researching this idea
buildingImplementation is underway
shippedThe idea has been realized and delivered
shelvedParked for later — not abandoned, just not active

The web dashboard provides a kanban board view where you can drag and drop ideas between status columns.

The source field records where an idea was originally captured. It is set automatically and cannot be changed after creation.

SourceOrigin
webCreated in the web dashboard
cliCreated via the nrepo CLI
claude-mcpCreated by Claude AI through MCP
siriCreated via Siri Shortcuts
emailCreated by sending an email to idea@neuralrepo.com
apiCreated via the REST API directly, and by the AI agent’s own tools
shortcutCreated via an Apple Shortcut (non-Siri)
iosCreated in the native NeuralRepo iOS app

Sources are useful for filtering and understanding your capture habits. You can filter by source in the web dashboard and in the API. A source is chosen by the client that creates the idea, so a REST API caller may set any of these values on itself.

Tags are user-defined labels that help you categorize and filter ideas. They are flexible and freeform — use whatever taxonomy makes sense for you.

  • Lowercase, hyphenated names are the convention (side-project, not Side Project)
  • Each idea can have up to 20 tags, each up to 50 characters
  • An idea saved with no tags is auto-tagged in the background — with AI on Pro, by borrowing tags from its nearest neighbours on the free plan
  • Filter by tags in the web dashboard, CLI, and API

Example tags: side-project, ai, mobile, revenue, devtools, ux-improvement

Relations create typed, directional connections between ideas. Every relation has a source idea, a target idea, and a type.

TypeMeaningExample
relatedGeneral association”Auth service” ↔ “OAuth provider research”
parentHierarchical grouping”Mobile app” → “Push notifications feature”
blocksDependency”Design system” blocks “Dashboard redesign”
inspiresOne idea led to another”Competitor analysis” inspires “Freemium pricing model”
duplicateSame idea captured twiceAuto-detected or manually set
supersedesReplaces an older idea”Auth v2” supersedes “Auth v1”

Relations are directional — the source and target matter. For example, “A blocks B” means A must be completed before B can proceed. The related type is the exception; it is treated as bidirectional.

Some relations are created for you: related links come from similarity scoring, and giving an idea a parent_id creates a parent relation. Creating relations by hand — in the web app, the CLI, the API, or MCP — requires Pro; free accounts see the graph read-only.

Links attach external resources to an idea. Each link has a type and a URL.

TypeUse Case
urlAny web URL — articles, docs, references
claude-chatLink to a Claude conversation that relates to the idea
github-repoLink to a GitHub repository
github-issueLink to a specific GitHub issue or PR

An idea can have multiple links. Links help bridge the gap between ideation and execution — connect your idea to the code, conversation, or research that supports it.

Links are URLs only — every link type stores an address, not a file. (The API also accepts a fifth type, attachment, but nothing in the product uploads files today.)

NeuralRepo uses vector similarity to detect potential duplicates. Detection is asynchronous — it runs after the idea is saved, never before:

  1. Saving an idea queues it; the queue worker generates a vector embedding of title and body
  2. The embedding is compared against your five nearest ideas, skipping shelved ones
  3. A match above the dedup threshold (default 0.75) records a pending duplicate detection
  4. You resolve it by merging or dismissing, from the Duplicates or Review view, the CLI, or the API

Duplicate detection is a Pro feature, but it runs for everyone: detections are recorded in the background on the free plan and simply not shown, so they are all waiting for you the moment you upgrade. Marking two ideas as duplicates by hand needs Pro too, because it means creating a relation.

The idea graph is the network formed by all your ideas and their relations. NeuralRepo visualizes this as an interactive mind map in the web dashboard.

The mind map lets you:

  • See clusters of related ideas at a glance
  • Discover hidden connections between projects
  • Identify blocking dependencies
  • Navigate between ideas by clicking nodes

The mind map lives in the web dashboard under the Mind Map tab. Free-tier users get view-only access; editing the graph (dragging, linking, status changes) and the AI agent require Pro.

The AI agent is a conversational assistant built into the web app. You can ask it to search your ideas, create new ones, discover connections, brainstorm variations, summarize clusters, score ideas, and draft documents — all in natural language.

The agent is available in two places:

  • Agent — a full split-pane view with a chat panel and an artifact canvas
  • Mind Map chat panel — a floating overlay on the mind map where tool results animate directly onto the graph

The agent supports five models: Anthropic’s Sonnet, Haiku, and Opus via BYOK, plus two Workers AI models — GPT-OSS 120B (the default) and Qwen 30B — that need no API key.

See the AI Agent section for complete documentation.

Start Capturing

Now that you understand the concepts, head to the Quick Start to begin capturing ideas.

Explore the API

Build custom integrations using the REST API with full access to ideas, relations, and links.