# ElizaOS Developer Update (2026-02-23 → 2026-03-01)

This update summarizes observed engineering activity across GitHub + developer Discord for the week ending **2026-03-01**.

---

## 1) Core Framework

### Runtime/version guidance: **v2.0.0 is still “alpha”; prefer `v2-develop` for production-ish builds**
Discord consensus this week reiterated that **v2.0.0 is undergoing an active rollout with frequent breaking changes**, while **`v2-develop`** is the safer target if you need “mature 1.x-ish” behavior with fewer surprises.

*Primary context:* developer reports that multiple plugins are broken OOTB on **1.7.2** and require manual patching, while **v2.0.0** also carries known issues (notably a bcrypt-related problem).  
References (Discord):  
- 2026-02-27 thread: plugin breakage + alpha-state clarification (see internal notes in `ai_news_elizaos_discord_md_2026-02-27`)

### “Plugins creeping back into core” concern (codebase hygiene)
A framework-maintenance concern was raised about plugins being reintroduced into the core repo, flagged against **PR #6531**. If your internal fork relies on a strict “plugins stay external” architecture, keep an eye on this thread and downstream merges.

- PR: https://github.com/elizaos/eliza/pull/6531

---

## 2) New Features

### Infrastructure orchestration pattern: **ZeitGaist + Conway + OpenClaw + (optional) ElizaOS comms**
Community member **Meme Broker** shared **ZeitGaist**, a VPS orchestration system that composes:
- **Conway terminals** for provisioning VPS instances
- **OpenClaw** for swarm orchestration
- **ElizaOS or OpenClaw** for inter-component communications

Repos:
- ZeitGaist: https://github.com/NewSoulOnTheBlock/zeitgaist  
- Conway plugin: https://github.com/NewSoulOnTheBlock/plugin-conway  

The Conway plugin was described as enabling:
- permissionless cloud VMs
- multi-provider inference
- domain registration for agents

**Developer takeaway:** This is an emerging “agent infrastructure” blueprint: ElizaOS can sit above provisioning/orchestration layers as the conversational + tool-execution interface, while Conway/OpenClaw handle compute lifecycle and swarm topology.

### Autonomy / cron-like scheduling: three viable approaches discussed
Discord clarified that “autonomy” in the ecosystem currently comes in multiple forms:

1. **`plugin-autonomous`** — periodic “thinking” loop to execute tasks on a cadence  
2. **v2.0.0 built-in autonomy** — “Shaw’s autonomous system” integrated in the alpha runtime  
3. **milaidy project** — broader autonomy, described as closer to OpenClaw-style OS behavior  

Additionally:
- **1.x tasks system** exists and behaves “cron-like”, but is **not chat-accessible**
- **`plugin-pim`** was suggested as a potential bridge for chat-configurable tasking (unconfirmed)

Because APIs differ across runtimes and branches, the most portable implementation remains an external scheduler that triggers agent actions via your own process.

Example: **external cron → invoke an agent action** (conceptual Node.js sketch)
```ts
import cron from "node-cron";
// import { runAgentOnce } from "./your-elizaos-runner"; // depends on your runtime integration

cron.schedule("0 * * * *", async () => {
  // Hourly: poll Linear for blocked issues, then ask agent for suggestions
  // await runAgentOnce({ prompt: "Check Linear for blocked issues and propose next actions." });
});
```

---

## 3) Bug Fixes (Critical)

> No confirmed “merged this week” GitHub fixes were present in the provided dataset. The most impactful items were **active breakages / unresolved issues** surfaced in Discord and requiring maintainer or contributor attention.

### a) Plugin breakage on ElizaOS **1.7.2**
Reported broken out-of-the-box (requiring manual patching):
- `plugin-linear`
- `plugin-rolodex`
- `plugin-memory`

Impact:
- Blocks common enterprise workflows (issue tracking, CRM/contact graph, memory persistence)
- Increases “time-to-first-agent” due to required local hotfixing

