## Weekly Newsletter (2026-02-10) — Week of **2026-02-03** to **2026-02-09** ### 1) Executive Summary **Big week for shipping + ecosystem momentum (even with market noise):** - **“Cron Job S1E2” weekly roundup dropped** with a stack of concrete milestones: **PageIndex hitting 98.7% RAG accuracy**, **Milaidy personal AI assistant launch**, **Babylon entering internal testing**, **Claude Opus 4.6 integration**, plus **ElizaCloud bug fixes** and a notable nod that **Ethereum welcomed ElizaOS cross-chain functionality**. - **Core reliability and multi-tenant foundations continued to harden** across the codebase: JWT auth/user management, request-scoped settings, and multiple stability fixes landed recently—setting the stage for more “real app” deployments rather than hobby demos. - **Community surfaced urgent clarity needs on token + migrations.** Confusion around Korean exchange delistings was resolved (old **AI16Z** token impacted, not current **ELIZAOS**), but questions about the **migration deadline** and token utility remain a high-priority communication gap. --- ### 2) Development Updates #### Core framework: scalability, safety, and “less prompt bloat” - **Action filtering got a major upgrade** with **vector search + BM25 reranking** to reduce “prompt bloat” (filtering hundreds of actions/providers down to the most relevant ~15). This is a meaningful step toward faster, cheaper, more consistent agent behavior: - PR: **ActionFilterService** — https://github.com/elizaos/eliza/pull/6475 - **Per-request settings via Request Context** landed, enabling cleaner multi-tenant patterns (e.g., different users/entities using different keys/settings without messy parameter threading): - PR: https://github.com/elizaos/eliza/pull/6457 - **JWT authentication + user management** shipped behind an isolation flag, strengthening production readiness for hosted/multi-user deployments: - PR: https://github.com/elizaos/eliza/pull/6200 #### Reliability fixes (a recurring theme this week) - Multiple **defensive null/undefined fixes** were merged to prevent runtime crashes in settings and bootstrap providers: - Settings guards: https://github.com/elizaos/eliza/pull/6471 - Bootstrap provider null check: https://github.com/elizaos/eliza/pull/6473 - **MESSAGE_SENT event emission** was fixed (a long-running issue) so plugins depending on message lifecycle events behave correctly: - PR: https://github.com/elizaos/eliza/pull/6378 #### Performance & infra: the Postgres “logs table” bottleneck In Discord, devs flagged a **serious performance bottleneck**: the **PostgreSQL logs table is being hit excessively**, slowing DB performance and therefore **slowing agent responses**. Stan confirmed a **major optimization plan** is already in motion. This is the kind of unglamorous work that matters most once real usage ramps. #### Milaidy & plugins: install pain, compatibility, and the next wave of tools - **Milaidy (Mac-native personal assistant) is live**, but early adopters found sharp edges: - A known crash in the **agent skills instructions provider**: `skill.description.toLowerCase is not a function` (confirmed by Odilitime as a real bug needing a fix). - Some errors were clarified as benign (missing server/world ID, server ownership messages), while **pluginRegistryService 401 Unauthorized** was labeled **work-in-progress functionality**. - **Plugin compatibility issue**: missing `MAX_EMBEDDING_TOKENS` constant in newer plugin versions was raised earlier in the week, with folks debating rollback vs. PRs across plugin repos. - A substantial proposal surfaced to use **PM2 as an external process manager** for websocket handling and more structured deployments—promising, but still a discussion-stage architecture direction. #### Open issues worth watching - **Webapp bug**: URLs in a message can trigger duplicate LLM calls (processed as both text + attachment preview), causing duplicated responses and doubled token cost: - Issue: https://github.com/elizaos/eliza/issues/6486 --- ### 3) Community Spotlight (Discord) This week’s Discord energy split into two modes: **builders shipping** and **holders asking hard questions**. **Notable community contributions & discussions:** - **Odilitime** did standout support work helping troubleshoot VPS Milaidy installs—clearly separating **“normal noise” vs. “real bug” vs. “WIP feature.”** That kind of triage unblocks everyone. - **Vega** announced active development of a plugin to use **SillyTavern character cards** with OpenClaw—great example of community-driven interoperability. - **yojo** delivered high-signal product feedback for **ElizaCloud.ai UX**, advocating strongly for “prompt-only” (no-code) experiences: better visual generation workflows, curated plugin marketplace, referrals, and crypto transfers without wallet-connect friction. - **Security awareness** rose: multiple scam attempts were reported, and the community correctly identified a **fake support desk Discord** as a scam. The call for better **autoban/anti-scam tooling** is getting louder (and justified). Also worth noting: **jin’s weekly roundup videos** are becoming the de facto heartbeat update for many community members—especially as people request more consistent status visibility. --- ### 4) Token Economics (AI16Z / ELIZAOS + auto.fun) **What actually happened this week:** - **Korean exchange delisting confusion got resolved:** community panic suggested ELIZAOS was being delisted from **Bithumb/Coinone/Korbit**, but clarifications from **davidhq** and **paolin** indicated the delisting affected the **pre-rebrand AI16Z token**, **not** the current **ELIZAOS** token. - **Migration anxiety remains unresolved:** a user reported missing the **AI16Z → ELIZA** migration deadline and asked whether tokens were lost. This question did not receive a definitive public answer in the captured discussions—this is a high-priority item for an official FAQ. - **Utility questions continue:** staking was explicitly stated as **not available** right now, and users asked for clearer token use-cases tied to products. - **Bridge safety reminder:** there is **no official/safe bridge** from Solana to BSC for ELIZAOS (community member EMERSON3S advised against it). Treat “bridges” you find in DMs as hostile until proven otherwise. **auto.fun:** no concrete, verifiable product updates surfaced in the captured Discord/GitHub snapshots this week. The community is clearly eager for more visibility into how token utility connects to upcoming launches—so expect auto.fun to be pulled into those broader “what’s shipping + why it matters” updates. --- ### 5) Coming Soon Here’s what the community should anticipate (based on active work + surfaced needs): - **Database/logging optimizations** to address the Postgres logs-table bottleneck and improve responsiveness at scale. - **Character editor wiring** (to fix current limitations where character setup is effectively “onboarding-only” and agents can revert to default behavior). - **Fix for Milaidy agent skill provider crash** (`skill.description.toLowerCase…`) and continued plugin compatibility cleanup. - **SillyTavern character card integration** plugin release (OpenClaw). - **Anti-scam improvements** (autoban / better moderation automation) given repeated scam attempts and fake support channels. - Continued maturation of the **“next” / multi-language Eliza** direction (Rust + Python + TypeScript) being developed in large PR branches: - PR: https://github.com/elizaos/eliza/pull/6474 --- ### 6) Resources **Discord discussions & media** - Weekly roundup (“Cron Job S1E2”) link shared in Discord: https://discord.com/channels/1253563208833433701/1377726087789940836 - Token + exchange delisting clarification thread (discussion channel): https://discord.com/channels/1253563208833433701/1253563209462448241 - Developer troubleshooting + Milaidy install bug reports (coders channel): https://discord.com/channels/1253563208833433701/1300025221834739744 **Key GitHub items** - Action filtering to reduce prompt bloat: https://github.com/elizaos/eliza/pull/6475 - Request context (per-entity/per-user settings): https://github.com/elizaos/eliza/pull/6457 - JWT auth + user management: https://github.com/elizaos/eliza/pull/6200 - URL triggers duplicate LLM calls (open bug): https://github.com/elizaos/eliza/issues/6486 --- If you’re feeling whiplash between “code is shipping” and “token sentiment is rough,” you’re not alone. The most constructive thing we can do this week: **turn the repeated questions (migration, listings, utility, bridges, scams) into a pinned, official, frequently-updated FAQ**—and keep the build cadence visible with short, regular release notes.