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

## 1) Executive Summary

This week pushed ElizaOS forward on two fronts: **next-gen architecture** and **day-to-day platform maturity**.

1. **Multi-language future accelerated (Rust + Python + TypeScript):** Work continued on the “next” Eliza runtime direction, expanding core packages and examples across languages and simplifying what “core” means for v2-style deployments (see PRs [#6485](https://github.com/elizaos/eliza/pull/6485) and [#6474](https://github.com/elizaos/eliza/pull/6474)).  
2. **Security & multi-tenant readiness improved:** The codebase gained major building blocks for safer, more enterprise-friendly deployments—especially JWT-based auth/user management (merged [#6200](https://github.com/elizaos/eliza/pull/6200)) and per-request/per-entity settings via request context (merged [#6457](https://github.com/elizaos/eliza/pull/6457)).  
3. **Ecosystem momentum (plugins + automation):** The plugin economy kept expanding, with strong signals around workflow automation (notably `plugin-n8n-workflow`) and “real-world” agent capabilities (marketplaces, sports data, financial safety guardrails) as highlighted in the project’s Feb 8–14 weekly summary.

---

## 2) Development Updates (Core + Plugins)

### Core framework & runtime
- **JWT authentication and user management (merged):** PR [#6200](https://github.com/elizaos/eliza/pull/6200) introduced a comprehensive JWT auth system designed for **data isolation and multi-entity support**. It’s gated behind `ENABLE_DATA_ISOLATION=true`, reducing risk for teams not ready to switch modes yet.
- **RequestContext for per-user settings (merged):** PR [#6457](https://github.com/elizaos/eliza/pull/6457) added an AsyncLocalStorage-based request context, enabling runtime methods (like `getSetting()`) to resolve settings in a **per-request entity scope**—a foundational piece for multi-tenant deployments where different users need different keys/tokens.
- **Action filtering to reduce prompt bloat:** PR [#6475](https://github.com/elizaos/eliza/pull/6475) added `ActionFilterService` using **vector search + BM25 reranking**, shrinking the action/provider context from “hundreds” down to the most relevant ~10–20. This directly targets latency/cost and improves response quality when many plugins are installed.

### Stability & bug fixes
- **Defensive checks preventing runtime crashes:**
  - PR [#6471](https://github.com/elizaos/eliza/pull/6471): null/undefined guards around `Object.entries()` in core settings utilities.
  - PR [#6473](https://github.com/elizaos/eliza/pull/6473): null check for `runtime.providers` to prevent `Cannot read properties of null (reading 'filter')`.
- **CLI reliability improvements (merged):**
  - PR [#6362](https://github.com/elizaos/eliza/pull/6362): `elizaos create` now uses `'latest'` for `@elizaos/*` deps to avoid npm resolution issues in linked/alpha scenarios.
  - PR [#6376](https://github.com/elizaos/eliza/pull/6376): agent commands load `.env` files correctly for authenticated remote servers.
  - PR [#6379](https://github.com/elizaos/eliza/pull/6379): validates directory paths to avoid confusing ENOENT errors.
- **Server event correctness:** PR [#6378](https://github.com/elizaos/eliza/pull/6378) ensures `MESSAGE_SENT` is emitted after sending responses to the central server—important for observability and downstream integrations.

### Workflow automation & build pipeline notes
- **n8n plugin consolidation direction (Discord):** Core devs discussed consolidating duplicate repos (`plugin-n8n` vs `plugin-n8n-workflow`) and standardizing around the more capable `plugin-n8n-workflow` (auto-correction for I/O, workflow preview/drafting, OAuth handling, cloud-friendly credential modes, and “zero hallucination” workflow generation).  
- **Build gotcha clarified:** Some JSON schema/index files are **intentionally generated** via a crawl script and not committed; CI generates them during release.

### Open issues worth tracking (user-impacting)
- **Duplicate LLM calls when messages include URLs:** Issue [#6486](https://github.com/elizaos/eliza/issues/6486) reports URL messages being processed as both text and attachment preview, doubling cost and duplicating output.
- **Image content stripped in cloud chat requests:** Issue [#6494](https://github.com/elizaos/eliza/issues/6494) flags `/api/v1/chat/completions` conversion stripping image content.
- **Custom OpenAI-compatible endpoints requested:** Issue [#6490](https://github.com/elizaos/eliza/issues/6490) asks for configurable OpenAI base URLs to support third-party “OpenAI-compatible” providers.

---

## 3) Community Spotlight (Discord)

### Funboy’s Moltbook anti-bot solver (real-world agent reliability)
In a standout engineering moment, **funboy** shared a working approach for Moltbook’s anti-bot verification flow: intercept `verification_required`, extract an obfuscated math challenge, solve it via an LLM (reported: **DeepSeek-chat**), then POST the result back within 30 seconds. The constraints are harsh (1-day suspension for first failure, 7-day for second, history deletion for third), so this is a meaningful “agents in adversarial environments” win.

### TipCat demo and the “reward good explanations” idea
At Clawcon HK, **R0am** demoed `tip.md` with PR rating/tipping mechanics, highlighting Stan’s PR **#6200** receiving a **9.5/10** TipCat rating. The follow-up discussion got interesting: **Odilitime** suggested a TipCat variant that rewards devs specifically when they *explain changes clearly*, nudging the culture toward better documentation and reviewability.

### Honest onboarding feedback (and a roadmap challenge)
Community member **yojo** gave direct feedback about gaps for non-technical users:
- unclear timeline for “zero-coding” agent creation,
- unclear token utility/governance explanations,
- roadmap presentation too developer-centric,
- without plugins, it’s hard to see immediate advantage vs ChatGPT beyond **decentralized ownership**.

This thread is a useful signal: the tech is moving fast, and the next step is packaging it so non-coders can actually ship real use cases.

---

## 4) Token Economics (AI16Z → ElizaOS, and auto.fun)

### Token migration: now closed
The biggest token-related update this week is administrative but important: **the ai16z → ElizaOS token migration window has closed** after a 90-day manual ticket process.

- **Swap ratio:** **1 ai16z = 6 elizaOS**  
- **Status:** migration/support channels are **locked**; only users who opened tickets before the deadline are still being processed  
- Discord discussion reference: [#discussion thread](https://discord.com/channels/1253563208833433701/1253563209462448241)

This came up because a user realized they missed the deadline—an explicit reminder that critical deadlines need high-visibility, repeated comms.

### auto.fun developments
No concrete, verifiable auto.fun product updates were included in this week’s provided logs. If you’re building on/around auto.fun, keep an eye on announcements and repo activity as it surfaces—this newsletter will summarize as soon as public milestones land.

---

## 5) Coming Soon

Here’s what to anticipate based on this week’s direction and open threads:

- **Plugin repo cleanup & consolidation:** Expect decisions (and possibly deletions/merges) around duplicate plugin repositories, with `plugin-n8n-workflow` emerging as the “primary” n8n path.
- **Wallet architecture evolution:** Discord conversations leaned toward **HD wallets** over heavy OAuth-app patterns for agent wallet management—more flexible branching, less operational overhead.
- **Onboarding improvements:** Based on community feedback, expect clearer “who is ElizaOS for right now?” messaging, safer recommended plugin sets, and better roadmap visibility for non-coders.
- **Fixes targeting cost + UX:** Watch for progress on the **URL double-processing** bug and cloud chat **image handling**, both of which have direct cost/quality implications.

---

## 6) Resources (PRs, Issues, Discussions)

**Core PRs / Features**
- Multi-language next-gen direction: [#6485](https://github.com/elizaos/eliza/pull/6485), [#6474](https://github.com/elizaos/eliza/pull/6474)  
- JWT auth system (merged): [#6200](https://github.com/elizaos/eliza/pull/6200)  
- Request context (merged): [#6457](https://github.com/elizaos/eliza/pull/6457)  
- ActionFilterService: [#6475](https://github.com/elizaos/eliza/pull/6475)

**Docs**
- Core documentation guides: [#6356](https://github.com/elizaos/eliza/pull/6356)  
- Environment variables reference: [#6377](https://github.com/elizaos/eliza/pull/6377)

**Bugs / Requests**
- URL triggers duplicate LLM calls: [#6486](https://github.com/elizaos/eliza/issues/6486)  
- Image content stripped in cloud chat: [#6494](https://github.com/elizaos/eliza/issues/6494)  
- Custom OpenAI endpoint URL: [#6490](https://github.com/elizaos/eliza/issues/6490)

**Discord threads referenced**
- Token migration Q&A: https://discord.com/channels/1253563208833433701/1253563209462448241  
- Cloud credits admin (core-devs): https://discord.com/channels/1253563208833433701/1377726087789940836