# ElizaOS Weekly Newsletter (2026-04-22) **Week of 2026-04-16 to 2026-04-22** ## 1) Executive Summary This week was a “shipping + securing” kind of week across ElizaOS: 1. **LifeOps and cloud auth took a big step forward.** A unified authentication flow now supports **wallet + GitHub logins**, and server-side **Steward token refresh** was added to address silent logout issues. LifeOps also expanded with new real-world utilities like calendar management and travel booking. 2. **Agent reliability improvements landed across the stack.** Scenario “final-check” handlers were restored, **task heartbeat** was integrated into swarm synthesis, and memory consistency was improved (notably: in-memory adapter ordering now matches SQL expectations). Together, these changes reduce “stuck runs,” improve determinism, and make multi-agent orchestration more predictable. 3. **The ecosystem continued to professionalize—while staying vigilant on security.** The community rallied around scam warnings after multiple phishing attempts, and we saw continued momentum on paid-agent integrations like **Elisym’s marketplace plugin**. At the same time, a CI configuration issue in the plugin registry blocked a key PR, highlighting the need to keep infra tidy as the plugin surface grows. --- ## 2) Development Updates ### Authentication & Cloud - **Unified auth workflow (wallet + GitHub):** The team implemented a single authentication path that supports both login methods, reducing friction for developers and users who bounce between “web2 identity” and “wallet identity.” - **Steward refresh on the server:** A server-side refresh mechanism was added to fix **silent logout** behavior where sessions expired without obvious UI feedback. - **React UI polish for wallet providers:** Styling and text-wrapping issues were addressed for both **EVM and Solana** wallet options, improving the onboarding “first five minutes.” ### LifeOps expansion - **App-LifeOps gained broader capabilities:** Work this week expanded LifeOps into more “assistant-like” territory, including: - **Calendar management** - **Travel booking** - **Cross-platform gateway support** (bridging channels/devices more reliably) ### Core runtime & model compatibility - **`PROMPT_OUTPUT_FORMAT` environment variable added:** A new env var makes output formatting more compatible across models—especially for providers that don’t reliably emit the project’s default encapsulation style (notably mentioned: **Gemini 2.5 Pro** and **Llama via Ollama**). If you’ve been juggling model-specific prompt wrappers, this should reduce template friction. - **Scenario final-check handlers restored:** Final-check logic (often the last line of defense before a scenario is declared “done”) is back, with tighter matching on channels/actions. - **Task heartbeat integrated into swarm synthesis:** Heartbeats help the system understand “liveness” during longer tool-use loops—useful for UI reporting and to prevent long-running orchestration from looking stalled. ### Data layer consistency - **In-memory adapter ordering fixed:** The in-memory database adapter now sorts memories in descending order (matching SQL store behavior). This sounds small, but it eliminates a class of “works in prod, fails locally” debugging sessions where retrieval order changes agent behavior. ### Dependency maintenance - A broad round of dependency updates landed across TypeScript tooling and Rust crates (examples mentioned include vitest/bun and tokio/reqwest). Expect the usual follow-on: faster builds in some places, occasional type strictness changes in others. --- ## 3) Community Spotlight (Discord) ### Security: fast moderation + consistent messaging Over multiple days, community members and mods responded quickly to scam activity: - A phishing incident hit the arena channel with fraudulent airdrop links; moderators removed malicious accounts and reiterated a clear rule: **airdrop tags in Discord are always scams**. - In discussion, members issued repeated scam warnings when suspicious users appeared. If you’re new: official announcements should come only through recognized channels—never via random “support tickets,” DMs, or airdrop pings. ### Ecosystem clarity: ElizaOK vs elizacloud A helpful clarification circulated: - **ElizaOK is built with elizacloud** and currently has **no separate token**. - Users registering via ElizaOK **flow into elizacloud**. This kind of product-map clarity is important as more apps and entry points appear. ### Builders helping builders - **stan0473** discussed building a “plugin for scammers” (i.e., counter-scam tooling), and **odilitime** offered to share an existing starter plugin. It’s a nice example of the community treating security as something we can also *productize*—not just moderate. ### Legal discussion (high-level) The community discussed a newly filed lawsuit (federal class action) tied to AI16Z / ElizaOS. **Odilitime** stated the team will respond through lawyers, emphasizing they have code and documentation supporting what was built and describing the suit as without merit. While details are best handled formally, it was reassuring to see calm, consistent communication in-channel. --- ## 4) Token Economics: AI16Z token & auto.fun ### AI16Z token migration: window closed - The token migration period is **officially closed**. A community member reported being unable to migrate remaining funds and then falling for a fraudulent “support ticket” scam—an important reminder that migration events are prime targets for impersonators. ### Staking status - Mods confirmed: **staking is not currently available** for ElizaOS-related tokens. ### Chains & deployment - The token was described as deployed on **Solana, BSC, and Base**. ### auto.fun - No concrete, shippable updates on **auto.fun** were surfaced in the provided discussions this week. If you’re building around auto.fun, keep an eye on official announcements and roadmap posts; avoid acting on rumors or “support” DMs. --- ## 5) Coming Soon Here’s what to watch for next: - **ElizaOS v3 nearing release:** satsbased shared that v3 is “nearly ready” and will enable **agents to generate revenue**—a major milestone for the ecosystem’s sustainability and for builders who want a direct path from capability → income. - **Auth authorize flow migration to Steward (WIP):** Expect more tightening around the authorize flow as Steward becomes the consistent session backbone. - **Plugin registry CI fix:** The OIDC permission issue in the registry workflow needs a repo-level configuration change; once fixed, it should unblock incoming ecosystem PRs. - **PII sanitization layer:** A new request surfaced for a PII sanitization layer—this is likely to become more important as LifeOps-style agents handle sensitive personal context. --- ## 6) Resources (links) - **Plugin registry PR blocked by CI config:** - PR #346 (elisym plugin registry entry): https://github.com/elizaos-plugins/registry/pull/346 - **Elisym integration context (Discord coders channel thread):** - https://discord.com/channels/1253563208833433701/1300025221834739744 - **Lawsuit discussion thread (Discord discussion channel):** - https://discord.com/channels/1253563208833433701/1253563209462448241 - **Examples directory for building from docs:** - https://github.com/elizaOS/eliza/tree/v2.0.0/examples - **Elisym plugin overview (from community write-up):** - Integrates ElizaOS v1 agents into a decentralized marketplace flow (Nostr capability cards + encrypted job requests + SOL payments on Solana), with extensive tests and build provenance mentioned in the release notes.