## Weekly Newsletter (2026-05-10) — ElizaOS Community **Week of 2026-05-03 to 2026-05-09** ### 1) Executive Summary This week was all about *stability + scale*: hardening the core runtime, expanding cloud monetization pathways, and smoothing how humans and agents collaborate. **Top milestones:** - **Secrets got a first-class home:** `@elizaos/vault` landed with cross-platform secrets storage and Settings UI integration, reducing plaintext key handling and improving self-host reliability—especially on headless Linux. - **Cloud monetization pipeline advanced:** support shipped for **monetized container app domains** and an **app-scoped chat endpoint**, moving Eliza Cloud closer to “agents that can ship paid apps end-to-end.” - **Monorepo consolidation continued:** Slack—one of the last major connector holdouts—was **migrated into the monorepo**, tightening release/version alignment across plugins. --- ### 2) Development Updates #### Core security & configuration - **`@elizaos/vault` (new):** A cross-platform secrets vault using OS keychains where available, with a headless-friendly fallback path. It’s wired into the Settings flow so sensitive plugin fields can be mirrored into encrypted storage instead of living only in `config.env`. - Notable follow-up fix: **skip OS keychain on headless Linux** to avoid native segfaults on agent boot. This is a big win for anyone running ElizaOS on servers without a desktop secret service. - Key PRs: **#7197**, **#7230** #### Cloud: monetized apps & domains - **Monetized container app domains:** Added Cloudflare-managed domain flows (check/buy/status/sync/verify), plus **app-scoped chat** at `/api/v1/apps/:appId/chat`, and improvements to container deployment status reconciliation. - Note: automated review flagged some **high-severity edge cases** (auth error classification, domain verification state, and credit reconciliation). Even though the feature is merged, expect hardening passes soon. - Key PR: **#7376** #### Connectors & plugin ecosystem - **Slack plugin migrated into monorepo:** `@elizaos/plugin-slack` now lives under `plugins/plugin-slack/` with actions/providers and a substantial unit test suite (120 tests). This reduces drift versus core’s rapidly evolving APIs. - Key PR: **#7375** - **X (Twitter) integration expectation change (community-confirmed):** Discord discussion clarified that the **X API is now required** for Twitter integration; pricing has improved, but builders should plan accordingly (and avoid relying on legacy login-only behavior). Documentation updates are still needed. #### Automations UX & n8n workflow loop A cluster of improvements landed to make automations feel less “LLM magic” and more “guided workflow building”: - Clarification round-trip route and UI improvements (including quick-pick clarifications). - Bug fixes around trigger deletion and free-form clarification handling. - Key PRs: **#7316**, **#7317**, **#7341**, **#7340**, **#7370**, **#7369**, plus plugin updates **#7373** / **#7372** #### Maintenance & stability - Dependency upgrades across the monorepo (React, TypeScript, Bun images, Cloud deps), plus CI reliability fixes (notably Windows installer smoke behavior). - Highlights: **#7322**, **#7277**, **#7232**, and multiple Cloud auth/session fixes (**#7324**, **#7327**, **#7361**, **#7367**, **#7377**) --- ### 3) Community Spotlight (Discord) Even with a quieter week in chat volume, there were a few standout moments worth surfacing: - **Builder showcase (full-stack agent system):** *harry346165* shared a completed client project with a modern production stack: Next.js 15 + React 19 + TypeScript + Tailwind/Shadcn, Prisma/Postgres, Redis, AWS Docker/Kubernetes, and agent orchestration using **LangGraph** and **CrewAI** (Claude 3.5 + GPT-4o), with RAG over Pinecone + Weaviate. If you’re looking for “what a real deployment looks like,” this is a strong reference point. - **Token market observation:** *cryptologos_00014* noted a divergence—**positive net fund flow while price declines**—suggesting potential manipulation or unusual price discovery dynamics. Not official analysis, but a useful signal to keep eyes on. - **X API requirement clarified:** *guru0* raised cost concerns; *odilitime* confirmed the **X API is required** now and pricing has become more reasonable than before. - **Hyperfy plugin disappearance:** *binarycookies* discovered the Hyperfy starter/plugin link returning **404** after recently being available. *odilitime* confirmed it was removed due to **version compatibility mismatches** with core, and provided a zip via DM as a temporary workaround. - **Open help request (unresolved):** *binarycookies* also asked for help implementing **movement** in a chat app with “bubble UI”—no solution posted yet. If you’ve shipped similar UI mechanics, this is an easy community win. - **Security note:** *dieantwoord1337* posted a “scam” warning without details—worth following up when context is available so mods can document patterns and prevention steps. --- ### 4) Token Economics (AI16Z token + auto.fun) There were **no official protocol-level announcements** in the provided data this week regarding **AI16Z token mechanics** or **auto.fun** product changes (no confirmed parameter updates, launches, or governance items referenced). What *did* surface: - Community market chatter flagged the **fund-flow vs. price** divergence as something to watch closely. Treat this as *informational*, not a call to action—consider using multiple data sources before drawing conclusions. If the team shares an official auto.fun roadmap or token update in Discord/GitHub next week, we’ll elevate it here. --- ### 5) Coming Soon Based on what surfaced in GitHub + Discord, expect follow-ups in these areas: - **Hyperfy plugin restoration:** either a compatibility update or a new officially maintained starter repo so it doesn’t vanish behind DMs. - **Docs refresh for X/Twitter integration:** clear guidance on *what requires the X API*, what endpoints are used, and cost expectations. - **Cloud monetization hardening:** tightening auth error handling, domain “verified” state sync, and credit reconciliation edge cases on the app-scoped chat endpoint. - **Community site reliability:** the `elizaos.github.io/summary/day` page was reported stuck since May 4—likely needs a pipeline/config fix. --- ### 6) Resources **Key PRs (GitHub):** - `@elizaos/vault` secrets vault + Settings integration — https://github.com/elizaos/eliza/pull/7197 - Headless Linux keychain segfault fix — https://github.com/elizaos/eliza/pull/7230 - Monetized container app domains (Cloud) — https://github.com/elizaos/eliza/pull/7376 - Slack plugin migrated into monorepo — https://github.com/elizaos/eliza/pull/7375 - Automations clarification roundtrip — https://github.com/elizaos/eliza/pull/7316 - Automations overview UX restoration — https://github.com/elizaos/eliza/pull/7317 **Notable Discord threads (for context & follow-up):** - Discussion channel (May 9): https://discord.com/channels/1253563208833433701/1253563209462448241 - Coders channel (May 9): https://discord.com/channels/1253563208833433701/1300025221834739744 **Open community action items:** - Hyperfy plugin compatibility + re-publish path (Discord surfaced; needs tracked issue/PR) - Movement mechanics help request (community help thread opportunity) - Clarify scam warning details so mods can document/mitigate patterns