# ElizaOS Weekly Newsletter (Apr 27, 2026 → May 3, 2026) ## 1) Executive Summary **1) Core stability leveled up across real-world deployments.** This week focused heavily on “make it not break” improvements: headless Linux segfaults were eliminated via a keyring/D‑Bus fallback, Telegram bot reliability issues were addressed (including message loss due to polling races), and multiple CI / workflow cleanups landed to keep the repo maintainable as the surface area grows. **2) Security and UX took a meaningful step forward with the Secrets Vault.** A major milestone merged: **`@elizaos/vault`**, providing cross-platform secrets management with OS keychain integration (and a passphrase fallback for headless servers). This moves the ecosystem away from plaintext config storage and toward a more professional operational baseline. **3) Automations (n8n) got closer to a true “NL → workflow” roundtrip.** The host now supports clarification-aware workflow generation and resolution, plus a Discord **ConnectorTargetCatalog** so the UI can present real guild/channel “quick picks” instead of asking users to guess IDs. --- ## 2) Development Updates (Technical) ### Runtime & Infrastructure - **Fixed headless Linux hard crashes (segfaults) in secrets/keyring paths** by adding a D‑Bus detection fallback for environments without a Secret Service agent. This is especially important for self-hosters and CI runners where “no desktop session” is the norm. - Merged: **`fix(vault, confidant): skip OS keychain on headless Linux…`** ([elizaos/eliza#7230](https://github.com/elizaos/eliza/pull/7230)) - **Repository maintainability improvements** landed via a large consolidation that brings Cloud + plugins into the main repo while removing legacy Rust/Python components. Expect some churn in paths and workflows, but the goal is a simpler, more unified developer experience. - Merged: **“add cloud and plugins, remove rust and python”** ([elizaos/eliza#7235](https://github.com/elizaos/eliza/pull/7235)) ### Authentication & Client Architecture - **Standardized client architecture** by merging duplicate client definitions into a canonical **ElizaClient**, eliminating confusing “method missing at runtime” behaviors that arise when prototype augmentation hits a class that never gets instantiated (a subtle but nasty failure mode). - **Improved SIWE reliability in Cloud contexts** by fixing domain/host resolution so production environments don’t accidentally behave like `localhost`. - Merged: **SIWE domain fix** ([elizaos/eliza#7327](https://github.com/elizaos/eliza/pull/7327)) - Also merged: **SIWE unblocking while cache is disabled** ([elizaos/eliza#7324](https://github.com/elizaos/eliza/pull/7324)) - **Codex CLI token recognition improved** (detection updated to match modern token shapes), reducing false “install required” states and improving auto-enablement of OpenAI/Codex paths in settings. ### Automations & n8n Workflow UX - **Clarification-aware workflow generation is now real on the host side.** When the n8n draft indicates missing parameters, the API can short-circuit with `needs_clarification`, return structured clarification requests, and accept resolutions to patch & deploy the draft. - Merged: **n8n clarification roundtrip route** ([elizaos/eliza#7316](https://github.com/elizaos/eliza/pull/7316)) - **Discord ConnectorTargetCatalog service added.** This surfaces real Discord guild/channel context (with caching) so UIs can offer accurate pickers during workflow setup. - Merged: **connector-target-catalog service (Discord)** ([elizaos/eliza#7315](https://github.com/elizaos/eliza/pull/7315)) - **Automations Overview UX restored** by bringing back the “NL-first hero centerpiece,” keeping the product aligned with the natural-language-first promise of ElizaOS. - Merged: **Automations hero centerpiece restoration** ([elizaos/eliza#7317](https://github.com/elizaos/eliza/pull/7317)) ### Messaging / Telegram Reliability - Multiple Telegram issues were addressed this week, including **launch errors** and **silent message loss** rooted in polling race conditions. If you’ve felt Telegram bots were “randomly ignoring messages,” this is the class of bug that causes that experience. --- ## 3) Community Spotlight (Discord) ### Philosophy, roadmap, and expectations (a real conversation) A major discussion unfolded around token price performance and communication expectations. **Shaw** reiterated a consistent stance: token holders shouldn’t be treated as traditional investors, and **buybacks require revenue**—pushing buybacks before products generate cashflow is framed as existentially harmful. The message: *build revenue-generating products first; token mechanics follow sustainable revenue.* **odilitime** provided a constructive counterbalance: rather than escalating moderation, make the roadmap and plan easier to understand. A **visual roadmap** was shared and coordinated for reposting in announcements, with plans to refresh the **GitHub roadmap text** as well. ### Builders building - **marianodim** shared they’re building a **spot trading agent** on ElizaOS (targeting SOL, SUI, and additional tokens), aiming to test over the next few weeks and publish ~**1–2 trading signals/week**. This is exactly the kind of “builder energy” the framework is meant to attract. - **sentient_dawn** resurfaced a high-signal technical theme: **memory rot in long-lived agents** (often showing up after ~3 months). They described a mitigation approach (freshness gates, reconciliation passes, periodic diffs, re-embedding under current ontology) that’s already proven in production—worth paying attention to if you’re deploying agents that must stay correct over time. ### Small but practical: spam filter workaround Strict anti-spam filtering in Discord is blocking some URLs. A workaround discussed: wrap URLs in backticks like `` `https://domain.com` `` to reduce false positives (until a better allowlist/UX is implemented). --- ## 4) Token Economics (AI16z token + auto.fun) ### Where things stand this week - The most material “token economics” update wasn’t a mechanism change—it was **clarity on sequencing**: revenue first, then potential buybacks. The team continues to emphasize that sustainable token support depends on shipping products that people pay for. - Community concerns surfaced about **price decline** and unanswered items (e.g., the “Babylon airdrop” question was raised in discussion but not resolved in the provided logs). If you’re tracking commitments, this is a good moment to request a crisp status update via the roadmap refresh effort. ### auto.fun / launchpad ecosystem notes While there weren’t deep technical release notes for **auto.fun** in the provided data, Shaw did mention ecosystem momentum: **Shadow’s “waifu.fun” launchpad** (with `four.meme` and `flap` contracts) is launching “powered by the new Eliza.” Treat this as a signal that distribution/launch surfaces are being lined up alongside V3/Cloud/Milady. --- ## 5) Coming Soon - **ElizaOS V3 launch**: repeatedly referenced as “soon,” with PR/marketing planning underway. - **Eliza Cloud**: infrastructure is described as “set up to be profitable,” and Cloud auth reliability work is actively landing. - **Milady app**: described as nearly ready and expected to be a **revenue driver**. - **Clean Architecture migration (Cloud)**: ongoing work (WIP) aims to resolve Worker-context pitfalls (like request-bound I/O constraints) more systematically. - In progress: **Clean Architecture migration (WIP)** ([elizaos/eliza#7336](https://github.com/elizaos/eliza/pull/7336)) - **Clarification UI**: backend clarification loop exists; UI work to render and resolve clarifications smoothly is still anticipated. - **Plugin expansion**: multiple ExergyNet “verified compute” related plugin additions are in-flight. --- ## 6) Resources (Links) ### Key Pull Requests / Fixes - `@elizaos/vault` Secrets Vault + Settings UI integration: [elizaos/eliza#7197](https://github.com/elizaos/eliza/pull/7197) - Headless Linux segfault fix (keyring / D‑Bus fallback): [elizaos/eliza#7230](https://github.com/elizaos/eliza/pull/7230) - n8n clarification roundtrip route (generate → needs_clarification → resolve): [elizaos/eliza#7316](https://github.com/elizaos/eliza/pull/7316) - ConnectorTargetCatalog (Discord context for pickers): [elizaos/eliza#7315](https://github.com/elizaos/eliza/pull/7315) - SIWE domain resolution fix on Worker: [elizaos/eliza#7327](https://github.com/elizaos/eliza/pull/7327) - Repo consolidation (cloud + plugins; remove rust/python): [elizaos/eliza#7235](https://github.com/elizaos/eliza/pull/7235) ### Discord Discussions (for context) - Token economics / roadmap / V3 “soon” discussion thread: https://discord.com/channels/1253563208833433701/1253563209462448241 ### Repos highlighted by Shaw (trading / strategy direction) - `plugin-auto-trader` (repo shared in Discord) - `plugin-social-alpha` (trench-signal profitability analysis; social copy-trading potential) - `spartan` (project shared as part of the trading stack direction) --- If you’re building this week: the biggest immediate “quality of life” wins are (1) adopting the Vault flow for secrets, and (2) trying the n8n clarification-enabled automation path—those two changes reduce the most common self-hosting and workflow-generation friction points.