## Issue Triage — 2026-01-21 (elizaOS)

### 1) **[Migration] Eligibility Mismatch & Snapshot Bug — Tangem Hardware Wallet** (#6369)
- **Current Status:** Open (reported 2026-01-16); 1 comment; awaiting verification/backfill
- **Impact Assessment:**
  - **User Impact:** High (migration portal blocking at least one verified holder; likely affects other hardware-wallet users)
  - **Functional Impact:** Yes (blocks token migration flow before deadline)
  - **Brand Impact:** High (migration trust + “snapshot correctness” credibility)
- **Technical Classification:**
  - **Category:** Bug / UX
  - **Component:** Migration Portal / Snapshot Indexing (backend + frontend wallet connect)
  - **Complexity:** Moderate effort (data reconciliation + portal lookup logic + support runbook)
- **Resource Requirements:**
  - **Required Expertise:** Solana snapshot/indexing, backend ops, portal integration, customer support triage
  - **Dependencies:** Access to snapshot dataset + portal eligibility service; confirm address mapping rules
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P0**
- **Specific Actionable Next Steps:**
  1. Reproduce by querying snapshot balance for address `2SEL...AX8K8` at snapshot slot/time; confirm expected 70k.
  2. Inspect portal eligibility lookup path (wallet connector → address → snapshot record). Identify why only Solflare hot wallet is recognized.
  3. Implement a **manual override/whitelist mechanism** (audited) for disputed addresses with on-chain proof.
  4. Publish a short “Hardware Wallet / Multi-wallet Snapshot Troubleshooting” doc + support intake checklist.
- **Potential Assignees:** Shaw (migration/backend), DorianD (migration rationale/comms), Stan ⚡ (docs), ops-capable core dev familiar with snapshot dataset

---

### 2) **Discord plugin runtime error — undefined `sendMessage`** (elizaos-plugins/plugin-discord **#43**)
- **Current Status:** Open (reported 2026-01-15)
- **Impact Assessment:**
  - **User Impact:** High (Discord is a primary integration surface)
  - **Functional Impact:** Yes (message delivery broken in affected path)
  - **Brand Impact:** High (public-facing agents fail in the most visible channel)
- **Technical Classification:**
  - **Category:** Bug
  - **Component:** Plugin System → Discord Integration
  - **Complexity:** Simple fix to Moderate effort (depending on root cause: API mismatch vs runtime wiring)
- **Resource Requirements:**
  - **Required Expertise:** TypeScript, Discord API adapter layer, eliza runtime messaging contracts
  - **Dependencies:** Confirm compatibility with eliza core version(s) + plugin-discord version(s)
  - **Estimated Effort:** 2/5
- **Recommended Priority:** **P0**
- **Specific Actionable Next Steps:**
  1. Add minimal reproduction (bot start + message send) and capture stack trace + versions.
  2. Identify the expected message transport interface: ensure `sendMessage` is injected/available where called.
  3. Add regression test covering send path + publish patch release for plugin-discord.
  4. Update compatibility matrix (core version ↔ plugin-discord version).
- **Potential Assignees:** Odilitime (plugin/bootstrap compatibility history), YuriNachos (runtime robustness), maintainers of plugin-discord overhaul work

---

### 3) **plugin-discord compatibility issue with ElizaCloud (unresolved)** (Discord report; **no GitHub issue yet**)
- **Current Status:** Reported in Discord (2026-01-18); not yet tracked
- **Impact Assessment:**
  - **User Impact:** Medium → High (blocks new users trying to deploy Discord bots via Cloud)
  - **Functional Impact:** Partial (Cloud workflow blocked; local may still work)
  - **Brand Impact:** High (Cloud onboarding friction)
- **Technical Classification:**
  - **Category:** Bug / UX
  - **Component:** Model Integration / Deployment (ElizaCloud) + Plugin System (Discord)
  - **Complexity:** Moderate effort
