# Intel Brief — 2026-05-08 (covering activity through 2026-05-07)

## 1) Data Pattern Recognition

### Development velocity & trend
- **GitHub (daily, 2026-05-07):**
  - **PRs opened:** 1 (elizaos.github.io — env var typing via `ImportMetaENV` in `next.config.js`)
  - **PRs merged / issues closed:** **0 / 0**
  - Signal: **throughput dip** on the docs site repo despite ongoing ecosystem changes that increase docs demand (auth changes, repo consolidation, plugin migrations).
- **Recent platform trajectory (context from May 5–7):**
  - **May 6:** infra consolidation (ElizaCloud → main `elizaOS/eliza`), hosting move away from Vercel to cheaper containers; x402 routes gained default payment methods.
  - **May 7:** friction shifted to **integration breakage + discoverability gaps** (Twitter auth requirement, missing Hyperfy plugin, stuck summary page).

### Community engagement patterns (Discord)
- **High-signal threads (May 7):** 3
  1) Twitter/X integration auth requirement + pricing concerns  
  2) Hyperfy plugin removed/404 + core/plugin version mismatch  
  3) elizaos.github.io summary/day stuck since May 4
- **Help interactions resolved:** 2 (odilitime→guru0; odilitime→binarycookies)  
- **Assistance offered:** 1 (da4tner→binarycookies)
- **New builder arrival:** 1 (AI full-stack engineer, 8+ years) → opportunity for onboarding conversion if “getting started” pathways are reliable.

### Feature adoption / usage signals (proxy indicators)
- **Twitter integration:** users are actively attempting to run Twitter bots; cost sensitivity is a gating factor. The question repeats across channels → indicates **documentation/UX mismatch**.
- **Hyperfy integration:** at least one active attempt to use a 3D/Hyperfy starter; plugin availability and compatibility are immediate blockers → likely suppressing adoption.

### Pain point correlation across channels
- **Single root theme:** “I can’t reliably find/run the thing the ecosystem claims exists.”
  - Missing plugin repo (404) + version mismatches
  - Daily summaries page stuck (public status signal degraded)
  - Twitter integration requirements changed but not clearly surfaced (behavioral regression for returning users)

---

## 2) User Experience Intelligence

### Feedback themes (categorized by impact)
**A. Plugin availability & compatibility (Hyperfy) — Impact: High**
- Symptom: GitHub link returns **404**; users saw it “days earlier,” implying removal or repo restructuring without a stable redirect.
- Secondary failure: **core/plugin version mismatch** (no compatibility contract, no pinned versions, no migration guide).
- Current workaround (DM zip) is **non-scalable** and creates trust + security concerns (unverifiable artifact provenance).

**B. Integration auth change (Twitter/X) — Impact: Medium–High**
- Users expected prior “login method” to work; now **X API required**.
- Cost concern is primary; “pricing revised and cheaper” helps, but without a **clear doc and expected monthly cost ranges**, users will defer adoption.

**C. Docs/status reliability (daily summary page stuck) — Impact: Medium**
- `elizaos.github.io/summary/day` stuck since **May 4** (≥3 days by May 7; ≥4 days by May 8).
- This page is a **visibility surface** (signals project momentum); being stale undermines external confidence.

**D. Unanswered operational questions (from May 6) — Impact: Medium**
- Hosting costs/hardware feasibility questions left unresolved (Twitter bot + Mac mini). This indicates a **gap in self-host guidance** and a likely source of repeated support load.

### Usage patterns vs intended design
- Users treat integrations as **turnkey starters** (“download starter pack; run against current core”).
- Current reality requires **internal knowledge** (matching versions, hunting removed repos, requesting zip files, interpreting pricing changes).
- This is a mismatch: the ecosystem is evolving quickly (consolidations/migrations), but the **distribution and compatibility UX** hasn’t caught up.

### Sentiment tracking (qualitative)
- **Concern/friction:** Twitter cost + “is it required now?” uncertainty.
- **Frustration/confusion:** plugin disappearance + 404.
- **Positive signal:** new experienced engineer joining; helpful responses from core community members.

---

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

