# ElizaOS Weekly Newsletter (Apr 22–Apr 28, 2026)

## 1) Executive Summary

**1. $ELIZA gained real infrastructure utility via x402.**  
This week brought a tangible milestone for the ecosystem: **$ELIZA is now the default payment method in x402 for elizaOS/Milady services**, meaning users can **bill x402 services directly with $ELIZA**. This connects token usage to actual service consumption rather than pure speculation.

**2. Eliza v3 + Milady integration moved into “nearly finished” territory.**  
Shaw shared that **Eliza v3 and the Milady integration are nearing completion**, with “an exciting couple of weeks ahead.” Development has been happening in quieter, dev-focused spaces to keep momentum and minimize distraction.

**3. Major modernization push continued (with a key build blocker).**  
Across the stack, the project is advancing a modernization target of **Node.js 24, TypeScript 6, Bun 1.3.13, and React 19.2.5**. Progress is currently **blocked by a missing transitive dependency causing `bun install` failures**, with broader dependency updates and CI pipelines stalled until the blocker PR (**elizaos/eliza#7146**) lands.

---

## 2) Development Updates

### Platform & Infrastructure
- **Dependency modernization (Node 24 / TS 6 / Bun 1.3.13 / React 19.2.5)** is underway, but:
  - The ecosystem is **critically blocked** by a missing transitive dependency that breaks `bun install`.
  - CI/CD impact: workflows in **elizaos/cloud** and **elizaos-plugins/registry** are failing to consistently run `bun install` and `tsc`, which increases the risk of regressions slipping through.
  - **Priority:** unblock by merging **elizaos/eliza#7146** so the update stack can proceed.

### Cloud & Model Routing Reliability
- **Cloud infra routing was modernized** by replacing **Vercel AI Gateway with OpenRouter**, with **OpenAI and Anthropic as failovers**. This improves resilience against provider outages and model availability drift.

### Auth & CLI Stability
- A long-running papercut was addressed: **CLI authentication hangs** were mitigated via **auto-clearing stale Steward and Privy tokens**, reducing “stuck login” scenarios.

### Automation & n8n Ecosystem
- The **n8n plugin** saw capability expansion:
  - **TriggerContext** was added to support **conversation routing**
  - **RuntimeContextProvider** improves how runtime data is passed and handled
- Additional in-progress work this week (across repos) points to deeper automation maturity:
  - Propagating conversation routing into the **n8n workflow generator**
  - Expanding runtime-context support (including targets like Discord and Gmail)

### Security & Credential Hygiene
- Multiple changes reinforced safer operations:
  - **Disconnect-purge functionality** to remove credentials on disconnect
  - **Stricter runtime-fact rules** to reduce accidental leakage/misuse of sensitive runtime state

### Reported Issue
- Community members reported a **non-functional Milady Play Store link** originating from the GitHub repository. If you’re onboarding via that path, expect a fix (or use alternate install instructions) once it’s corrected.

---

## 3) Community Spotlight (Discord)

### “Utility over vibes” moment: x402 + $ELIZA
A standout community thread centered on token utility. After suggestions to “connect the coin to infrastructure,” **odilitime confirmed that $ELIZA is the default payment method in x402 for elizaOS/Milady services**—and clarified that **yes, users can bill x402 services with $ELIZA**. This is exactly the kind of concrete loop (usage → payment → ecosystem value) the community has been asking for.

### Balancing build-mode with community-mode
Several members (notably **zadayos** and **cryptologos_00014**) raised an important meta-topic: the need to balance deep technical focus with:
- clearer public-facing updates,
- PR planning,
- and business strategy materials that help the broader community track “what’s shipping and why.”

Shaw acknowledged the gap and committed to **posting more frequent updates in the main discussion channel**.

### Community ops: coordination + security
- **odilitime banned a scammer**, a reminder to stay cautious with DMs and “too-good-to-be-true” links.
- A separate thread mentioned formation of an **“eliza army” steering group** for community coordination, alongside an invite to a related Discord (Hyperscape).
- There was also a helpful educational aside on the **original 1966 ELIZA chatbot** and the “ELIZA effect,” grounding the project’s name in its historical roots.

### Collaboration callout
**kevin111s** introduced themselves as a software engineer seeking a **US-based, client-facing collaborator**, while they focus on building production-ready AI workflows and backend architecture. If you’re strong on partnerships, sales engineering, or customer comms, this could be a good match.

---

## 4) Token Economics (AI16z / $ELIZA / auto.fun)

### $ELIZA: from “token” to “meter”
Two complementary directions were discussed this week:

- **Direct utility (now live):**  
  **$ELIZA as the default x402 payment method** for elizaOS/Milady services.

- **Low-friction utility strategy (ongoing philosophy):**  
  Shaw described a preference to **accept whatever payment method users already have**, then use revenue to **buy back tokens**, avoiding UX friction from forcing a single-token checkout path.

Together, these suggest a pragmatic approach: maximize adoption (easy payments) while still creating a durable value loop (utility + buybacks where applicable).

### AI16z token & auto.fun
No major, verifiable shipping updates for **AI16z token** mechanics or **auto.fun** were posted in the provided activity this week. If you’re tracking these closely, keep an eye on upcoming announcements—community questions about roadmap clarity are rising, and more frequent official updates were explicitly requested.

---

## 5) Coming Soon

Here’s what the community should anticipate next, based on this week’s signals:

- **Eliza v3 release momentum** and **Milady integration completion** (Shaw: “nearly finished”).
- **degenAI updates** were described as imminent in recent discussion, though an April timing question remained unanswered in-channel.
- **Fix for the broken Milady Play Store link** referenced by community members.
- **Unblocking the toolchain modernization** once the `bun install` dependency blocker is resolved (watch **elizaos/eliza#7146**).
- Continued work in the cloud repo, including:
  - pushing **develop → production**
  - early design discussions for a **Claude + Codex sub-agent bridge specification**

---

## 6) Resources

### Key Discord threads
- ElizaOS main discussion (Apr 28):  
  https://discord.com/channels/1253563208833433701/1253563209462448241

### Notable PR / work references (from weekly activity summaries)
- Build/dependency unblocker (blocking modernization): **elizaos/eliza#7146**  
- x402 paid routes + hardening: **elizaos/eliza#7100**  
- Event-kind triggers wired to runtime event bus: **elizaos/eliza#7116**  
- Apps as native windows + App Details page: **elizaos/eliza#7115**  
- CLI auth hang mitigation (stale token auto-clear): referenced in overall project summary (Apr 28)

### Quick reminders
- If you’re testing automation + workflows: watch for improvements around **n8n routing/context** and workflow generation reliability.
- If you’re validating payments/monetization flows: x402 now has a clearer story with **$ELIZA-default billing** for elizaOS/Milady services.

---