## Intel Report — 2026-04-11 (ElizaOS)

### 1) Data Pattern Recognition (Signals, Trends, Quant)

**Development velocity (GitHub)**
- **Month-to-date (Apr 1 → May 1 window snapshot):** **4 new PRs (3 merged)**, **7 new issues**, **1 closed issue**, **14 active contributors**.
- **Code churn (recent snapshot):** **+6,785 / -3,732 LOC**, **81 files**, **~70 commits**.
- **Work mix trend:** heavy “core hardening / runtime composition / messaging reliability” plus “agent economy layer” plugin proposals.
- **Risk trend:** multiple “medium-risk” core PRs touching message pipeline + runtime composition; reviewer bots flagged P1/P0-type logic risks (see Strategic section).

**Community engagement (Discord)**
- Dominant topics over last 72h:
  1) **v2 Socket.IO integration** (deep technical debugging, repeated doc requests)
  2) **Token utility / airdrops / buybacks / Jeju gas fees** (high repetition + frustration)
  3) **Onboarding/support friction** (Collab.land wallet verification unresolved)
  4) Early ecosystem promos (deployment platforms like Hatcher.host; external projects like promdict.ai)
- **Engagement shape:** high question volume, low closure rate on sensitive/operational topics (tokenomics + support), strong self-service behavior in dev channel (integrators reverse-engineering protocols).

**Feature adoption / usage patterns (inferred from discussion + repo direction)**
- **v2 still actively used** for custom dashboards + Socket.IO integrations despite team focus shifting to v3.
- **Local model hosting is real usage:** Qwen3.5 via Nosana GPU (port 3001) + dashboard (8080) indicates “bring-your-own-inference” deployments are happening now.
- **Economic layer interest rising:** x402 usage-based billing (Orbis on Base) and agent-economy plugins are surfacing frequently, aligning with weekly strategic pivot toward “trust/identity + agent finance.”

**Data quality / instrumentation**
- A “no activity recorded” daily activity JSON conflicts with actual Discord summaries for 2026-04-10. This suggests **telemetry pipeline drift** (collector outage / channel mapping issue) and should be treated as an ops risk (missed trend detection).

---

### 2) User Experience Intelligence (Themes, Impact, Sentiment)

**A. Developer experience (High impact, high frequency) — “Canonical protocol docs missing”**
- Pain point cluster: **ElizaOS v2 Socket.IO**
  - Working pattern discovered: `socket.emit('message', { type: 1|2, payload })`
    - **type=1:** ROOM_JOINING  
    - **type=2:** SEND_MESSAGE  
  - Auth requirement: `entityId: UUID` in socket options.
  - Missing: complete enum, payload schemas (required vs optional), programmatic DM channel creation/discovery.
- UX impact:
  - Integrators are spending “hours debugging” and resorting to **reading source with Cursor** as the primary documentation path.
  - This increases integration time, support load, and probability of community-maintained “folk docs” diverging from actual behavior.

**B. Product communications (High sentiment risk, medium technical impact) — “Tokenomics ambiguity”**
- Repeated questions:
  - Airdrop eligibility/plan: “some planned” but no details.
  - Buybacks + Jeju gas fee timing: “no further plans beyond what was laid out.”
- Observed sentiment: **frustration with vagueness**, perceived lack of roadmap specificity.
- UX risk: this pattern tends to amplify rumors and increases moderation burden.

**C. Support/onboarding (Medium impact, high frustration) — “Verification dead-ends”**
- Collab.land wallet verification issue raised and remained unresolved in-thread.
- UX impact: blocks access/roles; feels like “no support path,” reducing retention for new/returning users.

**D. Safety expectations (Emerging, high severity if unmet)**
- Question raised on preventing unsafe agent operations (unresolved). This aligns with repo-level movement toward **capability-based auth / AgentID**; users are already expecting guardrails.

---

### 3) Strategic Prioritization (What to do next, why, and resourcing)

#### Priority 1 — Ship “v2 Socket.IO Protocol Reference” as a containment doc (High user impact, low-to-medium engineering risk)
**Why now**
- v2 is still in production use; lack of docs is causing direct time loss and integration failures.
- Team focus is v3, but **a doc-only intervention** prevents ongoing churn without diverting core engineering.

