Overview
Episodes are chronological records of events — conversations, operations, state changes, and observations. They form the foundational layer of Neuradex’s memory system. For why structured memory matters over simple chunk search, see the concept overview.Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier |
content | string | Episode content |
episodeType | string | Type of episode |
actorType | string | Who performed the action |
actorId | string? | Actor identifier |
actorName | string? | Actor display name |
channel | string | Source channel |
sessionId | string? | Session grouping ID |
parentEpisodeId | string? | Parent episode (for Q&A threading) |
scopeType | string | Scope type (project) |
scopeId | string | Scope identifier |
occurredAt | string | When the event occurred |
createdAt | string | Creation timestamp |
Episode Types
Each episode is classified by its type, describing the nature of the recorded event.| Type | Description |
|---|---|
question | User question |
answer | Agent or system answer |
action | Operation performed |
observation | State change observed |
Actor Types
The actor type indicates who or what generated the episode.| Type | Description |
|---|---|
user | Human user |
agent | AI agent or assistant |
system | System-generated |
Channels
Episodes can originate from various channels, each representing a different integration point.Session Management
Episodes within the same session are grouped bysessionId. This allows you to retrieve all events that occurred within a single interaction or workflow.
Use parentEpisodeId to thread questions and answers together. For example, an answer episode can reference the question episode it responds to, forming a clear Q&A pair.
Related Pages
Data Types
Concept overview of all data types
Episodes API
Manage episodes with the SDK