ElizaOS Architecture
Source analysis of elizaos/eliza v2.0.0-alpha.176. Multi-agent Web3 framework with 35+ plugins.
Key Insights
- Character-driven runtime: Agents as JSON personality configs with knowledge arrays, style guides, topics, and message examples - separates behavior from implementation, enables non-technical creation
- Plugin composition: 4 types (Actions=tools, Providers=context, Evaluators=assessment, Services=background) - 35+ plugins from Solana/EVM to Discord/Telegram, clean separation vs monolithic
- Multi-platform abstraction: Unified client pattern hides platform differences (Discord, Telegram, Twitter, Direct API) - cross-platform agents without platform-specific code
- Web3-native design: Built-in wallet + blockchain as first-class citizens (EVM chains, Solana, TEE) - token operations, DeFi, smart contracts integrated at the core
- Advanced memory with trust: RAG with embeddings + fact extraction, relationship tracking with trust scores, trajectory logging for decision trees - persistent context beyond simple chat history
What's Shocking
- Character JSON as portable agent identity: Share and fork entire agent personalities without any code or credentials. A JSON file IS the agent — bio, voice, style, lore, knowledge arrays, topics, message examples. Non-technical users create agents by editing text.
- The plugin ecosystem IS the product: 35+ plugins (Solana, EVM, TEE, Farcaster, Discord, Telegram, Twitter) with action/evaluator/provider architecture — the runtime is just a shell. The marketplace and community contributions are what drove 20K+ stars and a $20B+ partner ecosystem.
- Multi-agent coordination built-in: WorldEngine manages shared state across agent swarms. Trajectory logging persists decision trees. Trust scoring tracks relationships. This isn't single-agent scaffolding — it's orchestration infrastructure.