# ElizaOS Weekly Newsletter (Apr 28, 2026) **Covering:** 2026-04-21 → 2026-04-27 ## 1) Executive Summary **1. Eliza Cloud monetization took a concrete step forward.** This week brought meaningful progress on revenue plumbing: pay‑as‑you‑go container hosting is now enabled, and credit balance management was added so organizations can be billed directly from their earnings. That’s a foundational milestone for turning “agent utility” into sustainable cashflow. **2. Agent reliability and connectivity improved (especially around coding + messaging).** The team added **GitHub PAT persistence** for coding sub‑agents (so spawned agents can authenticate reliably), refined credential feedback for **n8n** workflows, and strengthened message handling to **preserve explicit `REPLY` actions during race conditions**—a subtle but important fix for avoiding dropped or confusing responses in busy rooms. **3. A major dependency modernization wave kicked off across the ecosystem.** Contributor-led Renovate updates began rolling through core repos targeting **Node.js 24**, **TypeScript 6**, and **Rimraf 6**. CI is still validating these bumps, but the direction is clear: keep ElizaOS on current tooling to reduce long‑term maintenance risk. --- ## 2) Development Updates ### Eliza Cloud: billing + hosting capabilities - **Pay‑as‑you‑go container hosting** is now enabled, unlocking more flexible deployments for teams that don’t want fixed plans. - **Credit balance management** landed to support direct billing from org earnings—key for integrating usage-based pricing without adding user friction. ### LifeOps: more real-world automation - **Milady LifeOps gained Google Calendar management capabilities**, extending the “agent as operator” story into scheduling and day-to-day coordination. ### Coding agents: GitHub auth that survives sub-agent spawning - **GitHub PAT persistence** was added for coding sub‑agents, alongside a settings UI card to store a per-user token and pass it to spawned agents via environment variables. This should reduce failed PRs/issues caused by missing auth in delegated work. ### n8n workflow experience: clearer credential handling - Credential feedback for **n8n** workflows was refined, making it easier to understand *why* a workflow deploy failed (e.g., missing credentials) and what to do next. ### Messaging/runtime hardening: fewer “weird” replies under load - Message handling was strengthened to **preserve explicit `REPLY` actions** during race conditions (when a newer message arrives while a response is generating). The goal: avoid throwing away a valid, explicit reply just because the room is active. ### Build and repo hygiene - Fixes landed for **re-export cycles** and **static node imports** to eliminate build warnings. - **Dev and main branches were synchronized** across repositories to reduce drift. - The **supabase/postgres Docker dependency** was updated (now tracking `17.6.1.112` in the reported workstream). ### Dependency modernization (in progress) - Renovate-driven updates targeting **Node 24 + TypeScript 6** are underway across core repos. The team is currently **waiting on CI results** to confirm the major version bumps don’t break release tooling, builds, or templates. --- ## 3) Community Spotlight (Discord) ### “Eliza Army” steering group forming Moderator **odilitime** mentioned an **“eliza army” steering group** is being formed to coordinate community efforts. If you’ve been looking for a way to contribute beyond price chat—this sounds like the on-ramp. ### ELIZA history mini-seminar (and why it matters) A surprisingly wholesome thread broke out about the original **ELIZA** chatbot (1964/1966 Weizenbaum paper) and the **ELIZA effect**—the tendency to project understanding onto software. It’s a useful reminder for builders: clarity about agent capabilities, limitations, and safety boundaries isn’t optional when people emotionally trust what they’re talking to. ### Fast moderation response to a scam attempt A scammer posted a suspicious link targeting a member asking for help. Community members warned the target quickly, and **odilitime banned the account**. Security is a shared responsibility, but fast mod action matters—thanks to everyone who flagged it. ### Hyperscape coordination Members asked about the long-term plan for **Hyperscape** and how to access the Discord. An invite link was shared in-channel, and the team noted they’re still actively working on it. ### Token sentiment check Discussion in 💬-discussion was dominated by token price concerns and frustration. While it wasn’t a “technical” day in Discord, it did surface a consistent theme: the community wants **more product shipping and clearer utility narratives** tied to real revenue. --- ## 4) Token Economics: AI16z Token + auto.fun ### What we heard this week - Token holders voiced concern about price performance and market cap levels, with some calling for market-making support or outreach to larger funds. ### Team perspective (utility without friction) In Discord, **shawmakesmagic** described a pragmatic approach to token utility: **accept whatever payment method users already have**, then use revenue to **buy back tokens**, rather than forcing token-only payments that add onboarding friction. This is a product-first stance: maximize adoption, then route value back to the token via buybacks. ### auto.fun watch There were **no explicit, confirmed auto.fun product milestones** in the provided activity this week. If you’re tracking auto.fun specifically, the best signal right now is indirect: the ecosystem is actively building the infrastructure (billing, paid routes, deployment paths) that makes downstream token-linked products more viable. *Reminder:* none of the above is financial advice—just a summary of what was discussed and shipped. --- ## 5) Coming Soon Here’s what the community should keep an eye on next: - **Eliza v3 nearing release:** The team indicated v3 is close to completion (no exact date shared yet). - **An application in final stages:** A near-finished app was mentioned as approaching completion—watch for release notes and onboarding docs when it lands. - **“degenai” updates imminent:** Framework updates involving **$degenai** were referenced as “coming soon.” - **HTN planning evolution:** Community discussion suggested an upgrade path from **HTN-lite → full HTN** (Hierarchical Task Networks) once Eliza v2 reaches beta—potentially shifting more decomposition into LLM planning while keeping triggers/steps stable. - **Fix needed:** The **Milady Play Store link** from the GitHub repo was reported as non-functional and needs a repair pass. --- ## 6) Resources ### Key Discord threads / references - Discord discussion channel (token sentiment, ELIZA history, scam ban, Hyperscape access): https://discord.com/channels/1253563208833433701/1253563209462448241 - ELIZA effect background: https://en.wikipedia.org/wiki/ELIZA_effect ### Notable PRs / technical breadcrumbs - GitHub PAT persistence + settings card for coding sub-agents: https://github.com/elizaOS/eliza/pull/7139 - Preserve explicit `REPLY` during race-discard handling: https://github.com/elizaOS/eliza/pull/7143 - Supabase/postgres Docker tag update (`17.6.1.112`): https://github.com/elizaOS/eliza/pull/7142 - Event-kind triggers wired to the runtime event bus (context for automation direction): https://github.com/elizaOS/eliza/pull/7116 ### Weekly snapshot reference - Prior weekly summary (Apr 19–25) for broader continuity: https://github.com/elizaOS/elizaos.news (community mirror) / internal weekly rollups referenced in project feeds