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

## 1) Executive Summary

This week was all about **shoring up the foundation** for secure, cloud-native, multi-connector agent deployments—while keeping self-hosters and builders unblocked.

**Top milestones:**
- **ElizaCloud consolidation + cost-focused infra shift:** ElizaCloud work has been consolidated into the main repo at **`github.com/elizaOS/eliza`**, alongside a move away from Vercel to support **cheaper container-based deployments** (per Shaw in Discord). This is a meaningful step toward a unified “build once, deploy anywhere” pipeline.
- **Security & reliability upgrades landed across the stack:** The project continued to harden runtime stability (notably for headless Linux) and improve connector reliability (Telegram polling race fixes landed earlier in the week’s cadence, and Slack is now first-class inside the monorepo).
- **DeFi ecosystem safety documentation in motion:** A docs PR is now open to add **SafeAgent** (token safety tooling) to the DeFi plugin registry, signaling a push toward clearer guidance and safer default behaviors for DeFi-adjacent builders.

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

### Core platform: stability, auth, and secure configuration
- **Cross-platform secrets management (“Vault”) is now real:** The `@elizaos/vault` feature landed recently and continues to define the direction for secure credential storage and Settings UI integration. The key theme: fewer plaintext secrets in configs, better cross-OS behavior, and safer self-hosting defaults.  
  - PR: **`feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration`** ([elizaos/eliza#7197](https://github.com/elizaos/eliza/pull/7197))
- **Headless Linux crash prevention:** A critical fix avoids OS keychain usage on headless Linux where native keyring backends can segfault without a secret-service agent.  
  - PR: **`fix(vault, confidant): skip OS keychain on headless Linux…`** ([elizaos/eliza#7230](https://github.com/elizaos/eliza/pull/7230))

### Cloud: monetized apps + domains are taking shape
- **Monetized container app domains support:** Cloud gained deeper support for app-scoped chat endpoints and Cloudflare-managed domains as part of the monetized app lifecycle. This is a big step for builders who want to ship agent-powered apps with billing and custom domains.  
  - PR: **`feat(cloud): support monetized container app domains`** ([elizaos/eliza#7376](https://github.com/elizaos/eliza/pull/7376))

### Connectors & plugins: Slack joins the monorepo, n8n UX improves
- **Slack plugin migrated into the monorepo:** Slack was the last major connector still living outside the main tree. It now ships with actions/providers and a substantial unit test suite.  
  - PR: **`feat(slack): migrate plugin-slack into the monorepo`** ([elizaos/eliza#7375](https://github.com/elizaos/eliza/pull/7375))
- **Automation (n8n) clarification loop improvements:** The automation UX continues to get more “human-friendly” with clarification roundtrips and quick-pick UI, making it easier to resolve missing info/credentials without derailing workflow creation.  
  - PRs: [#7316](https://github.com/elizaos/eliza/pull/7316), [#7341](https://github.com/elizaos/eliza/pull/7341), and follow-up bugfix [#7340](https://github.com/elizaos/eliza/pull/7340)
- **Docs: SafeAgent added to DeFi plugin registry (awaiting review):**  
  - PR: **`elizaos/docs#84`** (SafeAgent registry entry; pending review)

## 3) Community Spotlight (Discord)

### Builder showcase: full-stack + multi-agent production patterns
Community member **harry346165** shared a completed client build that looks like a “modern reference architecture” for many ElizaOS community projects:
- **Frontend:** Next.js 15, React 19, TypeScript, Tailwind, Shadcn, TanStack Query  
- **Backend/Data:** Prisma + PostgreSQL, Redis caching  
- **Infra:** AWS, Docker, Kubernetes  
- **Agents:** LangGraph + CrewAI using Claude 3.5 and GPT-4o  
- **RAG:** Pinecone + Weaviate

If you’re designing a production-grade agent web app, the stack outline is worth comparing to what you’re building—especially the “multiple vector DB” approach for RAG evaluation and migration flexibility.

### Twitter/X integration: a key requirement changed
In a thread prompted by **guru0**, **odilitime** confirmed that **X API access is now required** for Twitter integration, and noted pricing has become more affordable than it used to be. This is important for anyone planning “agent-as-a-social-bot” deployments; budgeting for API usage is now part of the baseline plan.

### Hyperfy plugin hiccup (and why it matters)
**binarycookies** noticed the **Hyperfy plugin disappeared** (GitHub link returning 404). The consensus: it was removed due to **version compatibility mismatches** with current ElizaOS core. A temporary zip workaround was shared via DM, but the community clearly needs a durable fix (see “Coming Soon”).

### Governance clarity: “builders-first” fair launch framing
Shaw reiterated a core identity statement: **ElizaOS is a fair launch project** without VC structure, and the “team” is fundamentally the set of builders using and extending the system. The stated emphasis remains on **product development rather than token price management**—a useful reference point during market volatility.

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

### Market note: fund flows vs price action divergence
Community member **cryptologos_00014** shared an observation: **positive net fund flow** has appeared consistently while **price continues to decline**, a divergence that can suggest abnormal market dynamics (including the possibility of strategic selling during low-impact periods). This isn’t a definitive conclusion—just a signal to keep an eye on liquidity conditions and execution patterns.

### auto.fun update
No concrete development updates for **auto.fun** were captured in this week’s aggregated notes. If you’re tracking auto.fun milestones, this week reads as “quiet on public signals”—watch Discord and the repos closely next week for movement.

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

- **Hyperfy connector/plugin return path:** Expect work to focus on restoring a compatible, version-aligned Hyperfy plugin release (or a documented migration path).
- **Docs updates for X (Twitter) integration requirements:** The community requested clearer documentation on the new requirement and cost expectations.
- **Daily summary site issue:** The **`elizaos.github.io/summary/day`** page appears stuck since May 4; likely a pipeline/config issue that needs investigation.
- **SafeAgent docs merge + broader DeFi safety posture:** Once `elizaos/docs#84` merges, builders should expect more visible guidance around token safety tooling and recommended practices.

## 6) Resources (Links & Threads)

### GitHub (high-signal PRs)
- Vault (secure secrets + Settings UI): https://github.com/elizaos/eliza/pull/7197  
- Headless Linux keychain segfault fix: https://github.com/elizaos/eliza/pull/7230  
- Cloud monetized container app domains: https://github.com/elizaos/eliza/pull/7376  
- Slack plugin migration: https://github.com/elizaos/eliza/pull/7375  
- n8n clarification roundtrip: https://github.com/elizaos/eliza/pull/7316  
- Clarification quick-pick UI: https://github.com/elizaos/eliza/pull/7341  

### Docs
- SafeAgent in DeFi plugin registry (awaiting review): **elizaos/docs#84**

### Discord threads (weekly highlights)
- May 7: X API requirement + Hyperfy plugin missing: https://discord.com/channels/1253563208833433701/1253563209462448241  
- May 8: Full-stack showcase + token market observations: https://discord.com/channels/1253563208833433701/1253563209462448241