Recommended mitigation (until pinned fixes are published):
- Standardize on **one known-good branch/runtime** across your org (see “Breaking Changes”)
- Pin plugin versions and runtime commit SHAs together in a lockstep release file

### b) v2.0.0 **bcrypt issue** (known runtime problem)
v2.0.0 was called out as having a bcrypt-related issue requiring patching. If your deployment relies on bcrypt-backed auth/secrets hashing, validate behavior in staging before promoting.

---

## 4) API Changes

### No explicit API diffs landed in the provided weekly dataset
However, developers should assume **API volatility** across:
- v1.x → v2.0.0 alpha runtime changes
- plugin interfaces that track runtime internals

Practical recommendation:
- Treat ElizaOS runtime + plugin set as a **single versioned platform unit**.
- Maintain an internal compatibility matrix: `{ runtime_sha, plugin_set_sha, node_version }`.

Docs:
- ElizaOS documentation site repo (for tracking doc/version updates): https://github.com/elizaos/elizaos.github.io

---

## 5) Social Media Integrations (Twitter / Telegram / Discord / Farcaster)

### Twitter: “input not working” report (needs repro details)
A developer reported **Twitter input functionality issues**, but troubleshooting stalled pending:
- which ElizaOS version/runtime
- which Twitter plugin/package
- product context (self-hosted agent? hosted service? custom integration?)

Action item for reporters: include a minimal repro bundle
```txt
- runtime branch/commit:
- node version:
- plugin name + version:
- auth mode (oauth/app tokens):
- expected behavior:
- actual behavior + logs:
```

### Cross-posting automation (Discord/X/Telegram)
A separate thread mentioned ongoing work on a bot that can automatically post across platforms (Discord, X/Twitter, Telegram). No PRs/links were included this week; if this is your use case, watch for plugin releases or share requirements in Discord to align on an interface.

---

## 6) Model Provider Updates (OpenAI / Anthropic / DeepSeek / etc.)

### No provider integration changes observed in this week’s dataset
No new merges/issues were provided for OpenAI/Anthropic/DeepSeek/Ollama integrations for 2026-02-23 → 2026-03-01.

If you are actively shipping, consider:
- pinning provider SDK versions
- adding contract tests for tool-calling / structured outputs
- validating embeddings behavior per OS (Linux vs macOS) before release

---

## 7) Breaking Changes (V1 → V2 Migration Warnings)

### Strong warning: **v2.0.0 remains alpha and carries breaking changes + known issues**
From Discord maintainers/devs:
- “almost every release contains breaking changes” (multiple runtime versions in flight)
- v2.0.0 includes autonomy changes and at least one bcrypt-related issue
- production-minded devs were advised to prefer **`v2-develop`** over the alpha channel

### Migration strategy (recommended)
1. **Pick your target**: `v2-develop` (stability) vs v2.0.0 (new autonomy, faster churn)
2. **Freeze a platform bundle**: runtime SHA + plugin SHAs + Node version
3. **Add smoke tests** for your critical plugins (memory + Linear + GitHub + chat)
4. **Roll forward intentionally**: update one dimension at a time (runtime, then plugins)

---

## References / Links Mentioned This Week

- ZeitGaist (VPS orchestration): https://github.com/NewSoulOnTheBlock/zeitgaist  
- Conway plugin: https://github.com/NewSoulOnTheBlock/plugin-conway  
- Core repo PR (plugin/core boundary concern): https://github.com/elizaos/eliza/pull/6531  
- Docs repo: https://github.com/elizaos/elizaos.github.io  
- Discord threads (source summaries):  
  - 2026-02-26: `ai_news_elizaos_discord_md_2026-02-26`  
  - 2026-02-27: `ai_news_elizaos_discord_md_2026-02-27`  
  - 2026-02-28: `ai_news_elizaos_discord_md_2026-02-28`