**Deliverables (1–2 days of effort)**
- Single canonical page:
  - Connection/auth: `entityId` requirements, polling fallback behavior.
  - Event contract: `message` event + `type` enum list (include numeric codes).
  - Payload schemas: required/optional fields per type (examples + JSON schema snippets).
  - “DM channel discovery/creation”: current supported method; if unsupported, explicitly state limitation + workaround pattern.
- Add a short “version caveat” banner: v2 protocol stability status vs v3.

**Owner / resourcing**
- 1 engineer (or devrel) + 1 reviewer; publish to docs.elizaos.ai.

---

#### Priority 2 — Establish a “Tokenomics Comms Minimum Viable Clarity” cadence (High sentiment impact, low engineering risk)
**Problem**
- Current answers (“planned, no details” / “no one knows”) are accurate but degrade trust when repeated.

**Actionable output**
- Weekly pinned update template:
  - What changed this week (even “no change”)
  - Next disclosure milestone (date or condition-based trigger)
  - Known-unknowns explicitly listed (buyback, Jeju gas fee, airdrop criteria)
- Provide a single linkable “Token Utility & Incentives” page so moderators don’t re-litigate in threads.

**Resourcing**
- Community ops/mod + 1 core stakeholder for approvals.

---

#### Priority 3 — Close the “Collab.land verification” loop with a support runbook (Medium user impact, very low risk)
**Action**
- Publish a runbook: common failure modes, required screenshots/logs, escalation path, expected response time.
- Create a single intake mechanism (Discord form/thread template) to prevent unresolved one-offs.

---

#### Priority 4 — Protect the v3 critical path by triaging current core PR risk (High technical impact)
**Current risk items (from repo review signals)**
- **PR #6712 (group addressee routing):** Greptile flagged a **P1 aliasEntity ambiguity bug** that can nullify name resolution when `agentId ≠ entityId`. This affects “who responds in group rooms,” i.e., user-visible correctness + anti-loop behavior.
- **PR #6701 (plugin-mnemopay):** flagged as **not production-ready** (no persistence, NaN reputation corruption, null deref risks, unbounded memory growth, no tests). If merged prematurely it creates long-tail support and reputational risk.
- **Issue #6704 (elizaos create fails on macOS due to bun dependency):** blocks onboarding; high leverage fix.

**Recommendation**
- Create a “v3 launch blocker” label and gate merges by:
  - Must-fix: addressee routing correctness (anti-loop + correct targeting)
  - Must-fix: CLI create path reliability on macOS (onboarding funnel)
  - Defer: non-essential economy plugins until persistence/testing standards met

**Resourcing**
- 1 core engineer focused on onboarding/tooling reliability (CLI + create path).
- 1 core engineer focused on group routing correctness + regression tests.
- Community plugins (mnemopay, marketplace, safety) go through stricter acceptance checklist: persistence, bounds/limits, null-safety, minimal test coverage.

---

### Key Correlations / Insights (Cross-channel)
- **Docs gaps → engineering distraction:** v2 integrators are forced into source spelunking; core team replies reflect v3 focus, widening the gap. A small documentation patch yields disproportionate reduction in repeated support pings.
- **Safety concerns align with roadmap:** community questions about unsafe operations correlate strongly with repo direction (AgentID/capability tokens). Converting that into a short “safety model” explainer will reduce anxiety and clarify intended guardrail posture.
- **Telemetry mismatch is a hidden risk:** conflicting “no activity” logs reduce the intel function’s accuracy; fix the collector before it masks emerging incidents.

---

### Action List (Next 7 days)
1) **Publish v2 Socket.IO protocol reference** (enum + payload schemas + auth + DM guidance).  
2) **Pin Tokenomics clarity page + weekly cadence post** (single source of truth).  
3) **Collab.land verification runbook + escalation path** (close unresolved loops).  
4) **Triage and fix PR #6712 aliasEntity bug** + add a regression test for `agentId ≠ entityId`.  
5) **Address Issue #6704 (macOS create failure)** by removing bun runtime dependency / adjusting install behavior.  
6) **Repair Discord activity telemetry pipeline** (resolve “no activity recorded” mismatch).