# ElizaOS Weekly Newsletter (May 4–May 10, 2026) ## 1) Executive Summary This week was a big “platform hardening + ecosystem expansion” sprint across ElizaOS: - **Secrets got a major upgrade:** `@elizaos/vault` landed with **cross-platform secret storage** and **Settings UI integration**, moving the ecosystem closer to “production by default” credential handling rather than plaintext env/config sprawl. - **Cloud monetization capabilities expanded:** Eliza Cloud added the building blocks for **monetized container apps with managed domains**, including app-scoped chat endpoints and Cloudflare domain flows—unlocking a more end-to-end path from “agent idea” to “deployed product.” - **Connector maturity improved:** The **Slack plugin was migrated into the monorepo**, reducing fragmentation and making it easier to ship consistent plugin updates alongside core changes. Alongside these, the Automations experience (especially the n8n workflow path) kept getting smoother thanks to clarification “roundtrips” and UI improvements. --- ## 2) Development Updates ### Security & Secrets: `@elizaos/vault` A standout feature this week is the new **`@elizaos/vault`** package and wiring through the runtime + Settings UI: - **Encrypted secrets at rest** (AES-256-GCM) with a master key managed by the OS keychain when available. - **Headless-friendly behavior**: fixes landed to avoid OS keychain access on headless Linux environments where native keyring backends can cause crashes. - **Settings UI flow** now supports vault-backed saving/revealing of credentials, plus better heuristics for identifying “primary credentials” (API keys, bot tokens, private keys, etc.). Why it matters: if you’re deploying agents on servers, rotating keys, or managing multiple providers, this is a foundational step toward safer, less brittle ops. ### Cloud: Monetized Apps + Managed Domains Eliza Cloud shipped support for **monetized container app domains**, including: - **App-scoped chat** (`/api/v1/apps/:appId/chat`) that can incorporate monetization metadata and provider routing. - **Managed domain flows** (check/buy/status/sync/verify) with Cloudflare integration. - Improvements to **container deployment status reconciliation** so containers don’t remain stuck in “deploying” when they’re actually healthy. Note: automated review surfaced some **high-severity edge cases** (auth error classification, domain verification state sync, credit reconciliation). Even though the feature path is now in place, we should expect quick follow-up patches to harden billing/auth correctness under failures and race conditions. ### Automations + n8n: Clarifications Become a Real UX Workflow generation has been steadily moving from “cool demo” to “repeatable UX”: - A **clarification roundtrip route** was added so the host/UI can properly handle `needs_clarification` responses. - UI improvements introduced **quick-pick clarification** buttons, plus fixes to the automation trigger deletion path and better handling of **free-form clarifications** (not every clarification maps cleanly to a `paramPath`). Net result: fewer dead ends, clearer prompts, and a much more “guided” creation loop when generating workflows. ### Connectors: Slack Joins the Monorepo `@elizaos/plugin-slack` was migrated into the main repository alongside other connector plugins. This brings: - A richer action/provider surface area (message operations, channel operations, workspace info, etc.). - A large unit test suite imported with it, which should help prevent regressions as core types evolve. If Slack is part of your agent deployment strategy, this migration is good news: it reduces lag between core changes and plugin compatibility fixes. ### CI/Build Reliability A few changes this week focused on keeping `develop` shippable: - Windows CI stability improvements (handling odd installer exit codes). - Ongoing dependency upgrades across the stack (TypeScript, SDKs, build tooling), with targeted fixes when version mismatches cause resolver issues. --- ## 3) Community Spotlight (Discord) Even on a relatively quiet chat week, a few themes stood out: - **Cost transparency for running agents on X (Twitter):** In `#coders`, the community shared real-world ops numbers: running an Eliza Twitter bot reportedly dropped from **~$100/month historically to ~$10/month** now, heavily dependent on configuration—especially the **volume of replies**. - **Security awareness signals:** Members flagged a **scam warning**, and one user asked whether something may have been **compromised**. There wasn’t enough context in-channel to conclude anything, but it’s a good reminder: if you see suspicious links, impersonation attempts, or token/key requests, surface them early and share details so mods/devs can respond. - **Builders introducing themselves (and showing work):** - A full-stack + AI project showcase highlighted a modern production stack (Next.js 15, React 19, TypeScript, Prisma/Postgres, Redis, Kubernetes on AWS) plus agent frameworks (LangGraph/CrewAI) and RAG using Pinecone/Weaviate. - Several new dev intros (AI + full-stack, autonomous blockchain agents, FastAPI/Next.js) indicate steady inflow of collaborators looking for real builds rather than hype. --- ## 4) Token Economics (AI16z & auto.fun) There were **no official protocol-level announcements** in the provided channels this week specifically detailing changes to **AI16z token economics** or new **auto.fun** releases. What we *did* see: - A community market observation noted a divergence: **positive net fund flow while price declines**, interpreted as a potential manipulation signal. Treat this as community commentary—not definitive analysis. - Continued casual community presence from traders/builders, but no concrete parameter updates (emissions, fees, buybacks, or launch mechanics) were discussed in the captured logs. If you want token updates to be more visible in future newsletters, consider posting: governance links, official changelogs, or auto.fun feature notes directly into Discord for easy aggregation. --- ## 5) Coming Soon Here’s what to watch for next week based on what shipped and what’s now “unblocked”: - **Cloud hardening follow-ups**: expect rapid iteration around error handling (auth status codes), domain verification state, and billing/credit reconciliation edge cases. - **Slack connector reliability pass**: now that the plugin is in the monorepo, it’s easier to ship improvements (especially around robustness on Slack API hiccups). - **More guided automation flows**: the clarification UX is now “real”—the next step is likely broader connector enumeration, richer context injection, and fewer cases where users need to manually patch a generated workflow. --- ## 6) Resources **Key Pull Requests (Core + Cloud + Plugins):** - `@elizaos/vault` + Settings integration: https://github.com/elizaos/eliza/pull/7197 - Headless Linux keychain crash fix (vault/confidant): https://github.com/elizaos/eliza/pull/7230 - Cloud monetized container app domains: https://github.com/elizaos/eliza/pull/7376 - Slack plugin migrated into monorepo: https://github.com/elizaos/eliza/pull/7375 - n8n clarification roundtrip route: https://github.com/elizaos/eliza/pull/7316 - Automations clarification quick-pick UI: https://github.com/elizaos/eliza/pull/7341 - Free-form clarification handling fix: https://github.com/elizaos/eliza/pull/7370 **Notable Discord threads (for context and follow-up):** - Discussion channel (introductions, community chat): https://discord.com/channels/1253563208833433701/1253563209462448241 - Coders channel (Twitter bot cost, security concerns): https://discord.com/channels/1253563208833433701/1300025221834739744