# ElizaOS Weekly Newsletter (Feb 8–Feb 14, 2026)

## 1) Executive Summary

**A big week for “production-grade” ElizaOS.** Here are the standout milestones:

1. **Multi-language core momentum (Rust + Python + TypeScript)** continued to crystallize, pushing ElizaOS closer to a framework that teams can embed into existing stacks—not just TS-first projects. The ongoing “next-gen” work is captured in the large PRs that expand core packages and examples (notably **elizaos/eliza #6485**).

2. **Security + multi-user hardening shipped**: a **JWT authentication and user-management system** landed (behind a flag) to support safer, more enterprise-ready deployments with stronger session isolation and data boundaries (**elizaos/eliza #6200**).

3. **Workflow automation and plugin economy accelerated**: the team aligned on consolidating around the more capable **n8n workflow plugin**, while the broader plugin ecosystem added financial guardrails, marketplaces, and real-world data sources—making agents more useful (and safer) in the wild.

---

## 2) Development Updates (Technical Highlights)

### Core framework: capability, cost, and stability improvements
- **ActionFilterService (prompt bloat killer)**: a new service filters actions/providers shown to the LLM using vector search + BM25 reranking, reducing “200+ actions” down to ~15 relevant ones and lowering latency + token spend (**elizaos/eliza #6475**).
- **JWT auth system**: end-to-end auth flow improvements across client/server, including middleware and tests, enabling multi-user patterns when `ENABLE_DATA_ISOLATION=true` (**elizaos/eliza #6200**).
- **Per-request entity settings (Request Context)**: AsyncLocalStorage-based request context enables per-user secrets/settings without threading parameters everywhere (**elizaos/eliza #6457**). This is foundational for hosted / multi-tenant deployments where different users bring different API keys or OAuth credentials.
- **Defensive runtime fixes**: null/undefined checks in core settings utilities and plugin-bootstrap providers prevent common runtime crashes that previously surfaced as `Object.entries(...)` errors (**elizaos/eliza #6471**, **#6473**).

### Plugins & infrastructure: finance, reliability, and automation
- **Financial safety & trading infra expanded**
  - Transaction guardrails + validation via Proofgate integrations in the plugin registry (**elizaos-plugins/registry #254** and related additions).
  - EVM and Solana plugins received deeper reliability work (multi-provider fallbacks, cloud proxy routing, Token-2022 support, multicall, portfolio/wallet improvements) (**plugin-evm #24/#25**, **plugin-solana #24/#26**).
- **OpenAI plugin cost controls**: persistent media caching reduces redundant image/audio calls and can materially cut costs for agents that generate media repeatedly (**plugin-openai #23**).
- **n8n workflow plugin consolidation (important!)**
  - In core-dev discussions, the team identified duplicated repos (**plugin-n8n** vs **plugin-n8n-workflow**) and agreed consolidation is needed—standardizing around the more feature-complete workflow plugin.
  - If you pulled **plugin-n8n-workflow** and hit TypeScript errors for missing JSON modules (`defaultNodes.json`, `schemaIndex.json`, `triggerSchemaIndex.json`): those files are **generated**, not committed. Run the **`crawl`** script locally; CI generates them during release.

### ElizaCloud / authentication roadmap signals
- Work is underway to add **SIWE (Sign-In With Ethereum, EIP-4361)** to ElizaCloud so agents can authenticate and generate API keys more smoothly. This also supports ideas like “proof-of-agent” onboarding via tasks.

---

## 3) Community Spotlight (Discord Contributions & Discussions)

### Clearing up Babylon launch expectations
A key community win this week was **timeline clarity**: Babylon’s **non-chain launch is near**, but the **token/chain launch is still months out**—and importantly, **there is no Babylon token yet**. The ICO is “at least a couple months” away. This reduced confusion around airdrops and launch phases.

### Wallet architecture: Privy OAuth vs HD wallets
One of the best technical threads came out of **#coders**, where devs compared:
- **Privy-based OAuth approach** (agents become OAuth apps via app/secret IDs; powerful but “heavy” and HTTP-dependent), versus
- **HD wallets** (hierarchical deterministic branching for subagents/users), which emerged as the preferred direction for simplicity and control.

If you’re building agent products that need wallet partitioning (subagents, user vaults, role-based spend), this is the thread to revisit.

### UX feedback that’s actually actionable
Community-led research highlighted real onboarding pain in ElizaCloud.ai (billing clarity, VPN recharge issues, plugin discoverability, and target-audience confusion). The discussion stayed constructive: the takeaway wasn’t “ship slower,” it was **make the product legible to non-coders** and tighten the “first 10 minutes” experience.

### Collaboration energy
Several devs posted availability, and projects like **LunchTable TCG** shared progress (streaming already working; UI/UX + artwork integration in progress). If you’re looking to contribute, Discord is currently high-signal for matching builders with real work.

---

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

### AI16z → ElizaOS migration status & support
- **Migration is confirmed complete.**
- Some community members reported missing the migration window and opened support tickets (e.g., **ticket-0550**) for manual resolution—reminder: use official channels and avoid scam DMs.
- Trading conversation leaned practical: users discussed minimizing slippage via DEX routes (community mentioned PancakeSwap on BSC and orca.so on Solana).

### Price sentiment & “what drives value?”
Token performance frustration was candid this week. The most grounded framing: **value follows utility + usage metrics**, not vibes. The community repeatedly pointed to measurable drivers—active accounts, revenues/subscriptions, and “best-in-class UX.”

### Babylon relationship (important nuance)
Several members asked whether Babylon success directly benefits the ElizaOS token. Current community understanding: **Babylon’s product launch may not automatically translate into Eliza token value** without explicit economic linkage—so clarity/docs here are a top request.

### auto.fun
No confirmed, concrete auto.fun product changes were surfaced in this week’s dataset. If there are ongoing experiments, they weren’t formally summarized in Discord threads captured here—so treat auto.fun as “watch this space,” not “announced this week.”

---

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

- **SIWE for ElizaCloud** + easier agent API key generation (enabling agent-native onboarding flows).
- **n8n plugin consolidation** (expect repo cleanup + clearer “one true plugin” guidance).
- **HD wallet architecture direction** for agents (cleaner branching for subagents/users).
- **2.x adoption push**: tooling to forward-port 1.x plugin improvements into 2.x while reducing backport churn.
- **UX + billing fixes** in ElizaCloud.ai (VPN recharge, duplicate account creation, plugin discovery).
- **Docs to clarify Babylon/token relationships** and **NFT collection plans/utility** (both requested repeatedly).

---

## 6) Resources (Links & References)

**Roadmap**
- Public roadmap: https://github.com/elizaos/roadmap

**Key PRs / Engineering Threads**
- Multi-language “next-gen” Eliza: https://github.com/elizaos/eliza/pull/6485  
- JWT auth + user management: https://github.com/elizaos/eliza/pull/6200  
- ActionFilterService: https://github.com/elizaos/eliza/pull/6475  
- Request Context (per-user settings): https://github.com/elizaos/eliza/pull/6457  
- n8n workflow plugin release (v1.1.0 referenced in weekly summary): https://github.com/elizaos-plugins/plugin-n8n-workflow/pulls

**Discord threads (high-signal)**
- Babylon timeline clarification: https://discord.com/channels/1253563208833433701/1301363808421543988  
- n8n consolidation + build notes: https://discord.com/channels/1253563208833433701/1377726087789940836  
- Wallet architecture discussion: https://discord.com/channels/1253563208833433701/1300025221834739744  
- Token/value & ecosystem discussion: https://discord.com/channels/1253563208833433701/1253563209462448241