- **Resource Requirements:**
  - **Required Expertise:** Cloud deployment pipeline, plugin packaging, environment/secret injection
  - **Dependencies:** Needs a concrete repro project + Cloud logs
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Create a GitHub issue in the appropriate repo (Cloud repo if exists; otherwise elizaos/eliza) with: steps, agent config, plugin versions, Cloud logs.
  2. Validate secrets/env expectations (Discord token, intents, webhooks) match Cloud’s injection model.
  3. Add a “Discord on Cloud” quickstart with a known-good template + automated validation checks.
- **Potential Assignees:** Odilitime (deployment + swarm/cloud direction), Stan ⚡ (docs), Cloud owner(s)

---

### 4) **Telegram plugin crash — TypeError during image processing** (elizaos-plugins/plugin-telegram **#23**)
- **Current Status:** Open
- **Impact Assessment:**
  - **User Impact:** Medium (Telegram bots affected; depends on image feature usage)
  - **Functional Impact:** Partial (crashes/feature unusable when images are involved)
  - **Brand Impact:** Medium (integration stability perception)
- **Technical Classification:**
  - **Category:** Bug
  - **Component:** Plugin System → Telegram Integration (media pipeline)
  - **Complexity:** Moderate effort (input validation + defensive parsing + test fixtures)
- **Resource Requirements:**
  - **Required Expertise:** TypeScript, Telegram Bot API media payloads, runtime message normalization
  - **Dependencies:** Need sample payloads that trigger the TypeError
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Capture failing update payload and add unit test fixture.
  2. Add guards for missing/variant fields (photos array, file_id presence, mime types).
  3. Patch release + changelog entry.
