← Back to all projects

eliza

TypeScript agents from character files and plugins, inside a product stack that now outweighs the framework

OfficialMIT
Stars
19.7k
Forks
5.9k
Open issues
127
Last commit
30 Oct 2026

What is eliza?

You write a character file — a name, a system prompt, a few bio lines and the list of plugins to load — and the runtime turns it into an agent that stores each message, composes context from the providers the turn actually routes to, lets the model pick an action, and files what it learned through evaluators that run after the reply. First-party plugins ship in the same repository for the chat platforms people already use, MCP servers, browser and desktop control, calendar and inbox assistants, non-custodial EVM and Solana wallets, and an on-device model path that answers with the network off. Two things to weigh before adopting it: the repository is a whole product stack — desktop and mobile apps, a hosted cloud, native device bridges — so you take on far more than an agent library, and the stable release on npm is still the older 1.x line while the stack described here ships only under beta and alpha tags.

What can you do with eliza?

  • Write the agent as a character file — Character holds name, a system prompt, bio and topics as lists of strings, messageExamples as groups of example exchanges, and style, whose all voice is the shared one that both chat and post build on. plugins names the packages to load, and knowledge points at documents the agent can look things up in.
  • Learn which providers the runtime actually asks — AgentRuntime stores the message, composes state, lets the model choose among registered actions, runs their handlers, then hands the turn to evaluators once the reply is out. Composition is selective: providers marked private or dynamic are skipped outright, and the rest run only when their declared contexts match the ones the turn was routed to — declare nothing and you get general, which drops out of narrow planner turns. alwaysInResponseState is the opt-in for a signal that should always be there.
  • Add capability as a plugin object — A Plugin exports any mix of actions (a validate check plus a handler returning success or failure), providers (a get returning text and structured data), evaluators, long-running services, model handlers, HTTP routes, app views and event listeners. The 2.x beta CLI scaffolds one with elizaos create my-plugin --template plugin; on the 1.x release that npm still installs by default the same flag is --type plugin.
  • Put the agent where people already talk — Connectors for Discord, Telegram, Slack, WhatsApp, Signal, Matrix, WeChat, X, Instagram and iMessage ship in the repository, alongside plugin-mcp, which reads servers from settings.mcp.servers and exposes their tools through a single MCP action, and assistant plugins for calendar, contacts, inbox, notes, todos and reminders. Of the hundred-plus plugin directories, roughly thirty are native device bridges that only do anything inside the Eliza app.
  • Run the models on the machine itself — plugin-local-inference serves text generation, embeddings, transcription, Kokoro speech synthesis, image generation and image description on-device, needing no network once the model files land in ~/.eliza/models. Routing is set per capability from the dashboard, so transcription can stay local while reasoning goes to a hosted provider.
  • Let it drive a browser or the desktop — plugin-browser adds a BROWSER action — open, navigate, click, type, fill, press, scroll, hover, drag, snapshot, screenshot — driving an embedded browser view, a paired Chrome or Safari extension, or a Playwright endpoint. plugin-computeruse takes the machine itself: screen capture, mouse and keyboard, window management, clipboard and OCR, with an approval inbox in front of it. Both are off until you enable them, and desktop input needs cliclick on macOS or xdotool on Linux.

Before you choose eliza

  • As of August 2026 the stable npm tag for elizaos and @elizaos/core still resolves to the 1.x line last published in January, while the 2.x stack described here ships only under the beta and alpha tags.
  • In August 2026 the founder said the ELIZAOS token was dead and the foundation winding down after a class-action settlement transferred the remaining treasury, while pledging that open-source development continues.

Star history

17 Aug to 30 Oct · +655

19.1k19.7k

Frequently asked questions

Is eliza free for commercial use?

eliza is released under the MIT licence — OSI-approved open source, which permits commercial use.

How can eliza be deployed?

eliza is available as Self-hosted / Runs locally / Managed cloud.