# elizaOS Issue Triage - 2025-09-13

## Issue Title: "dont show update available for alpha versions if user is not on alpha dist" (#5971)
- **Current Status**: OPEN
- **Impact Assessment**:
  - User Impact: Medium (Affects users seeing inappropriate update notifications)
  - Functional Impact: Partial (Update system functions but provides incorrect information)
  - Brand Impact: Medium (Creates confusion and appears unpolished)
- **Technical Classification**:
  - Issue Category: UX
  - Component Affected: CLI Update System
  - Complexity: Simple fix
- **Resource Requirements**:
  - Required Expertise: CLI update workflow knowledge
  - Dependencies: None
  - Estimated Effort: 1
- **Recommended Priority**: P2
- **Next Steps**: Modify version comparison logic to check for alpha status before showing update notifications
- **Potential Assignees**: @ChristopherTrimboli (Based on recent work on NPM packages)

## Issue Title: "feat: Adds browser build with PGlite WASM support" (PR #5970)
- **Current Status**: OPEN
- **Impact Assessment**:
  - User Impact: High (Enables new offline functionality)
  - Functional Impact: No (New feature addition)
  - Brand Impact: High (Strategic feature for framework adoption)
- **Technical Classification**:
  - Issue Category: Feature Request
  - Component Affected: Browser Integration
  - Complexity: Moderate effort
- **Resource Requirements**:
  - Required Expertise: Browser WASM, PGlite, elizaOS internals
  - Dependencies: None identified
  - Estimated Effort: 3
- **Recommended Priority**: P1
- **Next Steps**: Complete code review, test in multiple browser environments, ensure proper documentation
- **Potential Assignees**: @cjft (Based on previous browser integration work)

## Issue Title: "feat: Creates elizaos alias package" (PR #5972)
- **Current Status**: OPEN
- **Impact Assessment**:
  - User Impact: Medium (Simplifies developer experience)
  - Functional Impact: No (Enhancement to package management)
  - Brand Impact: Medium (Improves developer perception)
- **Technical Classification**:
  - Issue Category: Feature Request
  - Component Affected: NPM Package Structure
  - Complexity: Simple fix
- **Resource Requirements**:
  - Required Expertise: NPM package management
  - Dependencies: Core package
  - Estimated Effort: 1
- **Recommended Priority**: P2
- **Next Steps**: Complete code review, ensure CI integration, document package structure
- **Potential Assignees**: @shaw (Based on recent NPM package management discussions)

## Issue Title: "NPM token management for elizaos package" (Discord Discussion)
- **Current Status**: In Progress
- **Impact Assessment**:
  - User Impact: Medium (Could affect package availability)
  - Functional Impact: Partial (May impact installation)
  - Brand Impact: Medium (Professional package management)
- **Technical Classification**:
  - Issue Category: Security
  - Component Affected: CI/CD Pipeline
  - Complexity: Simple fix
- **Resource Requirements**:
  - Required Expertise: NPM, GitHub Actions, CI/CD
  - Dependencies: None
  - Estimated Effort: 1
- **Recommended Priority**: P1
- **Next Steps**: Regenerate tokens, add second NPM token in CI, consider transferring elizaos package to organization
- **Potential Assignees**: @cjft, @shaw (Based on their recent discussion)

