You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/docs/core/actions.md
+28
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@ sidebar_position: 6
6
6
7
7
Actions are core building blocks in Eliza that define how agents respond to and interact with messages. They allow agents to interact with external systems, modify their behavior, and perform tasks beyond simple message responses.
8
8
9
+
---
10
+
9
11
## Overview
10
12
11
13
Each Action consists of:
@@ -17,6 +19,8 @@ Each Action consists of:
17
19
-`handler`: Implementation of the action's behavior
Copy file name to clipboardexpand all lines: docs/docs/core/agents.md
+6-3
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Agents are the core components of the Eliza framework that handle autonomous int
10
10
11
11
## Overview
12
12
13
-
The [AgentRuntime](/api/classes/AgentRuntime) class is the primary implementation of the [IAgentRuntime](/api/interfaces) interface, which manages the agent's core functions, including:
13
+
The [AgentRuntime](/api/classes/AgentRuntime) class is the primary implementation of the [IAgentRuntime](/api/interfaces/IAgentRuntime) interface, which manages the agent's core functions, including:
14
14
15
15
-**Message and Memory Processing**: Storing, retrieving, and managing conversation data and contextual memory.
16
16
-**State Management**: Composing and updating the agent’s state for a coherent, ongoing interaction.
@@ -90,7 +90,7 @@ const runtime = new AgentRuntime({
90
90
91
91
## State Management
92
92
93
-
This section should cover how agents manage and update state, with a focus on initial state composition and updating methods. The runtime maintains state through the [State](/api/interfaces) interface:
93
+
This section should cover how agents manage and update state, with a focus on initial state composition and updating methods. The runtime maintains state through the [State](/api/interfaces/state) interface:
94
94
95
95
```typescript
96
96
interfaceState {
@@ -148,7 +148,7 @@ The Eliza framework uses multiple types of memory to support an agent's long-ter
148
148
149
149
-**RAG Integration**: Uses a vector search to perform contextual recall based on similarity matching. This enables the agent to retrieve relevant memory snippets or knowledge based on the content and intent of the current conversation, making its responses more contextually relevant.
150
150
151
-
The runtime uses multiple specialized [IMemoryManager](/api/interfaces) instances:
151
+
The runtime uses multiple specialized [IMemoryManager](/api/interfaces/IMemoryManager) instances:
152
152
153
153
-`messageManager` - conversation messages and responses
154
154
-`descriptionManager` - user descriptions and profiles
Copy file name to clipboardexpand all lines: docs/docs/core/characterfile.md
+11-3
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,11 @@ sidebar_position: 4
6
6
7
7
Character files are JSON-formatted configurations that define an AI character's personality, knowledge, and behavior patterns. This guide explains how to create effective character files for use with Eliza agents.
8
8
9
+
---
10
+
9
11
## Overview
10
12
11
-
A `characterfile` implements the [Character](/api/type-aliases) type and defines the character's:
13
+
A `characterfile` implements the [Character](/api/type-aliases/character) type and defines the character's:
12
14
13
15
- Core identity and behavior
14
16
- Model provider configuration
@@ -90,11 +92,11 @@ The character's display name for identification and in conversations.
90
92
91
93
#### `modelProvider` (required)
92
94
93
-
Specifies the AI model provider. Supported options from [ModelProviderName](/api/enumerations) include `ANTHROPIC`, `LLAMALOCAL`, `OPENAI`, and others.
95
+
Specifies the AI model provider. Supported options from [ModelProviderName](/api/enumerations/modelprovidername) include `ANTHROPIC`, `LLAMALOCAL`, `OPENAI`, and others.
94
96
95
97
#### `clients` (required)
96
98
97
-
Array of supported client types from [Clients](/api/enumerations) e.g., `DISCORD`, `DIRECT`, `TWITTER`, `TELEGRAM`.
99
+
Array of supported client types from [Clients](/api/enumerations/clients) e.g., `DISCORD`, `DIRECT`, `TWITTER`, `TELEGRAM`.
98
100
99
101
#### `bio`
100
102
@@ -205,6 +207,8 @@ The `settings` object defines additional configurations like secrets and voice m
Copy file name to clipboardexpand all lines: docs/docs/core/evaluators.md
+11-8
Original file line number
Diff line number
Diff line change
@@ -4,24 +4,21 @@ sidebar_position: 5
4
4
5
5
# 📊 Evaluators
6
6
7
-
## Table of Contents
7
+
[Evaluators](/api/interfaces/evaluator) are core components that assess and extract information from conversations. They integrate with the [AgentRuntime](/api/classes/AgentRuntime)'s evaluation system.
[Evaluators](/api/interfaces) are core components that assess and extract information from conversations. They integrate with the [AgentRuntime](/api/classes/AgentRuntime)'s evaluation system, enabling agents to:
Copy file name to clipboardexpand all lines: docs/docs/core/providers.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# 🔌 Providers
2
2
3
-
[Providers](/api/interfaces) are core modules that inject dynamic context and real-time information into agent interactions. They serve as a bridge between the agent and various external systems, enabling access to market data, wallet information, sentiment analysis, and temporal context.
3
+
[Providers](/api/interfaces/provider) are core modules that inject dynamic context and real-time information into agent interactions. They serve as a bridge between the agent and various external systems, enabling access to market data, wallet information, sentiment analysis, and temporal context.
0 commit comments