# ElizaOS Weekly Newsletter (2026-03-02) **Week of 2026-02-23 to 2026-03-01** ## 1) Executive Summary **1) Prediction-market direction got more concrete.** ElizaBAO shared progress on a **custom ElizaOS v2.0 integration for the Milady project** that includes a **Polymarket plugin**—a meaningful signal that “agents + markets” (and verifiable oracle / prediction primitives) are becoming a first-class use case rather than a side experiment. **2) Community-built infrastructure and “real-world” plugins stood out.** Two notable community efforts gained traction: - **zeitgaist**, a VPS orchestration/swarm deployment system that can use ElizaOS or OpenClaw for communications. - A **credit-building automation plugin** (with certified mail support) that sparked an important compliance discussion around FCRA safeguards. **3) Reality check on versions, breakage, and autonomy options.** Discord discussions converged on a practical takeaway: **v2.0.0 is still alpha with frequent breaking changes**, many **plugins may fail out-of-the-box** on older runtimes (e.g., 1.7.2), and autonomy exists in multiple flavors (plugin-based, built-in, and project-specific). The community is aligning around clearer guidance—especially “what to use in production.” --- ## 2) Development Updates (Framework, Plugins, Reliability) ### Version guidance: “alpha” vs “v2-develop” A recurring theme this week was **runtime fragmentation and plugin compatibility**. Developers reported that several plugins (e.g., Linear, Rolodex, Memory) can be **broken out-of-the-box on 1.7.2**, requiring manual patching. In response, community guidance leaned toward: - **Use `v2-develop`** when you need *more mature, stable-ish* behavior (relative to v2.0.0 alpha). - Treat **v2.0.0 as alpha**, where breaking changes are expected during the rollout. ### Known pain points called out - **bcrypt-related issue in v2.0.0** was referenced as something that may require patching. - Concern about **plugins “creeping back into the core”** surfaced, referencing **elizaos/eliza PR #6531** as something worth reviewing from an architecture/maintenance standpoint. ### Autonomy: three paths emerging The community clarified that “autonomy” currently isn’t a single switch—it’s an ecosystem of approaches: 1. **`plugin-autonomous`**: periodic “thinking” so an agent can execute tasks without a user prompt. 2. **Built-in autonomy in v2.0.0** (attributed to Shaw): integrated autonomous behavior as part of the runtime direction. 3. **Milady project autonomy**: described as more OpenClaw-like, suggesting deeper “agent OS” behaviors. A practical gap remains: developers asked how to implement **cron-like scheduling** cleanly (and whether it’s configurable via chat). The older **tasks system** was compared to cron behavior, but not necessarily chat-accessible; **plugin-pim** was mentioned as a possible bridge. ### Regulated automation: quality meets compliance The credit-building plugin announcement was recognized as a potential “plugin-form candidate” (i.e., meeting a quality bar for broader adoption), but it also triggered an important technical/product requirement: **FCRA compliance verification and safeguards** to prevent improper disputes. This is a strong example of the community pushing beyond demos into “production consequences” territory. --- ## 3) Community Spotlight (Notable Contributions & Discussions) ### Meme Broker’s “zeitgaist” orchestration stack The **zeitgaist** project is a compelling “agents managing infrastructure” direction, combining: - **Conway terminals** for provisioning VPS instances - **OpenClaw** for swarm orchestration - **ElizaOS or OpenClaw** for communication between components The developer also candidly noted a visibility challenge—highlighting an ongoing opportunity for the community: **better discovery paths for serious third-party builds**. ### Credit-building automation plugin + compliance discussion The plugin’s certified-mail capability sparked serious questions: *How do we prevent misuse? How do we verify compliance?* The follow-up from Caesar on FCRA safeguards is exactly the kind of scrutiny that makes the ecosystem safer and more credible. ### Production-grade systems talent joins the conversation In **#coders**, **aicodeflow** introduced themselves with hands-on experience in **healthcare/finance/e-commerce AI systems**, emphasizing reliability, messy data, latency, and long-term maintenance. That’s a valuable mindset for ElizaOS as more teams attempt “agents with SLAs,” not just prototypes. ### Security & onboarding: scam bots remain disruptive Multiple users reported scam bots targeting new posters (often via DMs or fake “support” outreach). Mods acknowledged the problem and are actively managing it, but the issue is still impacting onboarding—especially for newcomers asking how to start contributing. --- ## 4) Token Economics (AI16Z → elizaOS, auto.fun) ### Migration status: closed Several questions this week repeated a key update: **the migration window from ai16z to elizaOS has ended**. Community members were clearly told that **migration is no longer available**, and importantly, newcomers were warned to ignore anyone offering “help” via DMs. ### Naming clarity A small but important clarification resurfaced: the community emphasized the correct token reference is **$elizaOS** (not “$eliza”). ### auto.fun: no confirmed weekly change notes in the provided logs There weren’t concrete, verifiable update details in this week’s provided data regarding **auto.fun** feature releases or parameter changes. If you saw claims elsewhere, treat them as unconfirmed unless they’re posted in official channels or linked from the team. --- ## 5) Coming Soon (What to Watch Next) - **Milady + Polymarket plugin (ElizaOS v2.0 custom build):** ElizaBAO offered to share the version—expect follow-up from builders who want prediction-market agents and verifiable-oracle style flows. - **Clearer “what branch should I use?” guidance:** recurring confusion (alpha vs v2-develop) suggests we’ll likely see documentation or pinned guidance requested by the community. - **Autonomy ergonomics:** expect more experimentation around cron-like scheduling, “periodic thinking,” and operational safety (rate limits, permissions, confirmations). - **Compliance-first plugin standards:** the credit-builder plugin discussion is a preview of what’s coming as ElizaOS moves into regulated domains—expect templates/checklists for safeguards. - **Anti-scam onboarding hardening:** community pressure is rising to reduce DM scams and impersonation, especially for first-time posters. --- ## 6) Resources (Links & References) ### Key repos shared this week - **zeitgaist (VPS orchestration / swarm automation):** https://github.com/NewSoulOnTheBlock/zeitgaist - **plugin-conway (Conway.tech integration):** https://github.com/NewSoulOnTheBlock/plugin-conway ### Referenced PR - **elizaos/eliza PR #6531** (plugins reintroduced concern): https://github.com/elizaos/eliza/pull/6531 ### Discord threads (weekly highlights) - **#discussion (migration status, scams, Milady/Polymarket mention):** https://discord.com/channels/1253563208833433701/1253563209462448241 - **#coders (aicodeflow intro / collaboration):** https://discord.com/channels/1253563208833433701/1300025221834739744 ### If you want to help this week - Share your preferred **“production setup”** (runtime + branch + plugin set) and what broke. Real matrices beat guesses. - If you’ve tested **plugin-autonomous / built-in autonomy**, post notes: what triggers, what guardrails, what failure modes. - Report scam bots via the proper mod flow—**do not engage via DMs**, and never trust “migration help” offers.