## Issue Title: "VSCode server in CVM with flox and Claude code integration" (Discord Discussion)
- **Current Status**: In Progress
- **Impact Assessment**:
  - User Impact: High (Improves development experience)
  - Functional Impact: No (Enhancement)
  - Brand Impact: High (Demonstrates project's robustness)
- **Technical Classification**:
  - Issue Category: Feature Request
  - Component Affected: Confidential Computing
  - Complexity: Complex solution
- **Resource Requirements**:
  - Required Expertise: Confidential Virtual Machines, VSCode integration
  - Dependencies: None identified
  - Estimated Effort: 4
- **Recommended Priority**: P2
- **Next Steps**: Complete integration, test in multiple environments, document setup process
- **Potential Assignees**: @Agent Joshua (Based on current work)

## Issue Title: "Research and development of a new knowledge system for Eliza" (Discord Discussion)
- **Current Status**: Research Phase
- **Impact Assessment**:
  - User Impact: High (Core improvement to agent capabilities)
  - Functional Impact: No (New capability)
  - Brand Impact: High (Fundamental to agent intelligence)
- **Technical Classification**:
  - Issue Category: Feature Request
  - Component Affected: Knowledge Plugin
  - Complexity: Complex solution
- **Resource Requirements**:
  - Required Expertise: Knowledge systems, embeddings, LLM integration
  - Dependencies: None
  - Estimated Effort: 5
- **Recommended Priority**: P2
- **Next Steps**: Gather interesting data and questions from partners, research embedding methods, prototype knowledge storage approaches
- **Potential Assignees**: @avirtualfuture (Based on Discord mention)

## Issue Title: "Browser integration with browser DB" (Discord Discussion)
- **Current Status**: Near Completion
- **Impact Assessment**:
  - User Impact: High (Enables offline capabilities)
  - Functional Impact: No (New capability)
  - Brand Impact: High (Strategic feature)
- **Technical Classification**:
  - Issue Category: Feature Request
  - Component Affected: Browser Integration
  - Complexity: Complex solution
- **Resource Requirements**:
  - Required Expertise: Browser storage, WASM, elizaOS internals
  - Dependencies: PGlite WASM implementation
  - Estimated Effort: 4
- **Recommended Priority**: P1
- **Next Steps**: Complete integration, test in multiple browsers, ensure compatibility with existing systems
- **Potential Assignees**: @cjft (Based on Discord mention)

## Issue Title: "Merging AgentManager into AgentServer" (Discord Discussion)
- **Current Status**: In Progress
- **Impact Assessment**:
  - User Impact: Low (Internal refactoring)
  - Functional Impact: No (Architecture improvement)
  - Brand Impact: Low (Invisible to users)
- **Technical Classification**:
  - Issue Category: Performance
  - Component Affected: Core Framework
  - Complexity: Moderate effort
- **Resource Requirements**:
  - Required Expertise: elizaOS architecture, TypeScript
  - Dependencies: None
  - Estimated Effort: 3
- **Recommended Priority**: P3
- **Next Steps**: Complete PR #5864, fix/add missing unit tests
- **Potential Assignees**: @Stan (Based on Discord discussion)

## Issue Title: "Add Stan to the GitHub organization" (Discord Discussion)
- **Current Status**: Pending
- **Impact Assessment**:
  - User Impact: Low (Internal operations)
  - Functional Impact: No (Administrative)
  - Brand Impact: Low (Internal operations)
- **Technical Classification**:
  - Issue Category: Documentation
  - Component Affected: Project Administration
  - Complexity: Simple fix
- **Resource Requirements**:
  - Required Expertise: GitHub organization administration
  - Dependencies: Owner privileges
  - Estimated Effort: 1
- **Recommended Priority**: P3
- **Next Steps**: Find GitHub organization owner to add Stan
- **Potential Assignees**: Any GitHub organization owner

## Issue Title: "Using local Ollama embeddings with knowledge plugin" (Discord Discussion)
- **Current Status**: Resolved
- **Impact Assessment**:
  - User Impact: Medium (Enables offline knowledge plugin)
  - Functional Impact: No (Alternative implementation)
  - Brand Impact: Medium (Flexibility for users)
- **Technical Classification**:
  - Issue Category: Documentation
  - Component Affected: Knowledge Plugin
  - Complexity: Simple fix
- **Resource Requirements**:
  - Required Expertise: Embeddings, Ollama integration
  - Dependencies: None
  - Estimated Effort: 1
- **Recommended Priority**: P4
- **Next Steps**: Document this capability more clearly in the knowledge plugin README
- **Potential Assignees**: @0xbbjoker (Based on knowledge demonstrated in Discord)

## Summary of Highest Priority Issues

1. **PR #5970: Browser build with PGlite WASM support (P1)**
   - This feature enables offline capabilities and browser-based storage, which is strategically important for the framework.

2. **NPM token management for elizaos package (P1)**
   - Security-related issue affecting package distribution that needs immediate attention.

3. **Browser integration with browser DB (P1)**
   - Near completion and represents a significant capability enhancement for offline usage.

4. **PR #5971: Update notification for alpha versions (P2)**
   - UX issue affecting user experience with the update system.

5. **PR #5972: elizaos alias package (P2)**
   - Developer experience improvement for package management.

6. **VSCode server in CVM with flox integration (P2)**
   - Significant developer experience enhancement for confidential computing.

7. **Research for new knowledge system (P2)**
   - Core capability enhancement that will improve agent intelligence.

## Patterns and Architectural Issues

1. **Package Management Complexity**: Multiple issues (token management, alias package, organization transfers) indicate a need for streamlined package management strategy.

2. **Duplication in Core Architecture**: The discussion about merging AgentManager and AgentServer reflects a pattern of redundant abstractions that should be addressed systematically.

3. **Browser/Server Model Separation**: Several issues relate to browser capabilities, suggesting the need for a clearer architecture separating browser and server concerns.

4. **Documentation Gaps**: Several discussions in Discord reveal features that work but aren't well documented, such as local Ollama embeddings with the knowledge plugin.

## Process Improvement Recommendations

1. **Implement Formalized Feature Planning**: Create a structured feature proposal process similar to Ethereum's EIPs as mentioned in the September 10th Discord logs.

2. **Consolidate Release Infrastructure**: The multiple discussions about NPM packages suggest a need for unified release engineering practices.

3. **Documentation Automation**: Implement systems to automatically extract capabilities mentioned in discussions and add them to documentation.

4. **Enhanced Testing Strategy**: Several bugs indicate a need for more comprehensive testing, particularly around browser compatibility and alpha releases.

5. **Clearer Ownership Model**: Discussions about GitHub organization access suggest a need for clearer roles and responsibilities in the project's governance.