# ElizaOS Weekly Newsletter (May 3 – May 9, 2026) ## 1) Executive Summary This week was about **turning ElizaOS into sturdier, more composable infrastructure**—with a few ecosystem wins that signal where things are headed next. - **Payments milestone for x402 routes:** `elizaOS` and `DegenAI` were added as **default payment methods** for x402 routes—an important step toward “agents that can charge” becoming a first-class primitive. - **ElizaCloud consolidation + cheaper hosting path:** ElizaCloud was **folded into the main monorepo** (`github.com/elizaOS/eliza`) and migrated away from Vercel toward **container-based deployments** to reduce operating costs and improve flexibility. - **Monorepo acceleration:** Big repo-level moves landed—**Slack plugin migration**, **Cloud monetized domains support**, and **vault-based secret management**—all pointing toward a unified, production-grade developer platform. --- ## 2) Development Updates (Core + Cloud + Plugins) ### Platform infrastructure & repository structure - **ElizaCloud is now “in-tree.”** If you previously followed Cloud work in separate repos, the canonical location is now the main monorepo: `github.com/elizaOS/eliza`. Alongside the move, the team also shifted off Vercel to support **cheaper container solutions**, prioritizing sustainable ops and easier deploy portability. ### Security & configuration: secrets done right - **`@elizaos/vault` introduced (and wired into Settings UI).** This adds cross-platform secrets storage (OS keychain where available, passphrase fallback for headless) and reduces plaintext credential handling in configs. If you’ve been waiting for a “real” approach to key management in local + self-hosted environments, this is a major quality-of-life upgrade. - Key PR: **Vault feature + integration**: [elizaos/eliza#7197](https://github.com/elizaos/eliza/pull/7197) - Related hardening for headless Linux stability: [elizaos/eliza#7230](https://github.com/elizaos/eliza/pull/7230) ### Cloud monetization & domains - **Support for monetized container app domains** landed—covering app-scoped chat endpoints, managed domain flows, and container lifecycle reconciliation. This is a foundational step for developers to ship apps on Cloud with clearer ownership, billing, and domain handling. - Key PR: [elizaos/eliza#7376](https://github.com/elizaos/eliza/pull/7376) ### Connectors & automation UX - **Slack connector moved into the monorepo,** bringing actions/providers/tests under the unified plugin structure. This reduces drift and improves maintainability across connectors. - Key PR: [elizaos/eliza#7375](https://github.com/elizaos/eliza/pull/7375) - **n8n clarification loop improvements** continued: routes and UI now better support “needs clarification” responses and quick-pick clarification options, making automation-building feel less brittle when agents need missing fields/credentials. - Clarification route: [elizaos/eliza#7316](https://github.com/elizaos/eliza/pull/7316) - Quick-pick UI: [elizaos/eliza#7341](https://github.com/elizaos/eliza/pull/7341) ### Reliability & build modernization - The weekly engineering theme was **hardening and simplification**—including dependency upgrades, CI fixes, and removing legacy components to keep the monorepo consistent. One especially large consolidation PR added Cloud + plugins while removing Rust/Python legacy structure where no longer needed. - Key PR: [elizaos/eliza#7235](https://github.com/elizaos/eliza/pull/7235) --- ## 3) Community Spotlight (Discord) ### Payments + infra excitement The biggest “product momentum” moment came from the x402 payment update: community members reacted strongly to the idea that **payments are now default-path** for certain routes. This is the kind of plumbing that makes agent commerce feel inevitable instead of aspirational. ### Governance clarity: fair launch, builder-led Shaw reiterated a core ethos that’s worth repeating: **ElizaOS is a fair launch** (no VC, no traditional team structure) and is increasingly shaped by **builders who use the tech and ship on top of it**. Importantly, the founder role was framed as **product-driven** rather than “token-price-managed,” setting expectations for where energy is going (shipping). ### Builder wins & projects - A community member shared that **“elizaOK”** was selected for the **Fourmeme Hackathon Top 20**, a nice signal that external ecosystems are noticing ElizaOS-based work. - **RubyHighAI** (early-stage AI learning platform) was shared—bugs and all—which is exactly the kind of “ship early” experimentation the ecosystem benefits from. - A new dev introduced themselves offering **AI + full-stack help** (LLM systems, agents, RAG, automation). If you’re looking for collaborators, Discord continues to be the fastest path. ### Open questions worth addressing next A few practical deployment/integration questions went unanswered this week (good candidates for docs or a FAQ pass): - Expected costs to run Eliza as a **Twitter bot** in the cloud; feasibility on **Mac mini** hardware. - Whether ElizaOS still connects to **Hyperfy**. (If you have answers or benchmarks, consider replying in `#coders`—these are high-leverage for new builders.) --- ## 4) Token Economics (AI16Z token + auto.fun) ### What changed this week - **No official parameter changes** (supply, emissions, etc.) were announced in the provided data. - Community discussion focused on **token operations and bridging**: members suggested **Wormhole** and **deBridge** as possible routes for bridging between **BSC and Solana**. ### Market chatter (context, not guidance) - There was visible excitement around **V3 price movement (reported +90–130%)** and comparisons to other tokens’ runs. As always: keep hype separate from fundamentals, and keep fundamentals anchored to what’s being shipped (payments, cloud monetization, infra hardening). ### auto.fun - No concrete auto.fun ship-items were included in this week’s dataset. If auto.fun updates were posted elsewhere, drop links in Discord so we can include them next week. --- ## 5) Coming Soon Here’s what’s most “next-up” based on this week’s direction: - **eliza-1 model training progress:** Shaw discussed ongoing work training **eliza-1** on a **Qwen base**, with performance/efficiency techniques like **speculative decoding (dflash)**, **thinking compression (caveman compression)**, and **quantization (turboquant)**. A **v2.0.0-beta.0** was mentioned as part of the development cycle—suggesting more visible packaging/release cadence soon. - **More monetization primitives:** Between x402 default payment methods and Cloud’s monetized domains/app chat paths, expect continued iteration on **billing + auth + domain lifecycle** so developers can reliably sell agent-driven apps. - **Docs and “self-host clarity”:** Given the unanswered deployment-cost and hardware questions, expect (or contribute) clearer guidance on **self-hosting footprints**, cost profiles, and supported integrations. --- ## 6) Resources (Links) **Discord threads (high signal):** - Discussion (payments + repo consolidation + governance): https://discord.com/channels/1253563208833433701/1253563209462448241 - Coders (deployment + integration questions): https://discord.com/channels/1253563208833433701/1300025221834739744 **Key pull requests (engineering highlights):** - `@elizaos/vault` secrets vault + Settings UI: https://github.com/elizaos/eliza/pull/7197 - Monetized container app domains (Cloud): https://github.com/elizaos/eliza/pull/7376 - Migrate Slack plugin into monorepo: https://github.com/elizaos/eliza/pull/7375 - Consolidation / large repo restructure: https://github.com/elizaos/eliza/pull/7235 - n8n clarification route: https://github.com/elizaos/eliza/pull/7316 - Automations clarification quick-pick UI: https://github.com/elizaos/eliza/pull/7341 If you want to help next week: pick one unanswered deployment question, run a quick benchmark (even rough), and post your findings—those threads are where new builders decide whether to commit.