Context Editor and Search

The Context Editor is where you maintain the spec map: the set of context nodes that connected agents read to learn what your project should be. Search finds text across your projects, phases (stages of work), tickets (units of work inside a phase), and context nodes, and opens the matching item.

Where to find it

• Context Editor is item 6 in the sidebar. Press Ctrl+6.
• Search is the last item in the sidebar. Press Ctrl+/ or Ctrl+K.

Panel shortcuts do nothing while the cursor is in a text field or editor.

What a context node is

A context node is one entry in the spec map: a piece of guidance an agent should know, such as a feature spec, a rule, or a reference document. The spec map is the full set of active nodes for a project.

Agents also see a summary (the first non-empty line, cut at 120 characters) and a token estimate (content length in characters divided by 4).

Where nodes come from

• Project import. Items you approve during import become nodes. Items in the specification category become spec nodes. Every other category, including architecture docs, becomes a standard node, except tech stack items, which merge into the project's tech stack.
• The Spec Editor. The project description, goal, tech stack, and non-goals each become a spec node, and each constraint becomes a rule node. Vibeless keeps these in step with the Spec Editor.
• This panel. You add nodes by hand with Add Node.

Nothing is added to the map automatically from file changes. The file watcher and git monitor see new files, but no file becomes a node until a person adds it in the app. The map describes what the project should be, so an agent must not be able to change it by writing files.

What you see

• Header. A type filter (All types, rule, spec, standard) and Add Node.
• Node list. Nodes grouped under Project, Domain, and Feature, with counts. Each row shows the active switch, name, type badge, scope name badge, and a one-line content preview. The pencil icon edits the node; the trash icon deletes it.
• Edges card. On the right, showing the links for the selected node.
• Scope Suggestions card. Appears below the node list when a project node's file mapping points at one specific area of the code, and proposes a tighter scope.
• File Mappings card. Each row ties a glob pattern (such as src/auth/**/*.ts) to a node, telling Vibeless which files that node governs.

How to use it

Add or edit a node

1. Select Add Node, or the pencil icon on a row.
2. Fill in Name, Type, Scope Level, Scope Name, and Content.
3. Select Create Node (or Save Changes).

A name is required. For the rule type, the form notes that rule nodes reach your agent's context but do not yet drive the watcher's drift classification. Drift is a gap between what the project record says and what the code does.

The VC button at the top of the sheet opens VC Copilot, an assistant that reads your draft. It is an LLM feature, so it needs a paid plan and uses credits.

Map files to a node

1. In File Mappings, type a glob pattern.
2. Pick the node from Select node.
3. Select the plus button.

Mappings decide which code an agent is pointed to for a node, and they feed automatic edges.

Scope suggestions, switching off, and deleting

Each scope suggestion shows the node, its glob, a proposed level, and a proposed name. Adjust them, then select Apply or Dismiss. Dismissed suggestions return the next time you open the panel.

Use a node's switch to hide it from agents without losing it. The trash icon deletes a node at once, with no confirmation prompt.

Edges

An edge is a link between two nodes. Agents use edges to find related guidance, and Vibeless uses them to rank suggestions. Select a node to see its edges.

To add an edge, type the target node's ID in Target node ID, pick a relationship, and select the plus button. The edge list identifies the other node by its ID, not its name.

Vibeless also derives edges itself, without an LLM. These show an auto badge with a confidence percentage, and are created at 60% confidence or more. The evidence comes from 3 checks:

• Code in one node's mapped files imports code in another node's mapped files (depends_on).
• One node's content mentions another node's name or scope (depends_on).
• Two nodes' file mappings cover overlapping files (related_to).

Automatic edges only link nodes that already exist and never change a node. Edges you create by hand are left alone.

When the evidence for an automatic edge disappears, Vibeless lists it under Pending edge removals instead of deleting it. Select Accept to remove it or Reject to keep it. Re-derive runs the check now and reports how many edges were added, refreshed, and proposed for removal. If you delete an automatic edge by hand while its evidence still holds, the next run adds it back.

Search

1. Open Search and type at least 2 characters.
2. Results appear grouped by type, each with its name and a short excerpt around the match.
3. Select a result to open it.

Search covers projects (their spec fields), phases, tickets, and context nodes. A multi-word query matches items containing any of the words. Ranking uses BM25, a standard relevance score, so items with more of your words, or rarer ones, rank higher. Word forms match, so "running" finds "run". Search shows at most 20 results; refine the query if you need more.

A project result opens the Spec Editor. A phase opens the Phase Planner with that phase selected. A ticket opens Tickets with that ticket selected. A context node opens the Context Editor.

Search in the app covers every project stored on this computer. Selecting a result does not switch the open project.

How it connects to agents

Agents never receive the whole map's content at once. They get an index, then open what they need.

• vibeless_declare_intent. The agent states what it is working on. Vibeless returns the project map, up to 5 suggested starting points, and a freshness check. The map lists every active node with name, type, scope level, summary, and token estimate. Above 150 visible nodes, the map lists only node counts per type and scope level instead of each node. Suggestions are ranked by text match with the description, whether the node is linked to an open ticket, recency, and scope specificity; nodes linked by depends_on or related_to edges inherit part of the score. Code from the topology whose files match a suggested node's file mappings is listed too. The map is authoritative; suggestions are guesses.
• Freshness warning. The map is flagged as possibly stale when changes are waiting for review, when no active node has been updated in 7 days or more, or when the map is empty. The agent then sees a warning first, telling it to treat suggestions as hints and check the code.
• Hidden config and entry files. The map hides standard nodes for lockfiles, tsconfig*.json, vite.config.*, *.config.ts and similar, index.* and main.* entry files, and nested duplicate CLAUDE.md or AGENTS.md files. The agent is told how many are hidden and can pass include_hidden=true to list them. spec and rule nodes are never hidden, and the Context Editor shows everything.
• vibeless_get_node. Opens one node. A context node with more than 8 KB of content returns an outline of its headings first; the agent then requests sections, the full text, or numbered chunks when there are no headings.
• vibeless_search_specs. The same search as the panel, limited to the agent's project, with the same 20-result cap.
• vibeless_spec_neighbors. Lists a node's edges, plus the code-graph nodes and repository files its file mappings match. It returns no content.
• vibeless_get_context. Deprecated. Returns the suggested starting points only.

Agents can read the spec map but cannot write to it. Nodes, edges, and file mappings change only in the app.

Rules and limits

• Nodes created from the Spec Editor belong to it. Edits made to them here are overwritten, and a switched-off synced node is switched back on, the next time the project's spec fields sync.
• Inactive nodes are invisible to agents and do not count toward the freshness check.
• Search returns at most 20 results, in the app and for agents.
• VC Copilot needs a paid plan. The free plan has no LLM features.

If something looks wrong

• The agent warns that the map may be stale. Review pending changes and update the nodes that cover recent work. The warning clears when nothing is pending and an active node was updated within 7 days.
• A config file is missing from the agent's map. It is probably hidden. The agent can call vibeless_declare_intent with include_hidden=true.
• An edit to a Project Goal or constraint node disappeared. Those nodes mirror the Spec Editor. Make the change there.
• A deleted edge came back. It was automatic and its evidence still holds. Change the file mappings or content that produce it.
• Search finds nothing. Type at least 2 characters. Search does not cover decisions or hooks.