## Intel — 2026-04-12

### Data coverage & confidence
- **Discord coverage:** Latest available is **2026-04-10** (plus **2026-04-09**). **No 2026-04-11/12 logs found**, so community signals may be undercounted.
- **GitHub coverage:** Month-to-date snapshot (**2026-04-01 → 2026-05-01** partial) + weekly summary (**Apr 5–11**).

---

## 1) Data Pattern Recognition

### Development velocity & trend
**Month-to-date (Apr 1 → May 1 window, as of snapshot)**
- PRs: **4 opened**, **3 merged**
- Issues: **7 opened**, **1 closed**
- Contributors: **14 active**
- Code churn: **+6,785 / -3,732** across **81 files**, **70 commits**

**Trend interpretation**
- Velocity is **high but spiky**, driven by a small number of large PRs (notably core/runtime changes and template migrations).
- A notable pattern: **“medium-risk” core changes landing while multiple P1 regressions are flagged by automated review**, indicating review/QA bandwidth may be the current constraint rather than implementation capacity.

### Community engagement patterns
From the latest Discord days (Apr 9–10):
- **Developer integration support demand** is concentrated on **ElizaOS v2 Socket.IO protocol details** (message types, payload schema, auth requirements).
- **Economic/token comms demand** is persistent: repeated requests for **utility, airdrops, buybacks, and Jeju gas fees**; sentiment shows **frustration with lack of timelines/clarity**.
- **Operational support demand**: wallet verification / Collab.land issue surfaced and remained **unresolved**.

### Feature adoption signals (qualitative)
- **Socket.IO + custom dashboard setups** are actively being built (HTTP polling fallback, local model hosting via Nosana GPU, dashboard split ports).
- **No-code/serverless deployment** interest exists (Hatcher.host beta pitch) suggesting a segment of users wants “deploy without infra.”
- **Ecosystem/plugin growth** continues (wallet/economic/security plugins proposed), aligned with the weekly strategic pivot toward **identity + economic layer**.

