Knowledge Graph
Connect your knowledge items with meaningful relationships to build a network of interconnected information.
What is the Knowledge Graph?
The Knowledge Graph transforms your stored items from a flat list into a connected network. Each relationship describes how two pieces of knowledge are connected, making it easier for Claude to understand context and find relevant information.
For example, a bug report can be linked to the feature spec it depends on, a decision document can supersede an older one, and test patterns can reference the hooks they cover.
Relationship Types
| Type | Meaning | Example |
|---|---|---|
related_to | General connection | "Auth Flow" ↔ "Login Bug" |
references | Cites or mentions | "Design Doc" → references → "API Spec" |
depends_on | Requires the other to work | "Feature X" → depends on → "Auth System" |
implements | Implements what the other describes | "PR #42" → implements → "Feature Spec" |
extends | Builds upon or expands | "V2 Plan" → extends → "V1 Plan" |
part_of | Is a component of | "Login Page" → part of → "Auth Module" |
similar_to | Content is similar | "Error Handling v1" ↔ "Error Handling v2" |
derived_from | Created based on | "Summary" → derived from → "Meeting Notes" |
supersedes | Replaces the other | "New Policy" → supersedes → "Old Policy" |
contradicts | Conflicts with | "Requirement A" ↔ "Requirement B" |
Creating Relationships
Via Claude (MCP)
The most natural way to create relationships is by asking Claude in your terminal. Claude will use the MCP tools automatically.
Link two items
"The Auth Flow item depends on the Login Bug, link them"Bidirectional link
"Connect Test Patterns and Pre-Push Hook, they're related to each other"Ask about connections
"What's connected to Auth Flow?"Explore your knowledge
"What do I have about testing and how is it all connected?"Via Dashboard
You can also create relationships directly from the dashboard:
- Open a Space and click on any Knowledge Item
- In the drawer, scroll down to Related Items and click the + Link button
- Select the target item from the dropdown
- Choose the relationship type
- Optionally check Bidirectional to create the link in both directions
- Click Link
Unidirectional vs Bidirectional
Unidirectional
The link goes one way. Good for relationships with clear direction.
Example: Feature X → implements → Spec Y
Bidirectional
The link goes both ways. Good for symmetric relationships.
Example: Doc A ↔ related to ↔ Doc B
Viewing Relationships
There are several ways to see relationships:
- Space stats grid — Shows the total relationship count for the space
- Item list — Items with relationships show a "Linked to..." badge with the names of connected items
- Item drawer — The Related Items section shows all connections with direction indicators and relationship type badges
- Claude — Ask "What is related to [item]?" and Claude will use
memory_list_relationshipsto show you the connections
Removing Relationships
In the item drawer, hover over any relationship row and click the trash icon to remove it. For bidirectional relationships, this removes both directions at once.
MCP Tools Reference
memory_relate
Create a relationship between two items.
source_id — UUID of the source item
target_id — UUID of the target item
relationship_type — One of the types listed above
weight — Strength of the relationship (0-1, default: 0.5)
bidirectional — Create in both directions (default: false)
memory_list_relationships
List all relationships for a knowledge item.
item_id — UUID of the item to query