# ElizaOS Developer Update (2026-02-22 → 2026-02-28)

## 1) Core Framework

### Branching / version-line clarity: `v2-develop` created to preserve mature 1.x
A critical repo hygiene issue surfaced this week: the `develop` branch unexpectedly contained **2.0.0** code rather than the expected **1.x** lineage, and it wasn’t traceable/repairable through normal PR history. To keep 1.x users unblocked during the V2 rollout, the team established a dedicated **`v2-develop`** branch as the recommended “stable-ish” line for 1.x-era runtime compatibility while V2 remains alpha.

*Impact for developers*
- If you are building on 1.x plugins/runtime semantics, **do not assume `develop` maps to 1.x**.
- Prefer **`v2-develop`** for “mature 1.x code” during the transition window (per maintainer guidance on Discord).

```bash
# If you are tracking the core repo directly:
git fetch origin
git checkout v2-develop
```

### Architectural tension: plugins “creeping back” into monorepo
Maintainers flagged concern that plugins are being reintroduced into the main codebase (contrary to the direction of keeping plugins external/registry-driven), calling out **PR #6531** explicitly for review:
- https://github.com/elizaos/eliza/pull/6531

This is an architectural governance point: it affects dependency boundaries, release cadence, and how breaking changes propagate into downstream builders.

### Autonomy in the ecosystem: three parallel implementations
Discord discussion clarified that “autonomous agents” currently exist in three distinct forms:
1. **`plugin-autonomous`**: periodic “think” loop for task execution.
2. **V2.0.0 built-in autonomy** (Shaw’s system): integrated into the alpha V2 runtime line.
3. **`milaidy` project**: broader autonomy approach “more like OpenClaw”.

Additionally:
- The **1.x task system** behaves like cron-style scheduling, but is **not chat-configurable**; `plugin-pim` may eventually cover chat-accessible scheduling (unverified; action item to confirm).

## 2) New Features

### `plugin-credit-builder`: regulated-industry automation + certified mail execution
A notable ecosystem feature shipped externally this week: **credit building automation** as an ElizaOS plugin with real-world delivery via certified mail.

- Repo: https://github.com/NewSoulOnTheBlock/plugin-credit-builder (preview image link surfaced in Discord OpenGraph)
- Discussion thread: https://discord.com/channels/1253563208833433701/1300025221834739744

**Capabilities highlighted**
- FCRA/ECOA/FDCPA dispute letter generation (19 letter types mentioned)
- FICO analysis + business credit management workflows
- **Lob certified mail integration** (the plugin can send real certified mail autonomously)

*Developer note:* this plugin is being evaluated as a “plugin-form candidate” (i.e., meeting higher packaging/quality expectations for broader adoption).

#### Recommended safety pattern (human-in-the-loop) for high-stakes actions
Given the regulatory and financial impact, the community strongly recommended human confirmation gates for actions with real-world consequences (mail dispatch, disputes, escalations). A minimal pattern is to split “draft” vs “execute” actions:

```ts
// Pseudocode illustrating a safe 2-step tool split
export const actions = [
  {
    name: "draft_dispute_letter",
    argsSchema: DraftSchema,
    handler: async (ctx, args) => {
      const letter = await generateLetter(args);
      return { ok: true, letter, requiresConfirmation: true };
    }
  },
  {
    name: "send_certified_mail",
    argsSchema: SendSchema,
    handler: async (ctx, args) => {
      // Enforce explicit confirmation and audit logging
      if (!args.confirmed) return { ok: false, error: "Confirmation required" };
      await auditLog(ctx, args);
      return await lobSendCertified(args);
    }
  }
];
```

### Cross-platform posting automation (Discord/X/Telegram)
Community work is underway to automate cross-platform bot posting (Discord/X/Telegram). This is not yet a merged framework feature, but it signals increasing demand for a unified “publisher” capability across social plugins (action item tracked in Discord).

## 3) Bug Fixes (and critical known issues)

### V2.0.0 bcrypt issue (known; requires patching)
Developers reported that **v2.0.0 currently ships with a bcrypt-related issue** that requires patches. No merged fix was referenced in the provided activity, but it is a **known blocker** for some users evaluating v2.0.0.

