elizaos

An elizaOS plugin is a plain object registering actions, providers, services, models, evaluators, routes, and events. At registration, plugin.init runs first, components are registered, routes are namespaced under the plugin name, and services initialize asynchronously.

Memory is persistent data such as messages, documents, and fragments stored across turns. State is ephemeral per-turn context with values, data, and text fields, built by providers during composeState for prompt composition and action execution.

Use a provider when the feature changes prompt context, since providers run during composeState and return text, values, or data. Use an action when the feature performs an operation or side effect executed through planned tool calls.

Providers marked private or dynamic are excluded from the default provider set unless explicitly requested. Also check provider ordering via the position field, since providers are ordered during state composition.

The pipeline ingests a message, persists the incoming memory, composes state via providers, optionally processes attachments, decides whether to respond, runs model inference, executes actions, persists the response, runs evaluators, and emits lifecycle events.