# ElizaOS Weekly Newsletter (May 5–11, 2026) ## 1) Executive Summary This week was all about **making ElizaOS easier to run securely, easier to integrate, and more ready for real monetized deployments**: 1. **Secrets handling took a big leap forward** with the new **cross-platform `@elizaos/vault`** and Settings UI wiring. This moves the ecosystem toward “secure-by-default” credential storage (OS keychain where available, passphrase fallback when not). 2. **Eliza Cloud’s monetized app pipeline advanced materially**, adding production paths for **app-scoped chat**, **managed domains**, and container deployment lifecycle improvements—key building blocks for shipping agent-powered apps that can charge, authenticate, and run reliably. 3. **Connector ecosystem consolidation continued**, with **Slack migrated into the monorepo** and ongoing improvements to **automation clarification flows** (n8n) that reduce friction from “LLM generated a workflow… but needs one missing detail.” --- ## 2) Development Updates (Technical) ### Secure configuration & credential management - **`@elizaos/vault` landed with Settings UI integration**: encrypted-at-rest secret storage with OS keychain support (macOS Keychain / Windows Credential Manager / Linux Secret Service), plus headless-friendly passphrase options. - PR: **`feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration`** ([#7197](https://github.com/elizaos/eliza/pull/7197)) - **Critical stability fix for headless Linux**: keychain access can segfault when no Secret Service is available; the runtime now **skips OS keychain on headless Linux** to prevent hard crashes. - PR: **`fix(vault, confidant): skip OS keychain on headless Linux…`** ([#7230](https://github.com/elizaos/eliza/pull/7230)) - **Runtime hygiene fix**: agent config loading now **skips vault sentinel values** so env application doesn’t leak placeholder refs into runtime state. - PR: **`fix(agent): skip vault sentinels in applyConfigEnvToProcessEnv`** ([#7368](https://github.com/elizaos/eliza/pull/7368)) ### Automations / n8n workflow generation: better clarification UX A lot of energy continues to go into making automation generation feel interactive instead of brittle: - **Clarification “roundtrip” support** so the host/UI can properly handle LLM responses that request missing parameters. - PR: **`feat(n8n): clarification roundtrip route`** ([#7316](https://github.com/elizaos/eliza/pull/7316)) - **UI quick-picks** for clarifications (reducing manual typing and back-and-forth). - PR: **`feat(automations): clarification quick-pick UI`** ([#7341](https://github.com/elizaos/eliza/pull/7341)) - **Bug fix**: clarification resolution now supports **free-form clarifications** (not every clarification maps neatly to `paramPath`). - PR: **`fix(automations): support free-form clarifications in resolve flow`** ([#7370](https://github.com/elizaos/eliza/pull/7370)) - **Parser resilience**: tolerate prose appended after JSON in workflow responses. - PR: **`fix(n8n-workflow): tolerate prose-trailed JSON…`** ([#7369](https://github.com/elizaos/eliza/pull/7369)) ### Cloud: monetized apps, managed domains, and auth hardening - **Monetized container app domains + app-scoped chat**: a major Cloud feature drop that touches app auth callbacks, Cloudflare managed domain flows, and container deployment reconciliation. - PR: **`feat(cloud): support monetized container app domains`** ([#7376](https://github.com/elizaos/eliza/pull/7376)) - **SIWE fixes** and environment correctness on Cloudflare Worker deployments (domain/host resolution, cache hotfix bypass): - PRs: [#7324](https://github.com/elizaos/eliza/pull/7324), [#7327](https://github.com/elizaos/eliza/pull/7327) - **Frontend stability fixes** in Cloud login flows (CLI login deadlocks, render loops): - PRs: [#7367](https://github.com/elizaos/eliza/pull/7367), [#7377](https://github.com/elizaos/eliza/pull/7377), [#7374](https://github.com/elizaos/eliza/pull/7374) ### Connectors: Slack joins the monorepo - **Slack plugin migration** into `elizaos/eliza` monorepo, bringing actions/providers/tests along with it and aligning to current alpha APIs. - PR: **`feat(slack): migrate plugin-slack into the monorepo`** ([#7375](https://github.com/elizaos/eliza/pull/7375)) ### Build & dependency maintenance highlights - **Large consolidation PR**: cloud + plugins added, legacy rust/python removed (repo architecture cleanup). - PR: [#7235](https://github.com/elizaos/eliza/pull/7235) - **Dependency and tooling updates** across AI SDK packages, React, TypeScript, and CI workflows (numerous Renovate/Dependabot PRs). --- ## 3) Community Spotlight (Discord) ### Multi-agent orchestrator testing proposal (and a clean ops pattern) A developer (**rma_bot**) proposed testing a **Python multi-agent orchestrator** built with `claude-agent-sdk`, featuring: - **A2A-protocol read-only research agent** - Tooling via MCP integrations: **Tavily**, **DuckDuckGo**, **fetch**, **arXiv** - Safe operational constraints: **sandbox channel**, **read-only**, **no DMs**, responds only to **@mentions** This is the kind of “controlled blast radius” deployment approach that scales well for community testing. **odilitime** stepped in to help with **OAuth invite/whitelist setup via DM**, unblocking next steps. - Discussion (coders): https://discord.com/channels/1253563208833433701/1300025221834739744 ### Practical ops: bot cost reality check In #coders, folks compared notes on running an Eliza Twitter bot. Reported costs have dropped significantly over time—from **~$100/month to ~$10/month**, largely driven by reply volume and configuration. This is a helpful baseline for anyone budgeting experiments. - Discussion context: May 10 Discord coders thread (summary captured in provided logs) ### Community introductions (skills you can tap) A wave of intros in #discussion surfaced community strengths in: - **Autonomous agents** (LangChain / AutoGen / CrewAI), multimodal + trading bots - **Next.js 15 / React 19 / TypeScript** + LangGraph - Deep ML production experience (GANs, PINNs, SNNs, etc.) - PM-style coordination for LLM + RAG systems If you’re forming a working group, this is a good week to scroll back and connect with people aligned to your roadmap. - Discussion: https://discord.com/channels/1253563208833433701/1253563209462448241 ### Unanswered but important: token support question One community member raised concern about whether the **ElizaOS token** is still actively supported, citing a social signal (bio change). The thread did **not** receive an official response in-channel—see Token Economics below for how we’re treating this in the newsletter. --- ## 4) Token Economics (AI16z token & auto.fun) No official on-record announcements or changelog entries about **AI16z token** mechanics or **auto.fun** shipped in the provided sources for this week. What *did* happen: community sentiment flagged uncertainty about token support. If you’re making ecosystem decisions based on token/alignment signals, the best next step is to **request an official statement** (or link to one) in a dedicated channel/thread so it doesn’t get lost in general chat. Separately, it’s worth noting that the week’s engineering direction (Cloud monetization paths, managed domains, secure secrets) is consistent with building **sustainable, revenue-capable infrastructure**—even if token-specific updates weren’t published here. --- ## 5) Coming Soon Here’s what to watch next based on this week’s momentum: - **Sandbox deployment of the A2A research agent** on Discord (OAuth/whitelist + permissions), plus potential **port into the Eliza framework** if the experiment proves valuable. - **Follow-up hardening for Cloud monetized chat + domains** (several reviews flagged edge cases around auth error classification and domain verification state—likely to see patches soon). - **Slack connector real-workspace smoke testing** and resilience improvements (especially around message handling error paths). - **Security follow-ups**: a brief “was something compromised?” question appeared in Discord without resolution—expect either clarification or a checklist-style response if the concern is validated. --- ## 6) Resources (Links) ### Discord - Multi-agent orchestrator sandbox request (coders): https://discord.com/channels/1253563208833433701/1300025221834739744 - Community intros + token concern (discussion): https://discord.com/channels/1253563208833433701/1253563209462448241 ### Key PRs (GitHub) - Vault + Settings UI integration: [#7197](https://github.com/elizaos/eliza/pull/7197) - Headless Linux keychain segfault fix: [#7230](https://github.com/elizaos/eliza/pull/7230) - Cloud monetized domains + app-scoped chat: [#7376](https://github.com/elizaos/eliza/pull/7376) - Slack plugin migrated into monorepo: [#7375](https://github.com/elizaos/eliza/pull/7375) - n8n clarification roundtrip: [#7316](https://github.com/elizaos/eliza/pull/7316) - Automations clarification quick-picks: [#7341](https://github.com/elizaos/eliza/pull/7341) - Free-form clarification support: [#7370](https://github.com/elizaos/eliza/pull/7370) - Workflow JSON tolerance fix: [#7369](https://github.com/elizaos/eliza/pull/7369)