# ElizaOS Weekly Newsletter (2026-04-29 → 2026-05-05) ## 1) Executive Summary **1) Cloud monetization rails took a big step forward.** This week delivered meaningful groundwork for *revenue-generating* apps on Eliza Cloud: support for **monetized container app domains** (including route ownership + Cloudflare management), plus a series of fixes that stabilize **auth, sessions, and the CLI login flow**. This is the kind of “plumbing” that makes the upcoming launches feel real—not just aspirational. **2) The connector ecosystem kept consolidating into a cleaner monorepo.** The **Slack connector** migrated into the main monorepo, bringing a mature action/provider set and a strong test suite with it. Combined with earlier repo consolidation work, this continues the trend toward “one place to build” for core + plugins + cloud. **3) Community energy spiked alongside price movement, but the long-term message stayed consistent.** Discord saw a major **V3 price move (+90–130%)**, yet the core narrative from Shaw and other contributors remained focused on building **revenue-first products** (V3 launch, Eliza Cloud, Milady app) rather than optimizing for short-term token action. --- ## 2) Development Updates (Technical) ### Cloud Infrastructure & Monetization - **Monetized container app domains + Cloudflare management landed.** Key capabilities shipped include route ownership checks, Cloudflare-managed domain flows, and app domain lifecycle support—critical for deploying “real” hosted apps with branded domains. *PR:* **elizaos/eliza #7376** (feat(cloud): support monetized container app domains) - **Stability fixes across billing + frontend routing.** - Fixed a **billing-data fetch loop** in the Cloud dashboard UI that could trigger repeated renders. *PR:* **#7374** (fix(cloud): stop billing-fetch render-loop in CloudDashboard) - Consolidated **Cloudflare Pages Functions** to reduce routing drift and improve reliability (part of the login/session stabilization work). - Multiple patches improved **steward login + CLI login** session synchronization (including deadlock/race fixes). ### Automations (n8n) UX + Reliability - **Clarification roundtrip is now end-to-end.** The platform can request missing workflow details in a structured way (instead of silently failing or hallucinating), and the UI can render those clarifications inline. - Route support for clarification resolution: **#7316** - UI “quick-pick” buttons for clarifications in AutomationsView: **#7341** - Bugfixes to handle free-form clarifications and deletion flows: **#7370**, **#7340** - Parsing hardening for “JSON + trailing prose” model outputs: **#7369** - Prompt/typing improvements in the workflow generator: **#7373** ### Connectors & Plugins - **Slack plugin migrated into the monorepo.** This brings Slack in line with other first-class connectors (Discord/Telegram/etc.), and centralizes actions/providers under the same build/test conventions. *PR:* **#7375** (feat(slack): migrate plugin-slack into the monorepo) ### Agent Autonomy: LifeOps Expansion - **New LifeOps modules shipped** to increase agent autonomy in day-to-day contexts, including proactive planning, inbox management, health monitoring, and activity reporting. *PR:* **#7356** (“lifeops code + analysis mode”) ### Configuration & Runtime Fixes - **Vault sentinel handling corrected** so vault sentinel keys are skipped during environment variable application (prevents config/env churn and confusing runtime state). *PR:* **#7368** (fix(agent): skip vault sentinels in applyConfigEnvToProcessEnv) --- ## 3) Community Spotlight (Discord) ### Market Momentum + Architecture Pride The discussion channel was buzzing as community members reported **V3 up 90–130%** from recent lows. Alongside the excitement, *zadayos* shared a strong architecture-focused perspective: elizaOS is being positioned as scalable infrastructure—capable of supporting **hundreds of thousands of agents**, with attention to fees, security, and UI/UX, plus “hidden features” meant to unlock developer integrations later. ### The “Revenue First” Token Conversation (from Shaw) In a more philosophical thread, **Shaw** reiterated a key framing: token holders should not view themselves as *traditional investors*, and **buybacks can’t happen without revenue**. The message was blunt but clarifying: the team is building products intended to generate sustainable revenue first, and the timeline should be thought of more like a real business (years), not a meme-cycle. ### Builders Showing Up A few standout builder moments: - **marianodim** announced a **spot trading agent** built on ElizaOS targeting SOL, SUI, and additional tokens, aiming to test multiple strategies and produce **1–2 signals/week** over the coming weeks. - **rsn6958** introduced themselves as an AI + full-stack developer focused on *production-ready, maintainable systems*—always a good sign as the ecosystem shifts from speculation to execution. - **odilitime** invited members to join the **“eliza army steering”** group for community coordination and momentum. ### Ops Friction: Bots + Links Two recurring pain points got airtime: - **Bot/spam management** in Discord (mods noted ongoing efforts). - **URL spam filtering** blocking legitimate links; workaround shared: wrap URLs in backticks like `` `https://example.com` ``. --- ## 4) Token Economics (AI16z token & auto.fun) ### Price Action + Liquidity Questions - Community reported **significant upside movement** this week (90–130% in the discussion thread), with some members taking partial profits and others holding for longer-term thesis execution. - A practical concern surfaced: **low liquidity on Solana**, with community members asking for clarity on why it looks thin there and what can be done. ### “Utility Later, Product Now” No new on-chain mechanics, buyback commitments, or token-utility changes were announced in the provided notes this week. The clearest token-economic signal remains strategic: **revenue-generating products first**, then sustainable token mechanisms (e.g., buybacks) once revenue exists. ### auto.fun There were **no explicit auto.fun feature or rollout updates** in this week’s provided dataset. If there are specific auto.fun announcements or metrics you want covered next week, drop them in Discord and tag Community Ops so they make the digest. --- ## 5) Coming Soon (What to Watch) Based on team/community direction this week, expect more news around: - **ElizaOS V3 launch execution**, plus the **community PR/marketing plan** being prepared around it. - **Eliza Cloud** continuing to harden around auth, session stability, and monetized app workflows (domains, billing, deployment lifecycle). - **Milady app** positioning as an early **revenue driver** (and a proving ground for UX + integrations). - **Further “hidden features” and utility-token flexibility** hinted at in architecture discussions—likely to surface as developer-facing integration points. --- ## 6) Resources (Links & Threads) ### Discord Discussions - Price + architecture discussion (May 4): https://discord.com/channels/1253563208833433701/1253563209462448241 - Project philosophy / token expectations (May 3): *(same channel context in provided summaries)* https://discord.com/channels/1253563208833433701/1253563209462448241 ### Key PRs Mentioned - Cloud monetized container app domains: **elizaos/eliza #7376** https://github.com/elizaos/eliza/pull/7376 - Slack plugin migrated into monorepo: **#7375** https://github.com/elizaos/eliza/pull/7375 - LifeOps expansion: **#7356** https://github.com/elizaos/eliza/pull/7356 - n8n clarification + UI improvements: **#7316**, **#7341**, **#7369**, **#7370** https://github.com/elizaos/eliza/pull/7316 https://github.com/elizaos/eliza/pull/7341 https://github.com/elizaos/eliza/pull/7369 https://github.com/elizaos/eliza/pull/7370 --- *Want something highlighted next week? Share a link (wrapped in backticks if needed) plus a 1–2 sentence summary in Discord so it’s easy to include.*