| Aspect | Value |
|---|---|
| Scope | Configurable (global, user, or custom namespace) |
| Persistence | Long-term |
| Default mode | Always |
| Supported modes | Always, Agentic |
Basic Usage
Three Types of Knowledge
Facts
Timeless truths: “Uses PostgreSQL”, “Headquarters in San Francisco”, “50 employees”Events
Time-bound occurrences: “Launched v2.0 on January 15”, “Closed $50M Series B”, “Had 4-hour outage”Relationships
Entity connections: Jane Smith → CEO → Acme Corp, Acme Corp → competitor_of → Beta IncAlways Mode
Entities are extracted automatically from conversations.Agentic Mode
The agent receives tools to manage entities explicitly.search_entities, create_entity, update_entity, add_fact, update_fact, delete_fact, add_event, add_relationship
Data Model
| Field | Description |
|---|---|
entity_id | Unique identifier (e.g., “acme_corp”) |
entity_type | Category: “company”, “person”, “project” |
name | Display name |
description | Brief description |
properties | Key-value metadata |
facts | Timeless truths |
events | Time-bound occurrences |
relationships | Connections to other entities |
Accessing Entity Memory
Context Injection
Relevant entities are injected into the system prompt:Namespaces
Control who can access entity data:Facts vs Events
| Use facts for | Use events for |
|---|---|
| Tech stack | Product launches |
| Headquarters location | Funding rounds |
| Employee count | Outages or incidents |
| Industry/domain | Partnerships announced |
| Pricing model | Key meetings |
Relationship Types
Common patterns for linking entities:- People:
CEO,CTO,engineer_at,founder,reports_to - Companies:
competitor_of,partner_of,acquired_by,subsidiary_of - Projects:
uses,depends_on,integrates_with,owned_by