- **Potential Assignees:** Plugin-telegram maintainer, YuriNachos (bugfix throughput), contributor who reported (#23 context)

---

### 5) **SQL error related to zero-vector fallback** (elizaos/eliza **#6380**)
- **Current Status:** Open (reported 2026-01-17)
- **Impact Assessment:**
  - **User Impact:** Medium (affects users hitting embedding edge-cases / fallback path)
  - **Functional Impact:** Partial (memory/search may fail or degrade)
  - **Brand Impact:** Medium (core reliability: “memory doesn’t work”)
- **Technical Classification:**
  - **Category:** Bug
  - **Component:** Core Framework + plugin-sql (embeddings/vector queries)
  - **Complexity:** Moderate effort
- **Resource Requirements:**
  - **Required Expertise:** Postgres/pgvector (or equivalent), plugin-sql internals, embedding pipeline
  - **Dependencies:** Determine which adapter(s) affected (pg/neon/pglite) + schema constraints
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Define expected behavior when embedding generation fails: skip similarity search vs store sentinel vector vs retry.
  2. Implement consistent “no-embedding” handling across adapters and queries (avoid invalid vector operations).
  3. Add integration test that forces fallback path.
- **Potential Assignees:** standujar (plugin-sql + RLS expertise), 0xbbjoker (sql plugin fixes), wtfsayo (stability)

---

### 6) **V2 Python example + inmemorydb changes likely contain runtime-breaking bugs** (elizaos/eliza PR **#6358**)
- **Current Status:** Open PR; automated review flags critical issues (variable mismatch, inconsistent getattr usage, missing dependency)
- **Impact Assessment:**
  - **User Impact:** High (Python quickstart/examples are onboarding-critical; broken examples create immediate churn)
  - **Functional Impact:** Partial (core may be fine, but “getting started” path fails)
  - **Brand Impact:** High (perceived quality: “examples don’t run”)
- **Technical Classification:**
  - **Category:** Bug / Documentation
  - **Component:** Model Integration (Python runtime), Plugin System (inmemorydb), Examples
  - **Complexity:** Moderate effort
- **Resource Requirements:**
  - **Required Expertise:** Python, packaging/requirements, runtime interfaces
  - **Dependencies:** CI job that actually runs examples; dependency locking
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Fix the flagged variable name error in `update_memory()` and align character provider attribute access fully to `getattr`.
  2. Add missing `python-dotenv` requirement (or remove import) and ensure quickstart includes required plugin installation steps.
  3. Add a CI “smoke test” that executes the Python chat example end-to-end.
- **Potential Assignees:** Odilitime (PR author), lalalune (v2.0.0 direction), CI-focused maintainer

---

### 7) **CLI documentation gap — missing upgrade instructions** (Docs site; **no GitHub issue yet**)
- **Current Status:** Acknowledged in core-devs (2026-01-20); CLI reference exists but upgrade path missing
- **Impact Assessment:**
  - **User Impact:** Medium (common operational need; prevents safe updates)
  - **Functional Impact:** Partial (tool works, but upgrade uncertainty causes breakage/support load)
  - **Brand Impact:** Medium (docs completeness)
- **Technical Classification:**
  - **Category:** Documentation
  - **Component:** CLI / Docs
  - **Complexity:** Simple fix
- **Resource Requirements:**
  - **Required Expertise:** CLI release process, package managers (npm/bun), versioning practices
  - **Dependencies:** Confirm canonical upgrade paths for global/local installs
  - **Estimated Effort:** 1/5
- **Recommended Priority:** **P2**
- **Specific Actionable Next Steps:**
  1. Add “Upgrading” section: global install, project-local install, migration notes, breaking-change notes.
  2. Include troubleshooting (cache, bun lockfiles, plugin version pinning).
  3. Link from CLI overview page prominently.
- **Potential Assignees:** Stan ⚡ (docs), Odilitime (CLI context)

---

### 8) **Agents are too chatty/anxious + hallucinations; missing conversational targeting context**
- **Current Status:** Reported in Discord coders (2026-01-20); solution idea proposed (“last 20 messages” context to decide if addressed)
- **Impact Assessment:**
  - **User Impact:** High (applies broadly; impacts real deployments)
  - **Functional Impact:** Partial (doesn’t hard-break, but degrades usefulness and cost)
  - **Brand Impact:** High (agent quality perception)
- **Technical Classification:**
  - **Category:** UX / Performance (cost control) / Bug (mis-targeted replies)
  - **Component:** Core Framework (message routing, shouldRespond heuristics), Memory/context handling
  - **Complexity:** Complex solution (needs careful prompting + heuristics + tests across platforms)
- **Resource Requirements:**
  - **Required Expertise:** Prompting, conversation modeling, runtime message pipeline, evaluation harness
  - **Dependencies:** Determine whether entity tracking already exists; align with Discord/Telegram/X semantics
  - **Estimated Effort:** 4/5
- **Recommended Priority:** **P2** (promote to P1 if this is driving major churn/support)
- **Specific Actionable Next Steps:**
  1. Audit existing `shouldRespond` and mention/reply detection across integrations.
  2. Prototype “context window for targeting” (last N messages + explicit addressing signals) behind a feature flag.
  3. Add measurable metrics: false-response rate, silence rate, token/cost delta.
- **Potential Assignees:** Jin (behavior goals), DorianD (proposal), YuriNachos (runtime behavior), plugin maintainers for platform-specific metadata

---

### 9) **Swarm deployment integration into Eliza Cloud**
- **Current Status:** Running conceptually (Babylon Discord multi-bot single server); planned Cloud integration
- **Impact Assessment:**
  - **User Impact:** Medium (cost + operational benefit for multi-agent operators)
  - **Functional Impact:** No (enhancement)
  - **Brand Impact:** Medium (Cloud competitiveness)
- **Technical Classification:**
  - **Category:** Feature Request / Performance
  - **Component:** Cloud Infrastructure / Deployment Orchestration
  - **Complexity:** Architectural change
- **Resource Requirements:**
  - **Required Expertise:** Infra/orchestration, multi-tenant isolation, resource scheduling, observability
  - **Dependencies:** Cloud architecture decisions; security boundaries for shared runtime
  - **Estimated Effort:** 5/5
- **Recommended Priority:** **P3** (unless Cloud unit economics are currently blocking growth)
- **Specific Actionable Next Steps:**
  1. Write a design doc: tenancy model, isolation guarantees, resource quotas, failure domains.
  2. Define MVP: shared process + separate configs vs shared runtime components.
  3. Pilot with 2–3 internal bots and publish cost/perf numbers.
- **Potential Assignees:** Odilitime (swarm context), Cloud infra lead, security reviewer

---

### 10) **Token utility / tokenomics clarity & roadmap communication gap (Discord-wide; no single GH issue)**
- **Current Status:** Escalating community concern (price decline, “no demand”, roadmap not connecting to token utility)
- **Impact Assessment:**
  - **User Impact:** Critical (affects community, partners, and ecosystem builders’ confidence)
  - **Functional Impact:** No (not a runtime break), but impacts funding/participation
  - **Brand Impact:** High (credibility + narrative quality)
- **Technical Classification:**
  - **Category:** Documentation / UX (ecosystem) / Product Strategy
  - **Component:** Public communications, docs, token migration/support, Jeju positioning
  - **Complexity:** Moderate effort (content + alignment + publication cadence)
- **Resource Requirements:**
  - **Required Expertise:** Technical writing, product narrative, token mechanics literacy, stakeholder comms
  - **Dependencies:** What can be disclosed; confirmation of buyback mechanism and Jeju utility timeline
  - **Estimated Effort:** 3/5
- **Recommended Priority:** **P1** (brand/ecosystem critical even if not “code P0”)
- **Specific Actionable Next Steps:**
  1. Publish a concise token utility explainer: **Framework → Cloud → Jeju** with near-term utility checkpoints.
  2. Stand up `research.elizaos.ai` with weekly technical posts (short, non-sensitive, shippable updates).
  3. Produce “Jeju whitepaper-lite”: what exists now, what’s speculative, milestones + dates/quarters.
  4. Convert key Shaw interviews into written briefs; add a single canonical “Why hold/use ELIZAOS” page.
- **Potential Assignees:** DorianD (proposal), Odilitime (roadmap articulation), Dr. Neuro (visual roadmap), Stan ⚡ (docs publishing), gby/Broccolex (partner feedback loop)

---

## Top Priority Summary (focus for immediate action)
1. **P0 — #6369 Migration eligibility mismatch (Tangem)**
2. **P0 — plugin-discord #43 undefined `sendMessage`**
3. **P1 — Cloud ↔ Discord plugin compatibility (needs GitHub tracking + repro)**
4. **P1 — eliza #6380 SQL zero-vector fallback error**
5. **P1 — eliza PR #6358 Python quickstart/example breakages**
6. **P1 — Token utility/tokenomics/roadmap communication gap (publishables + cadence)**
7. **P1 — plugin-telegram #23 image processing TypeError** (if Telegram is a strategic channel; otherwise keep as P2)

---

## Patterns / Themes Suggesting Deeper Issues
- **Version/interface drift across core ↔ plugins ↔ Cloud**: recurring compatibility failures (Discord) suggest missing contract tests and an incomplete compatibility matrix.
- **Onboarding fragility**: broken examples/quickstarts (Python) and missing upgrade docs indicate the “first 30 minutes” experience isn’t protected by CI.
- **Edge-case hardening in data/embeddings**: SQL/vector fallback issues and prior embedding-dimension mismatch fix indicate the embedding pipeline needs stricter invariants and clearer fallback semantics.
- **Non-technical trust gap**: migration + token narrative gaps are compounding brand risk; technical progress isn’t translating into understandable user value.

---

## Process Improvement Recommendations
1. **Add “Integration Contract CI”**: nightly matrix tests covering (core × plugin-discord × plugin-telegram × Cloud deploy template) with a minimal send/receive scenario.
2. **Protect onboarding with smoke tests**: CI should run official examples (TS + Python) and fail the build if they don’t execute successfully.
3. **Publish and maintain a compatibility matrix**: pinned versions for core/plugins/Cloud templates, with automated checks during release.
4. **Introduce a migration support runbook + audited override path**: reduce ad-hoc handling and shorten time-to-resolution for snapshot disputes.
5. **Adopt a weekly “shipping + narrative” cadence**: a lightweight research/blog update tied to concrete merged PRs and milestones to reduce rumor-driven comms churn.