# ElizaOS Weekly Newsletter (Apr 26, 2026 – May 01, 2026) ## 1) Executive Summary **This week was about turning “v3 vision” into an executable platform.** Here are the biggest takeaways: 1. **ElizaOS v3 was clearly defined as a full application runtime**—not just an “agent framework.” Shaw shared a detailed architectural overview: cross-device, cross-platform, social-native (including iMessage), capable of issuing tasks to tools like **Codex** and **Claude**, and designed for building/editing/running apps dynamically with monetization through **Eliza Cloud**. 2. **Real infrastructure utility landed for $ELIZA via x402**: $ELIZA is now implemented as the **default payment method in x402** for elizaOS/Milady services, connecting the token directly to paid routes and service usage rather than abstract “utility.” 3. **Shipping momentum continued in the codebase**: dependency and infra upgrades (AI SDK updates, self-hosting improvements like CORS + bearer auth, Docker tag updates) plus active discussion of ecosystem expansions (Hive Civilization on Base, SwarmScore reputation). --- ## 2) Development Updates (Technical) ### ElizaOS v3 runtime direction (architecture + product surface) Across Discord updates and community Q&A, v3 is being positioned as a **runtime that hosts applications and workflows**, with key capabilities that will matter to builders: - **Social integrations** across platforms (explicitly including **iMessage**) - **Tool/task delegation** to external copilots/agents (e.g., Codex, Claude) - **Workflow creation** and runtime “apps” that can be created/edited/executed dynamically - **Subscription management** as a first-class concern - Monetization via **Eliza Cloud**, aiming to let agents/app creators charge for what they ship A notable proof point shared this week: **“botdick” (an Eliza agent) created its own video game**, demonstrating the “agents that build” thesis. ### AI SDK + dependency maintenance (keeping providers healthy) Framework compatibility work continued with key version bumps: - **Anthropic AI SDK → v0.92.0** - **AI dependency → v6.0.172** - **provider-utils → v4.0.25** - **provider → v3.0.10** - **OpenAI provider → v3.0.55** These upgrades are not flashy, but they’re essential—provider breakage and subtle SDK behavior changes are often where agent reliability goes to die. ### Self-hosting and infra hardening For teams running ElizaOS in their own environments, the following improvements landed: - **CORS support** added for self-hosted deployments - **Bearer authentication** introduced (a practical step toward production-ready deployments) - **Cross-platform build fixes** (important as the runtime spans more devices/OS targets) - **Supabase/Postgres Docker tag updated → v17.6.1.113** ### Strategic proposals in motion (ecosystem breadth) Two integrations moved into active discussion: - **Hive Civilization on Base mainnet**: aimed at expanding the agent ecosystem footprint - **SwarmScore**: a potential **agent reputation rating** layer (useful for marketplaces, discovery, and trust signaling) --- ## 3) Community Spotlight (Discord) ### A candid, important conversation on building through drawdowns Shaw addressed frustrations head-on: the Discord is for contributors, and the project is **still building despite market conditions**. He also provided unusually direct transparency on the project’s constraints—particularly the funding reality after token collapse—and why v3 has been built with sustained effort over ~6 months. ### AMA + demos: Botdick and v3 An AMA was held featuring **Shaw, binkyfishai, and baogerbao**, focused on **Botdick** and **ElizaOS v3**. The big win here wasn’t just hype—it was aligning the community around what v3 *is* (runtime + apps + monetization), not what people assume it is (another chat agent wrapper). ### New builders raising their hands Several community members signaled willingness to contribute: - **Aiden190157** expressed interest in helping - **rsn6958** shared detailed AI/full-stack credentials with a production mindset - **Kevin111s** proposed collaboration: they build production AI workflows/backends and want a US-based partner for client-facing coordination - **0xtdl01** joined with thoughtful security + local-first questions (see below) ### Security-minded discussion (healthy signals) A new thread of conversation touched on: - **Local LLM data storage** - **Keeping agent keys local** - **Red-team swarm testing** methodologies This is exactly the type of pragmatic, operational thinking that tends to separate “cool demos” from “systems people can trust.” --- ## 4) Token Economics (AI16z, $ELIZA, and auto.fun) ### $ELIZA: tangible payment rails via x402 The clearest token development this week: **$ELIZA is now the default payment method in x402 for elizaOS/Milady services**. That’s meaningful because it ties token flow to **service consumption** (paid plugin routes / paid infra), not just narrative. ### AI16z + buyback comments (profit-first) Shaw reiterated that prior token dynamics created real team constraints (no meaningful equity after collapse). On forward-looking token strategy: a **buyback plan** was mentioned, but explicitly **contingent on profitability**—a sober framing that avoids promising financial mechanics before the underlying business can support them. ### auto.fun No concrete shipping updates were reported in the provided data this week, but community interest remains visible (including active “auto.fun enjoyer” identities). If you’re building on or around auto.fun, now is a good time to surface what you’re shipping so it can be amplified alongside v3/Cloud momentum. --- ## 5) Coming Soon (What to anticipate) Based on team and community signals, here’s what’s likely next on the near-term horizon: - **Eliza v3 + Milady integration nearing completion** (Shaw hinted the next couple weeks should be “exciting”) - **Eliza Cloud** maturation: monetized runtime apps, subscriptions, and developer-facing workflows - Deeper **social platform integrations** (including the iMessage target) - Continued **self-hosting hardening** (auth, cross-platform builds, deployment ergonomics) - Potential ecosystem expansions: **Hive Civilization (Base)** + **SwarmScore** if proposals solidify - More focus on **security posture**: local key custody patterns and red-team swarm testing --- ## 6) Resources (Links & Pointers) ### Key discussions (Discord) - v3 architecture + funding + token philosophy thread (Apr 30): https://discord.com/channels/1253563208833433701/1253563209462448241 - AMA announcement/context (Apr 30): https://discord.com/channels/1253563208833433701/1253563209462448241 ### Where to find examples beyond docs - Community members were pointed to an examples channel: `#1299989396874854440` (in the ElizaOS Discord) ### Recent GitHub highlights referenced in weekly rollups - TypeScript/Node/Bun modernization: https://github.com/elizaos/elizaos.github.io/pull/247 https://github.com/elizaos/eliza/pull/7151 - Cloud migration to Vite + Hono Workers: https://github.com/elizaos/cloud/pull/484 https://github.com/elizaos/cloud/pull/482 - Android native agent execution (foreground service): https://github.com/elizaos/eliza/pull/7172 - Multi-chain payment support (plugins registry): https://github.com/elizaos-plugins/registry/pull/352 ### Security-related external note shared - Claude Security public beta (Enterprise) mentioned in Discord: codebase vuln scanning + patch suggestions (see Apr 30 discussion link above) --- If you’re looking for the “one sentence” theme of the week: **v3 is converging on a real runtime + payment rails + Cloud monetization—while the community shifts from price talk to shipping, security, and integration depth.**