# ElizaOS Weekly Newsletter (2026-02-23 → 2026-03-01) ## 1) Executive Summary **1) Community-built infrastructure got a serious boost with ZeitGaist + Conway.** Meme Broker showcased **ZeitGaist**, a VPS orchestration system that chains together **Conway terminals (provisioning)** → **OpenClaw (swarm orchestration)** → **ElizaOS/OpenClaw (agent-to-system comms)**. Alongside it, they shared an early but promising **Conway.tech plugin** aimed at permissionless cloud VMs, multi-provider inference, and domain registration for agent operations. **2) Clearer (if still bumpy) guidance emerged on versions, plugins, and autonomy.** Developers repeatedly surfaced the same pain point: **plugin breakage across runtime versions** and uncertainty about what’s “production-ready.” The most consistent guidance in Discord this week: **prefer `v2-develop` for more mature 1.x codepaths**, treat **v2.0.0 as alpha**, and expect breaking changes while the rollout stabilizes. **3) The community leaned into real-world use cases—plus the compliance/security realities that come with them.** A “credit building” automation plugin discussion pushed beyond demo territory into **regulated workflows** (certified mail, FCRA concerns). In parallel, members reinforced operational safety with a reminder that **DM/ticket-link scams are active**—a good nudge as the ecosystem grows. --- ## 2) Development Updates (Framework, Plugins, Bugs) ### Versioning reality check: `v2-develop` vs “alpha” (v2.0.0) A recurring thread was **how to choose a stable base** while the framework evolves quickly: - **Reported issue:** Multiple plugins (notably `plugin-linear`, `plugin-rolodex`, `plugin-memory`) were described as **broken out-of-the-box on 1.7.2**, requiring manual patching. - **Community guidance:** v2.0.0 is “very much alpha” during rollout; **`v2-develop`** was repeatedly recommended for those wanting fewer sharp edges while still staying current. ### Autonomy: three paths are in play Autonomous behavior came up in practical “how do I run cron-like tasks?” terms. The ecosystem currently has **multiple autonomy approaches** discussed in Discord: - **`plugin-autonomous`**: periodic “thinking” loops for task execution - **v2.0.0 built-in autonomy**: referenced as “Shaw’s autonomous system” - **“milaidy” project**: described as a more comprehensive autonomy approach, closer in spirit to OpenClaw-style orchestration One key takeaway: the community still wants a **canonical, documented recipe** for cron-like operations (polling Linear issues, summarizing meetings, triggering PR drafts) that works across versions. ### OpenClaw vs ElizaOS: a pragmatic comparison A helpful production-oriented comparison was shared: - **ElizaOS**: framed as **more stable** and better aligned for **enterprise/financial data safety** - **OpenClaw**: framed as more like a “full OS” (browser control, nodes, sessions), but with **more frequent breaking changes** This isn’t an either/or so much as a signal that teams should choose based on **risk tolerance** and **operational requirements**. ### Bugs & open technical questions worth answering Several items remained unresolved (and are good candidates for maintainers or experienced builders to weigh in on): - **Twitter input issues**: needs clarification on **which product + which version** before troubleshooting can proceed - **Code bot + org repos**: question open on whether the bot “follows” organizational accounts when used in org contexts - **bcrypt issue in v2.0.0**: referenced as requiring patches (status not confirmed in the week’s chat) --- ## 3) Community Spotlight (Notable Contributions & Discord Discussions) ### Project Showcase: ZeitGaist orchestration (Meme Broker) ZeitGaist stood out as a concrete, systems-level contribution that goes beyond chat agents: - **Conway terminals** for VPS provisioning - **OpenClaw** to orchestrate swarms - **ElizaOS/OpenClaw** for communication handling The meta-story: the builder felt the project wasn’t getting enough attention. A simple but real piece of community advice landed well: **“Onboard users one at a time.”** If you’re looking for a place to contribute, this is an ideal target for **docs, quickstarts, demo videos, and reproducible deployments**—all high-leverage for adoption. ### Regulated automation: Credit-building plugin + compliance questions A “credit building” plugin was introduced with **certified mail sending** as a real-world capability, and it was even called out as a potential “plugin-form candidate” (i.e., a quality bar moment). The community immediately raised the right hard question: - **How do we verify FCRA compliance and prevent improper disputes?** This is exactly the kind of discussion that helps ElizaOS mature: it’s not just “can the agent do it,” but “can it do it safely, legally, and with auditable safeguards.” ### Safety moment: scam awareness A community member reminded everyone that **ticket links and DMs can be scams**, and clarified they are not a team member. As the ecosystem expands, this kind of consistent hygiene messaging is crucial—especially with tokens and migrations discussed in the same spaces. --- ## 4) Token Economics (AI16z token + auto.fun) ### Token naming + migration clarity Two token-related points surfaced: - There’s still confusion in the community between **$elizaOS** and “$eliza.” Discord guidance this week reiterated: **the token is $elizaOS**. - A question resurfaced about whether **ai16z → elizaOS migration** is still possible after the previously stated deadline (Feb 4). No definitive in-thread resolution was captured this week—so this remains a good candidate for an official FAQ refresh. ### Market chatter caveat A bot flagged **ai16z** as “interesting,” but it was also noted that the referenced models/analysis may be **outdated**. Treat automated token takes as **signals, not sources of truth**. ### auto.fun No concrete **auto.fun** development updates were shared in the provided Discord logs for this week. If there are releases or parameter changes in-flight, consider posting a short weekly changelog in Discord to keep builders aligned. --- ## 5) Coming Soon (What to Watch Next) - **A clearer “production path” doc**: a simple matrix for *runtime version → known-good plugins → autonomy option* would unblock many teams. - **Cron-like autonomy recipes**: community demand is strong for a reference implementation (e.g., “hourly Linear poll + memory update + human approval step”). - **Compliance-ready plugin patterns**: expect more pressure for reusable guardrails (confirmations, audit logs, policy gates) as plugins move into regulated domains. - **Visibility push for infra tools**: ZeitGaist + plugin-conway could become a repeatable template for “agent-operated infrastructure,” but it needs community testing and walkthroughs. --- ## 6) Resources (Links & Threads) **Key repositories shared** - ZeitGaist (VPS orchestration): https://github.com/NewSoulOnTheBlock/zeitgaist - Conway.tech plugin: https://github.com/NewSoulOnTheBlock/plugin-conway **Discord discussions (week highlights)** - ZeitGaist showcase + visibility discussion (💬-coders): https://discord.com/channels/1253563208833433701/1300025221834739744 - Version selection + autonomy questions (💬-discussion): https://discord.com/channels/1253563208833433701/1253563209462448241 **Referenced PR / thread to review** - Concern about plugins “creeping back in” (mentioned alongside **PR #6531**): https://github.com/elizaos/eliza/pull/6531 **Background reading (latest available GitHub weekly summary in dataset)** - Project Weekly Summary (Feb 15–21, 2026): *(provided in community knowledge dump; useful context for beta prep, SAID, and plugin registry momentum)*