### Priority 0: Restore trust in plugin distribution (Hyperfy incident)
**Why now:** A 404 in a “starter” path is a hard-stop adoption failure and creates repeated support burden.

**Recommended actions (1–2 days to stabilize, then follow-ups):**
1) **Reinstate a stable artifact path**
   - Option A: restore repo or publish a new canonical repo under the current org with a **permanent redirect notice** from the old location.
   - Option B: publish a **tagged release asset** (zip) in GitHub Releases with checksums.
2) **Introduce a compatibility contract**
   - Add `peerDependencies` / explicit `@elizaos/core` version range + a CI matrix that tests against `core@current` and `core@previous-minor`.
3) **Publish a compatibility matrix page**
   - “Core vX ↔ Plugin vY” plus quick fix guidance when mismatched.

**Risk:** Medium (versioning/CI wiring), but high leverage.

### Priority 1: Fix the public-facing summary pipeline (elizaos.github.io/summary/day)
**Why now:** This is a project heartbeat signal and reduces internal support questions when accurate.

**Recommended actions:**
- Triage checklist:
  - Verify GitHub Actions workflow runs since May 4 (permissions, token scopes, schedule triggers).
  - Validate data source endpoints and build output path.
  - Add a **staleness monitor** (badge or banner: “Last updated: …” + alert when >24h).
- If account config is suspected: document the exact setting(s) required (Pages deploy perms, workflow permissions).

**Risk:** Low–Medium (CI/config), high reputational benefit.

### Priority 2: Clarify Twitter/X integration requirements and costs
**Deliverable (same day):** a short doc update + FAQ entry:
- “X API is required for posting” (and what still works without it, if anything).
- Link to current X pricing tiers; provide **typical usage estimates**:
  - e.g., “N posts/day ≈ $/mo” (even if approximate ranges).
- Provide an alternative pathway if available (read-only, manual import, or other social integrations).

**Risk:** Low, immediate reduction in repeated questions.

### Priority 3: Close the self-hosting “cost & hardware” gap
**Deliverable (1 page):**
- Reference deployments:
  - “Twitter bot minimal” (CPU/RAM, expected monthly cost on container host)
  - “Mac mini local” viability checklist (uptime, networking, secrets, logs)
- Include a “bill of materials” for required keys (X, etc.) and expected recurring costs.

**Risk:** Low; reduces support churn and increases builder conversion.

---

## Quantitative Scorecard (Today’s signals)
- **Discord high-signal issues:** 3 (auth change, plugin removal, docs pipeline)
- **Resolved help threads:** 2
- **Workarounds using non-canonical distribution (DM zip):** 1 (flagged as a risk)
- **Public docs/status outage duration:** ≥4 days stale by 2026-05-08
- **GitHub daily throughput (May 7):** 1 PR opened; 0 merged; 0 closed issues

---

## Resource Allocation Recommendation (next 48–72 hours)
- **1 engineer (platform/docs infra):** fix summary pipeline + add staleness indicator.
- **1 engineer (plugin ecosystem):** Hyperfy plugin republish + compatibility enforcement (version ranges + CI).
- **0.5 DevRel/Community Ops:** update Twitter integration docs + self-hosting cost/hardware FAQ; pin in Discord and link in README/docs nav.

---

## Key Dependencies / Critical Path
1) **Canonical plugin distribution path** (repo/releases) must exist before compatibility docs are meaningful.
2) **Summary pipeline fix** may depend on GitHub org/account workflow permissions—needs owner/admin attention if confirmed.
3) **Twitter docs** depend on confirming exact supported modes (post/read-only/login deprecation) so we don’t document incorrect behavior.

---

## Actionable Next Steps (owner-ready)
1) Create issue: **“Re-publish Hyperfy starter + add core/plugin version gates”** (include: redirect plan, CI matrix, compatibility matrix page).
2) Create issue: **“Restore daily summary generation; add staleness banner + alert”** (include: permissions audit).
3) Merge doc PR(s):
   - “Twitter/X: X API required (pricing + setup steps)”
   - “Self-host sizing: Twitter bot + Mac mini baseline”