### Pain point correlation across channels
| Pain Point | Where observed | Correlated risk |
|---|---|---|
| Missing/insufficient **v2 Socket.IO** canonical docs | Discord (Apr 10) | Increased support load; fragmented third-party implementations; integration bugs |
| **Token/economic roadmap ambiguity** (airdrop/buyback/gas fees) | Discord (Apr 10) | Trust erosion; repeated questions crowd out technical channels |
| **Onboarding failures** (Bun postinstall / `elizaos create`) | GitHub issue #6704 | Direct funnel drop-off; negative first-run experience |
| Core behavior changes shipping with **P1 logic bugs** flagged (routing/memory) | PR reviews (#6712, #6562 notes, #6701) | Production regressions; increased incident/support burden |

---

## 2) User Experience Intelligence

### Feedback categorized by impact & theme

**High impact (blocks adoption / breaks builds)**
1. **`elizaos create` fails on macOS due to Bun postinstall dependency behavior** (Issue #6704)  
   - Impact: prevents new projects entirely; CLI cleans up directory leaving “nothing behind” → especially damaging UX.
2. **Group addressee routing P1 bug** in PR **#6712** (aliasEntity ambiguity)  
   - Impact: silent failure of “addressed to self/other” detection in multi-agent/group rooms; risks bot noise or non-responsiveness.

**Medium impact (integration friction / slows developers)**
1. **ElizaOS v2 Socket.IO protocol unclear** (Discord Apr 10)  
   - Users need message enums, required/optional payload fields, DM channel creation programmatically.
2. **Wallet verification via Collab.land unresolved** (Discord Apr 10)  
   - Onboarding/support friction for community access gating.

**Sentiment/Trust (community temperature)**
1. **Token utility + buyback/airdrop timing unclear** (Discord Apr 10)  
   - Sentiment: frustration; repeated follow-ups indicate prior answers aren’t satisfying because they lack specificity.

### Usage patterns vs intended design (inferred)
- Users are **still investing in v2 integrations** (Socket.IO dashboards) while team focus is stated as **v3** → mismatch creates confusion and perceived abandonment risk for v2 builders.
- Deploy experience demand is bifurcating:
  - Power users: custom local model + GPU + dashboard orchestration.
  - Broad users: “no-code, serverless deploy” (Hatcher.host interest).

### Implementation opportunities (UX wins)
- Provide a **single authoritative “Socket.IO Protocol for v2” reference** (enums + payload schemas + auth examples) to reduce “query the codebase” burden.
- Add “**don’t delete scaffold on failure**” behavior to `elizaos create` and surface a guided fix checklist.

---

## 3) Strategic Prioritization (Impact × Risk × Dependencies)

### Critical path dependencies (next 1–2 weeks)
1. **Onboarding reliability** (Issue #6704) blocks growth and amplifies support load.  
   - Dependency: package/dependency model for bun runtime vs types; CLI template behavior.
2. **Core correctness in group routing + memory** affects all connectors and multi-agent rooms.  
   - Dependency: fix P1 aliasEntity bug in #6712 before merge; validate memory persistence edge-cases noted in prior core changes.
3. **Docs + comms**: v2 Socket.IO docs and token comms reduce churn/noise.

### Initiative scoring (recommended)
| Initiative | User impact | Tech risk | Effort | Priority |
|---|---:|---:|---:|---|
| Fix `elizaos create` Bun dependency/postinstall failure (#6704) + change “cleanup on fail” | Very high | Low–Med | Small–Med | P0 |
| Ship canonical **v2 Socket.IO protocol** documentation (enums, payloads, auth, DM creation) | High | Low | Small | P0 |
| Block merge of #6712 until **aliasEntity ambiguity** fixed + add targeted tests | High | Med | Small | P0 |
| Resolve Collab.land verification playbook (triage + pinned guide) | Medium | Low | Small | P1 |
| Token comms: publish a **bounded statement** (what is known, what is TBD, next update date) | Medium–High | Low | Small | P1 |
| Review/iterate plugin-mnemopay (#6701) gating issues (persistence, NaN guard, null safety, tests) | Medium | Med | Med | P2 |
| Ecosystem: clarify “elizabao_ai” status/usage (what it is + current capabilities) | Medium | Low | Small | P2 |

---

## Quantitative Targets (next 7 days)
- **Onboarding:** reduce “create fails” reports by shipping a fix + doc within **7 days**; add a CI smoke test: `elizaos create && bun run build` on macOS runners.
- **Docs:** publish **1** Socket.IO v2 protocol page + **1** runnable example (join room, send message, auth with entityId UUID).
- **Support deflection:** pin **2** guides in Discord:
  - “Wallet verification / Collab.land troubleshooting”
  - “v2 Socket.IO quickstart & message types”

---

## Actionable Recommendations (immediate)

### Engineering (P0)
1. **Fix #6704 (Bun postinstall)**
   - Remove `bun` from runtime dependencies where appropriate; replace with `@types/bun` in devDependencies.
   - Change CLI behavior: **do not delete generated project on failure**; keep directory + write `FAILURE.md` with detected cause and remediation.
2. **Gate core merges with P1 fixes**
   - #6712: fix aliasEntity token ambiguity and add a regression test specifically covering agents with **entityId ≠ agentId**.
   - Establish a “P1 from automated review must be resolved” merge checklist for core/runtime PRs.

### Documentation (P0)
1. **Canonical Socket.IO v2 protocol reference**
   - Include: `type` enum mapping (ROOM_JOINING=1, SEND_MESSAGE=2), required fields, example payloads, auth (`entityId` UUID), and fallback behavior (polling).
   - Add “How to programmatically create a DM channel” (even if “not supported → recommended workaround”).

### Community/Comms (P1)
1. **Token/economic clarity without overpromising**
   - Post a short “state of play” with: what’s confirmed, what’s not decided, and a **next update date**.
2. **elizabao_ai explainer**
   - One-paragraph definition + “what you can do today” + where to follow updates to absorb recurring questions.

### Support ops (P1)
- Collab.land: create a structured intake (wallet type, chain, screenshots, error string) and an escalation path; convert the recurring issue into a tracked FAQ item.