elizaOS

On April 22, 2026, the ElizaOS ecosystem focused on stabilizing core infrastructure, with significant progress in authentication migration for elizaos/cloud and extensive dependency hardening across the elizaos/eliza framework. The registry also expanded its plugin ecosystem, while teams addressed critical regressions in Milady integrations and AI billing logic to ensure system reliability.

✅ Completed Work

Authentication and Identity Infrastructure

• Migrated the /app-auth/authorize flow to Steward and implemented native Ethereum and Solana login buttons to improve identity management (elizaos/cloud#466, elizaos/cloud#469).

Framework Stability and Dependency Management

• Hardened the codebase by updating a wide range of Rust, Python, and TypeScript dependencies and applying security patches to python-dotenv and tqdm (elizaos/eliza#7005, elizaos/eliza#7012).
• Restored Milady CI functionality and refactored subpath imports to improve LifeOps signal client reliability (elizaos/eliza#7008).
• Updated vitest and performed bulk cargo group updates across 19 directories to maintain environment consistency (elizaos/eliza#6997, elizaos/eliza#7037).

AI Pricing and Registry Expansion

• Resolved billing lookup failures for image-generation models by correcting pricing row classification (elizaos/cloud#470).
• Integrated @elisym/plugin-elizaos into the registry to support ecosystem growth (elizaos-plugins/registry#346).

🏗️ Work in Progress

New Pull Requests

• elizaos-plugins/registry: Add @holdfastprotocol/eliza-plugin
• elizaos/cloud: fix(auth): send tenant_id to Steward, fix(auth): preempt steward session expiry, fix(db): repair _journal.json drift
• elizaos/eliza: Bump cargo group (15 dirs), Bump cargo group (12 dirs), Introduce local inference hub/provider switcher, 2.x/v3 clean up

🐞 Issue Triage

New Issues

• elizaos/eliza: Telegram read receipts require optimization to avoid inefficient nested lookups.