# ElizaOS Weekly Newsletter (Apr 27 – May 3, 2026) ## 1) Executive Summary This week was a “make it run everywhere, safely” kind of push—plus a few big community moments: 1. **Secrets handling leveled up across platforms.** The new **`@elizaos/vault`** landed upstream with Settings UI integration, giving ElizaOS a first-class, cross-platform secrets vault (OS keychain when available, passphrase fallback for headless servers). This is a major step toward safer self-hosting and cleaner operational hygiene. 2. **Self-hosted + mobile/desktop connectivity got meaningfully smoother.** A large PR improved **CORS, bearer auth flows, and cross-platform build reliability** (browser, Capacitor mobile, Electrobun desktop), reducing friction for anyone running ElizaOS outside a single local machine. 3. **Core infrastructure stabilized under real-world constraints.** Multiple fixes targeted critical breakpoints: **ESM-only compatibility across plugins**, a **headless Linux segfault** in keychain access, and **Windows Server 2025 CI packaging quirks**. The result: fewer “works on my machine” surprises. --- ## 2) Development Updates (Technical) ### Security & Ops: Vault + headless stability - **Merged: `feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration`** This introduces encrypted-at-rest secret storage, OS keychain support (macOS/Windows/Linux where available), and a Settings UI flow that mirrors sensitive values into the vault rather than leaving them as plaintext configuration. **PR:** https://github.com/elizaos/eliza/pull/7197 - **Merged: headless Linux segfault prevention for keychain access** Some headless Linux hosts (no D-Bus Secret Service) could hard-crash at the native layer. The fix bypasses unsafe keychain paths and falls back to passphrase-derived keys, preventing process-level crashes. **PR:** https://github.com/elizaos/eliza/pull/7230 ### Self-hosting & cross-platform clients - **Merged: CORS + bearer auth + cross-platform build fixes** Highlights include `ELIZA_ALLOWED_ORIGINS` support, better Capacitor origin handling, bearer-token plumbing via `fetchWithCsrf`, and multiple packaged-build fixes (Electrobun, Android templates, registry directory presence). This improves the “remote runtime” experience across browser/mobile/desktop. **PR:** https://github.com/elizaos/eliza/pull/7212 ### Build system modernization & plugin compatibility - **ESM alignment work completed across multiple plugins** Build failures in `plugin-ollama`, `plugin-openai`, `plugin-openrouter`, and `plugin-pdf` were resolved by removing incompatible CommonJS bundles and aligning with the **ESM-only** direction of `@elizaos/core`. - **Jupiter plugin migrated to the new endpoint + API key requirement** `plugin-jupiter` moved to `api.jup.ag` with mandatory API key auth—important for anyone relying on Solana routing/quote flows in agents. - **Windows CI reliability improved (packaging smoke tests)** The CI now tolerates bogus non-zero Inno Setup exit codes on Windows Server 2025 by verifying installed artifacts before failing. **PR:** https://github.com/elizaos/eliza/pull/7232 ### Known pain points (in progress) Telegram is the biggest hot spot right now, with multiple open issues: - **Dual-polling race condition causing silent message loss** when both a wrapper and `@elizaos/plugin-telegram` poll the same bot token. **Issue:** https://github.com/elizaos/eliza/issues/7245 - Token passing failures, Bun runtime issues on `bot.launch()`, and other integration bugs were also flagged (#7240, #7241) and are actively being worked. Also in-flight: - **Large repo structure consolidation PR** (cloud + plugins added, rust/python removed). Expect churn here if/when it lands. **PR (open):** https://github.com/elizaos/eliza/pull/7235 - **Discord auto-reply env var standardization** is being coordinated in `plugin-discord` (WIP PR referenced as `#50` in the daily summary). --- ## 3) Community Spotlight (Discord Highlights) ### Agents in the wild: trading + robotics - **Spot trading agent announcement:** community member **marianodim** shared they’re building a spot trader on ElizaOS covering **SOL, SUI, and five additional tokens**, combining multiple strategies plus contextual signals. Testing is planned over the next few weeks, targeting **1–2 trading signals/week**. (As always: experiment carefully; markets are adversarial and strategy evaluation takes time.) - **Robotics demo:** **shawmakesmagic** showed Eliza integrated with a **Unitree robot**, taking commands to walk around—an encouraging reminder that ElizaOS isn’t just chat; it can be a control plane for embodied agents. ### Deep technical discussion: “memory rot” in long-lived agents - **sentient_dawn** shared production learnings on a failure mode that emerges after ~3 months: retrieval-only memory systems (RAG/vector stores) can accumulate **stale facts** that the agent continues to treat as true, causing unseen drift until humans notice contradictions. They proposed (and implemented) a mitigation: a **reconciliation pass** with freshness gates, periodic cross-source diffs, and re-embedding under the current ontology. If you’re building agents meant to live for months, this is one of the most practically useful discussions of the week. ### Ecosystem clarity & org momentum - **odilitime** posted a helpful positioning comparison: **ElizaOS as the “Linux” of agentic frameworks** (open-source, developer-controlled) vs consumer platforms like Orbofi (marketplace/app-store-like). - An **“eliza army steering”** group was mentioned for partners who want to help coordinate momentum—interested folks were invited to request access. - Reminder from ops side: **exchange listing discussions are NDA-bound**, so don’t expect public play-by-plays. --- ## 4) Token Economics (AI16z & auto.fun) No formal token parameter changes were announced this week, but a few ecosystem notes matter: - **Shaw discussed project funding constraints candidly**—highlighting how token value collapses impacted team retention and why some development is being funded via personal savings right now. This context helps explain the strong emphasis on shipping core runtime capabilities (v3, cloud monetization) rather than short-term token “utility theater.” - **Exchange listing chatter remains restricted** due to NDAs (community reminder). - Community interest in **auto.fun** continues (we saw “auto.fun enjoyer” activity), but there were **no concrete auto.fun release notes** in the provided weekly data. --- ## 5) Coming Soon A few near-term things to watch (and potentially help with): - **Telegram integration hardening:** resolving Bun `launch()` issues, token bridging, and—most critically—eliminating dual-poller races that drop messages. - **Repo consolidation work (PR #7235):** if merged, expect follow-up tasks for docs, build tooling, and contributor workflows. - **ElizaOS v3 direction (from Discord):** Shaw described v3 as a full application runtime across devices/platforms, social integrations (even iMessage), workflow creation, and monetization via Eliza Cloud. Expect more surfaced artifacts as this moves from architecture talk to public implementation details. - **Long-lived memory reliability:** the “memory rot” reconciliation approach is likely to inspire concrete patterns/plugins—this is a good area for contributors to prototype reference implementations. --- ## 6) Resources (Links) **Key Pull Requests** - Vault + Settings integration: https://github.com/elizaos/eliza/pull/7197 - Self-hosted CORS + bearer auth + build fixes: https://github.com/elizaos/eliza/pull/7212 - Headless Linux keychain segfault fix: https://github.com/elizaos/eliza/pull/7230 - Windows Server 2025 CI packaging fix: https://github.com/elizaos/eliza/pull/7232 - Repo consolidation (open): https://github.com/elizaos/eliza/pull/7235 **Key Issue** - Telegram dual-polling race / silent message loss: https://github.com/elizaos/eliza/issues/7245 **Discord References (weekly highlights)** - Trading agent build + partner steering group (May 2): https://discord.com/channels/1253563208833433701/1253563209462448241 - Orbofi vs ElizaOS positioning, robotics demo, memory rot discussion (May 1): https://discord.com/channels/1253563208833433701/1253563209462448241 --- If you’re looking for a high-impact way to contribute next week: jump into **Telegram reliability**, help document **vault operational patterns** (especially headless deployments), or prototype a **memory reconciliation** utility that others can adopt.