*Mitigation guidance (current week)*
- If you need fewer surprises: use **`v2-develop`** instead of **v2.0.0** while the alpha hardens.

### 1.7.2 plugin breakage: multiple plugins broken OOTB
Developers reported that in **ElizaOS 1.7.2**, several plugins are broken “out of the box” and require manual patching:
- `plugin-linear`
- `plugin-rolodex`
- `plugin-memory`

This is likely a symptom of rapid runtime/API churn and multiple runtime versions in circulation (maintainers reiterated the project is in an **alpha** phase with frequent breaking changes).

### Twitter “input” issues (unresolved triage)
A Twitter input malfunction was reported, but troubleshooting is blocked pending environment details (which runtime/version/product):
- Discord note (triage request): https://discord.com/channels/1253563208833433701/ (see 2026-02-26 coders discussion summary)

## 4) API Changes (developer-facing)

No concrete, merged API signature changes were explicitly recorded in the provided week’s activity logs. However, there are **important compatibility signals**:

- **Version-line divergence** (1.x vs v2.0.0 alpha vs v2-develop) is currently the dominant “API surface” risk: downstream plugins may compile but fail at runtime due to behavioral changes.
- Open requests that may become API changes soon:
  - Custom OpenAI endpoint support request (OpenAI-compatible third-party endpoints): https://github.com/elizaos/eliza/issues/6490
  - Duplicate LLM calls when a URL is present (webapp double-processing as text + attachment): https://github.com/elizaos/eliza/issues/6486

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

### Twitter
- Reported issue: Twitter input not functioning (version unspecified; needs reproduction details).
- Recent ecosystem direction (from community needs): expand beyond posting to include reliable ingestion + tool execution and reduce auth retry loops (builders should watch plugin-twitter changes closely if they’re pinned to older versions).

### Discord / Telegram
- Cross-post automation work announced (Discord → X/Telegram). Not yet upstreamed, but aligns with demand for a unified “broadcast” workflow with per-platform formatting adapters.

### Security reminder for social channels
Community warned about scam “ticket links” and DMs impersonating team members. If you operate bots across Discord/Telegram, ensure:
- allowlists for admin commands,
- signed release artifacts,
- and no credential exchange via DMs.

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

No provider integrations were confirmed as merged/updated specifically during this week in the supplied data. Two provider-related signals to watch:

- **OpenAI endpoint flexibility request** (OpenAI-compatible providers like SiliconFlow): https://github.com/elizaos/eliza/issues/6490  
- Community noted that some token/model analyses circulating in chat were using **outdated models**, suggesting devs should validate benchmarks/provider defaults against current configs.

## 7) Breaking Changes (V1 → V2 migration warnings)

### V2.0.0 is alpha and introduces systemic breaking shifts
Maintainers reiterated that **v2.0.0 is “very much alpha”** and “almost every release contains breaking changes” due to multiple runtime versions evolving concurrently.

Key breaking-change themes called out by builders this week:
- Plugin compatibility: multiple plugins broken on 1.7.2; v2 requires additional porting/patching.
- Auth/crypto dependency issues: bcrypt problem in v2.0.0 (patch-required).
- Repository structure expectations: don’t rely on `develop` meaning “latest stable 1.x”; use `v2-develop` as directed.

### Action required for teams shipping production agents
- Pin to a known-good branch/tag and lock plugin versions.
- Add CI that runs a smoke agent session using your exact plugin set.
- For high-stakes automations (financial/legal), implement explicit confirmation + audit trails before execution.

**Links referenced this week**
- PR to review (plugins reintroduced): https://github.com/elizaos/eliza/pull/6531
- Credit builder plugin: https://github.com/NewSoulOnTheBlock/plugin-credit-builder
- Open issue (URL causes duplicate LLM calls): https://github.com/elizaos/eliza/issues/6486
- Open issue (custom OpenAI endpoint): https://github.com/elizaos/eliza/issues/6490
- ElizaOS news companion site (release context): https://elizaos.news