# elizaOS Issue Triage - 2025-07-17

## Impact Assessment

### P0 - Critical Issues (Fix Immediately)

1. **Unable to create dir on windows** (Issue #5603)
   - **Impact Assessment**:
     - User Impact: Critical (Blocks installation on Windows)
     - Functional Impact: Yes (Prevents project creation)
     - Brand Impact: High (Poor Windows support damages perception)
   - **Technical Classification**:
     - Issue Category: Bug
     - Component Affected: CLI
     - Complexity: Simple fix
   - **Resource Allocation**:
     - Required Expertise: Node.js file system handling, Windows paths
     - Dependencies: None
     - Estimated Effort: 1
   - **Next Steps**: Fix path normalization in CLI project creation for Windows
   - **Potential Assignees**: @wtfsayo, @SYMBaiEX

2. **Make API key setup optional in npx elizaos create** (Issue #5604)
   - **Impact Assessment**:
     - User Impact: High (Blocks onboarding for new users)
     - Functional Impact: Yes (Prevents project creation without API keys)
     - Brand Impact: High (Poor first user experience)
   - **Technical Classification**:
     - Issue Category: UX
     - Component Affected: CLI Setup Flow
     - Complexity: Moderate effort
   - **Resource Allocation**:
     - Required Expertise: CLI workflow, ElizaOS configuration
     - Dependencies: None
     - Estimated Effort: 2
   - **Next Steps**: Modify CLI setup flow to make API keys optional with appropriate warnings
   - **Potential Assignees**: @yungalgo, @wtfsayo

### P1 - High Priority Issues (Fix this sprint)

3. **Unable to create project without using keys** (Issue #5605)
   - **Impact Assessment**:
     - User Impact: High (Blocks new user onboarding)
     - Functional Impact: Partial (Can't create project without keys)
     - Brand Impact: Medium
   - **Technical Classification**:
     - Issue Category: UX
     - Component Affected: CLI Create Command
     - Complexity: Simple fix
   - **Resource Allocation**:
     - Required Expertise: CLI workflow design
     - Dependencies: Likely related to Issue #5604
     - Estimated Effort: 2
   - **Next Steps**: Refactor create command to have a "skip keys" option
   - **Potential Assignees**: @wtfsayo, @yungalgo

4. **.eliza directory getting hoisted** (Issue #5606)
   - **Impact Assessment**:
     - User Impact: High (Causes unexpected behavior)
     - Functional Impact: Partial (Projects not isolated correctly)
     - Brand Impact: Medium
   - **Technical Classification**:
     - Issue Category: Bug
     - Component Affected: CLI Project Structure
     - Complexity: Moderate effort
   - **Resource Allocation**:
     - Required Expertise: Node.js path resolution, project structure
     - Dependencies: None
     - Estimated Effort: 2
   - **Next Steps**: Fix directory resolution logic to avoid hoisting
   - **Potential Assignees**: @wtfsayo, @ChristopherTrimboli

5. **Custom plugin schema migration issues** (Discord report)
   - **Impact Assessment**:
     - User Impact: High (Affects plugin developers)
     - Functional Impact: Partial (Custom plugins fail to migrate)
     - Brand Impact: Medium
   - **Technical Classification**:
     - Issue Category: Bug
     - Component Affected: Plugin System, Database Migrations
     - Complexity: Complex solution
   - **Resource Allocation**:
     - Required Expertise: Drizzle ORM, PostgreSQL, plugin architecture
     - Dependencies: DatabaseMigrationService
     - Estimated Effort: 3
   - **Next Steps**: Create GitHub issue with detailed logs, implement fix for schema handling
   - **Potential Assignees**: @wtfsayo, @0xbbjoker

### P2 - Medium Priority Issues (Plan for near term)

6. **Advisory locking for DatabaseMigrationService** (PR #5569)
   - **Impact Assessment**:
     - User Impact: Medium (Affects concurrent migrations)
     - Functional Impact: Partial (Race conditions possible)
     - Brand Impact: Low
   - **Technical Classification**:
     - Issue Category: Performance, Reliability
     - Component Affected: Database Migration System
     - Complexity: Moderate effort
   - **Resource Allocation**:
     - Required Expertise: Database locking mechanisms, Drizzle ORM
     - Dependencies: None
     - Estimated Effort: 3
   - **Next Steps**: Review and merge PR #5569
   - **Potential Assignees**: @wtfsayo, @tcm390

7. **PGLite directory setup issues in WSL** (Discord report)
   - **Impact Assessment**:
     - User Impact: Medium (WSL users affected)
     - Functional Impact: Partial (EPERM errors with PGLite)
     - Brand Impact: Low
   - **Technical Classification**:
     - Issue Category: Bug
     - Component Affected: Database Setup
     - Complexity: Simple fix
   - **Resource Allocation**:
     - Required Expertise: WSL compatibility, file permissions
     - Dependencies: None
     - Estimated Effort: 2
   - **Next Steps**: Create fallback mechanism for WSL permission issues
   - **Potential Assignees**: @sayonara, @wookosh

8. **Provider reliability for context injection** (Discord report)
   - **Impact Assessment**:
     - User Impact: Medium (Affects AI response quality)
     - Functional Impact: Partial
     - Brand Impact: Medium
   - **Technical Classification**:
     - Issue Category: Bug
     - Component Affected: Provider System
     - Complexity: Moderate effort
   - **Resource Allocation**:
     - Required Expertise: Provider framework, context management
     - Dependencies: None
     - Estimated Effort: 3
   - **Next Steps**: Improve provider callback reliability
   - **Potential Assignees**: @0xbbjoker, @tcm390

### P3 - Low Priority Issues (Address when resources allow)

9. **Website jargon and onboarding clarity** (Discord feedback)
   - **Impact Assessment**:
     - User Impact: Low (Affects new user understanding)
     - Functional Impact: No
     - Brand Impact: Medium
   - **Technical Classification**:
     - Issue Category: Documentation, UX
     - Component Affected: Website
     - Complexity: Moderate effort
   - **Resource Allocation**:
     - Required Expertise: UX writing, documentation
     - Dependencies: None
     - Estimated Effort: 2
   - **Next Steps**: Update website with clearer onboarding paths
   - **Potential Assignees**: @3on_, @SYMBaiEX

10. **Support passing images to Anthropic models** (Discord request)
    - **Impact Assessment**:
      - User Impact: Low (Feature request)
      - Functional Impact: No
      - Brand Impact: Low
    - **Technical Classification**:
      - Issue Category: Feature Request
      - Component Affected: Model Integration
      - Complexity: Moderate effort
    - **Resource Allocation**:
      - Required Expertise: Anthropic API, model integration
      - Dependencies: None
      - Estimated Effort: 3
    - **Next Steps**: Implement image support for Anthropic via useModel
    - **Potential Assignees**: @Charlie, @tcm390

## Summary of Top Critical Issues

1. **Unable to create dir on Windows** (Issue #5603) - P0
   - Blocks project creation on Windows, requires immediate path normalization fix

2. **Make API key setup optional in npx elizaos create** (Issue #5604) - P0
   - Preventing new users from starting projects without API keys, poor UX

3. **Unable to create project without using keys** (Issue #5605) - P1
   - Related to #5604, blocks new user onboarding

4. **.eliza directory getting hoisted** (Issue #5606) - P1
   - Causes unexpected behavior with project isolation

5. **Custom plugin schema migration issues** (Discord) - P1
   - Affecting plugin developers with database migration failures

6. **Advisory locking for DatabaseMigrationService** (PR #5569) - P2
   - Improves reliability for concurrent migrations

7. **PGLite directory setup issues in WSL** (Discord) - P2
   - Affects WSL users with EPERM errors

## Recurring Patterns and Deeper Issues

1. **Windows/Cross-Platform Compatibility**
   - Multiple issues related to Windows path handling and WSL compatibility
   - Insufficient testing on Windows platforms before releases
   - Solution: Implement mandatory Windows testing in CI pipeline

2. **CLI Usability and Onboarding**
   - Multiple issues with API key requirements blocking new users
   - Overly strict configuration requirements creating friction
   - Solution: Create an "easy mode" installation profile with minimal requirements

3. **Plugin System Complexity**
   - Database migration issues and schema handling complexity
   - Provider reliability problems indicate architectural concerns
   - Solution: Consider refactoring plugin system for simpler integration patterns

## Process Improvement Recommendations

1. **Platform-Specific Testing**
   - Implement automated testing on Windows, macOS, and Linux for all CLI commands
   - Create Docker containers for WSL testing scenarios
   - Add Windows-specific issue templates to capture environment details

2. **User Experience Testing**
   - Create first-time user sessions to identify onboarding friction points
   - Implement "time to first success" as a key metric for CLI and GUI users
   - Document common pitfalls and solutions in a troubleshooting guide

3. **Plugin Development Documentation**
   - Create comprehensive tutorial for plugin developers with database schema examples
   - Provide better schema validation and error reporting for plugin migrations
   - Implement a plugin test framework that verifies database compatibility