# ElizaOS Weekly Newsletter (May 3–May 9, 2026)

## 1) Executive Summary

This week was a solid “infrastructure + ecosystem readiness” push across ElizaOS:

- **Cloud consolidation and cost optimization landed.** ElizaCloud was consolidated into the main monorepo at **`github.com/elizaOS/eliza`**, alongside a shift away from Vercel toward **cheaper container-based hosting options**—a meaningful step toward sustainable ops and easier contributions.
- **Monetization and secure deployment pathways advanced.** Support for **monetized container app domains** shipped, expanding the “build → deploy → monetize” story for agent-built apps running on ElizaCloud infrastructure.
- **Developer experience and reliability improved across the stack.** Notable progress included a cross-platform **secrets vault** integrated into the Settings UI, continued hardening for Linux/headless environments, and UX fixes for the Automations workflow (especially the new clarification loop).

## 2) Development Updates (Core + Cloud + Plugins)

### Core platform & repo structure
- **Monorepo hardening & simplification:** A large consolidation effort brought more Cloud + plugins into the main repo and removed legacy Rust/Python components from certain paths, reducing drift and making the repo easier to reason about (see PR **#7235**).
- **Cross-platform secrets management shipped:** The new **`@elizaos/vault`** provides encryption-at-rest for sensitive config and integrates directly with the Settings UI. It supports OS keychains (with headless Linux fallbacks) and introduces vault-first reveal behaviors (PR **#7197**).  
  - Follow-up reliability work also ensured headless Linux environments don’t segfault when secret services aren’t available (PR **#7230**).

### ElizaCloud: app monetization + domains
- **Monetized container app domains:** Cloud now supports app-scoped chat endpoints, Cloudflare-managed domain flows (check/buy/status/sync/verify), and deployment-monitor reconciliation so containers don’t get stuck in “deploying” (PR **#7376**).  
  - Note: automated review flagged some **auth + reconciliation edge cases** in this area previously; if you’re building on the newest Cloud endpoints, keep an eye out for follow-up fixes and test carefully in staging.

### Automations / n8n workflow UX
A lot of “make automations feel complete” work came together:
- **Clarification roundtrip route:** the host now properly handles clarification requests emitted by the n8n-workflow path (PR **#7316**).
- **Clarification quick-pick UI:** clarification prompts can be resolved via inline button picks in the Automations view (PR **#7341**).
- **Bug fix:** deletion flows in the Automations UI now pass the right trigger name from the detail pane (PR **#7340**).
- **Robust parsing fixes:** n8n workflow response parsing now tolerates trailing prose after JSON (PR **#7369**), and clarification resolution supports free-form clarifications (PR **#7370**).

### Plugin ecosystem
- **Slack connector moved into the monorepo:** `@elizaos/plugin-slack` has been migrated under `plugins/plugin-slack/`, bringing actions/providers/tests into the unified build and release pipeline (PR **#7375**).
- **ElizaCloud plugin fix:** improved fence stripping/deduping of responses output (PR **#7371**).

### Docs / website infra
- A new PR in **`elizaos.github.io`** proposes adding an `ImportMetaENV` interface to improve environment variable handling in the docs site’s Next.js configuration (work in progress; referenced in the May 7 dev activity summary).
- Community also reported that **`elizaos.github.io/summary/day`** has been stuck since May 4—likely a pipeline/config issue still under investigation.

## 3) Community Spotlight (Discord Highlights)

### Twitter/X integration: API requirement clarified
A key clarification emerged for builders shipping social bots: **the X (Twitter) API is now required** for Twitter integration. The good news: recent pricing revisions were reported as **more affordable than before**, easing concerns for smaller projects that only need posting functionality. This change likely impacts older “login method” expectations—documentation updates were explicitly requested.

### Hyperfy plugin: missing repo + version mismatch
A real-world integration hiccup surfaced when **binarycookies** discovered the Hyperfy starter plugin link returning **404**, after it had been available days earlier. Investigation pointed to **version mismatches** between the plugin and current ElizaOS core.  
- **odilitime** confirmed the plugin needs updates and suggested using a **coding agent** to help repair compatibility.
- As a temporary unblock, a **zip of the plugin** was shared via DM while a proper fix is pending.

### New builder intro + community momentum
- **itssowenn4462** introduced themselves as an AI Full Stack Engineer (8+ years in agents, automation workflows, multimodal AI) and is looking to connect with builders—say hi if you’re working on agents-in-production.
- Shoutout to the community member whose **elizaOK** project was selected for **Fourmeme Hackathon Top 20** (and saw a last-call push for votes).
- Ongoing **scam warnings** circulated—appreciate everyone staying vigilant and helping keep the community safe.

## 4) Token Economics (AI16z + auto.fun)

Token talk was present but mostly practical and builder-oriented this week:

- **Cross-chain bridging discussion:** community members discussed bridging tokens between **BSC and Solana**, with **Wormhole** and **debridge** suggested as options. If you’re moving assets for testing or liquidity operations, double-check contract addresses and beware of impersonators.
- **Payments milestone:** ElizaOS and **DegenAI** were added as **default payment methods for x402 routes**, a meaningful step toward standardized payment rails inside the ecosystem.
- **auto.fun + AI16z:** no major shipped changes were surfaced in the provided discussions this week. If you’re tracking releases closely, keep an eye on announcements and product threads as the payments and monetization layers mature.

## 5) Coming Soon (What to Watch Next)

- **Hyperfy plugin restoration:** expect work to re-publish or re-home the plugin and align it with the current core versioning. If you rely on it, consider pinning versions or keeping a local copy until it’s back in-repo.
- **Docs clarification for X API:** documentation updates are needed to reflect the new requirement and current pricing reality.
- **Summary pipeline fix:** the stuck daily summary page likely needs CI or account/config remediation; once restored, it should improve project visibility for non-Discord community members.
- **Model work (eliza-1):** ongoing training efforts continue using **Qwen** as a base, with performance improvements like speculative decoding and quantization techniques discussed by Shaw—more updates likely as the housekeeping and releases progress.

## 6) Resources (Links & Pointers)

**Discord threads (May 5–7):**
- Twitter/X API requirement + Hyperfy plugin troubleshooting  
  - https://discord.com/channels/1253563208833433701/1300025221834739744  
  - https://discord.com/channels/1253563208833433701/1253563209462448241

**Key GitHub PRs mentioned this week:**
- `@elizaos/vault` secrets vault + Settings UI integration: **elizaos/eliza PR #7197**  
- Headless Linux keychain segfault fix: **elizaos/eliza PR #7230**  
- Monetized container app domains (Cloud): **elizaos/eliza PR #7376**  
- Migrate Slack plugin into monorepo: **elizaos/eliza PR #7375**  
- n8n clarification roundtrip route: **elizaos/eliza PR #7316**  
- Automations clarification quick-pick UI: **elizaos/eliza PR #7341**

**Operational note:**
- Reported issue: daily summary page stuck since May 4  
  - https://elizaos.github.io/summary/day (currently reported as not updating)

If you want to help this week: the quickest wins are **(1)** helping update the Hyperfy plugin for current core compatibility, and **(2)** contributing a docs PR clarifying the new X API requirement + setup guidance.