# Issue Triage - 2025-09-16

## P0: Critical Issues (Fix Immediately)

### Issue #5976: Clean Core Build Proof
- **Current Status:** OPEN (no comments since creation)
- **Impact Assessment:**
  - User Impact: High (affects all users of the core package)
  - Functional Impact: Partial (likely impacts build process)
  - Brand Impact: Medium (affects perceived quality)
- **Technical Classification:**
  - Issue Category: Build/Deployment
  - Component Affected: Core Framework
  - Complexity: Moderate effort
- **Resource Requirements:**
  - Required Expertise: Build systems, TypeScript
  - Dependencies: None identified
  - Estimated Effort: 3
- **Recommended Priority:** P0
- **Next Steps:** 
  1. Investigate the clean build process for the core package
  2. Identify and resolve any build failures
  3. Add automated tests to prevent regression
- **Potential Assignees:** ChristopherTrimboli, wtfsayo

### Excessive PostgreSQL Database Requests from Farcaster Plugin
- **Current Status:** Known issue (mentioned in Discord)
- **Impact Assessment:**
  - User Impact: High (affects performance for all Farcaster plugin users)
  - Functional Impact: Partial (plugin functions but with resource issues)
  - Brand Impact: High (performance issues reflect poorly on product)
- **Technical Classification:**
  - Issue Category: Performance
  - Component Affected: Plugin System (Farcaster)
  - Complexity: Moderate effort
- **Resource Requirements:**
  - Required Expertise: Database optimization, Farcaster API
  - Dependencies: None identified
  - Estimated Effort: 3
- **Recommended Priority:** P0
- **Next Steps:** 
  1. Profile the Farcaster plugin to identify the source of excessive requests
  2. Implement caching or batching of requests
  3. Add rate limiting to prevent database overload
- **Potential Assignees:** Stan ⚡, anyadachan

## P1: High-Impact Issues (Fix this sprint)

### Browser Compatibility for Plugins
- **Current Status:** In progress (CJFT working on it)
- **Impact Assessment:**
  - User Impact: High (affects all browser-based deployments)
  - Functional Impact: Partial (some plugins work, others don't)
  - Brand Impact: High (core feature not fully working)
- **Technical Classification:**
  - Issue Category: Feature
  - Component Affected: Plugin System
  - Complexity: Complex solution
- **Resource Requirements:**
  - Required Expertise: Browser APIs, bundling, TypeScript
  - Dependencies: PGLite compatibility
  - Estimated Effort: 4
- **Recommended Priority:** P1
- **Next Steps:** 
  1. Complete migrator browser tweaks
  2. Make plugin-openai browser compatible with remote URL endpoint
  3. Document browser/node import options
- **Potential Assignees:** CJFT

### CLI Hot Reloading for Plugin Directory Changes
- **Current Status:** Reported in Discord
- **Impact Assessment:**
  - User Impact: Medium (affects developers)
  - Functional Impact: Partial (requires manual restart)
  - Brand Impact: Medium (impacts developer experience)
- **Technical Classification:**
  - Issue Category: Bug
  - Component Affected: CLI
  - Complexity: Moderate effort
- **Resource Requirements:**
  - Required Expertise: File watching, CLI development
  - Dependencies: None identified
  - Estimated Effort: 2
- **Recommended Priority:** P1
- **Next Steps:** 
  1. Identify why plugin directory changes aren't triggering hot reload
  2. Implement improved file watching for plugin directories
  3. Test with various plugin update scenarios
- **Potential Assignees:** sayonara, ChristopherTrimboli

### Type Issues in Client Package
- **Current Status:** Reported in Discord
- **Impact Assessment:**
  - User Impact: Medium (affects developers)
  - Functional Impact: Partial (types are exported but not correctly)
  - Brand Impact: Medium (developer experience issue)
- **Technical Classification:**
  - Issue Category: Bug
  - Component Affected: Client
  - Complexity: Simple fix
- **Resource Requirements:**
  - Required Expertise: TypeScript, barrel exports
  - Dependencies: None identified
  - Estimated Effort: 1
- **Recommended Priority:** P1
- **Next Steps:** 
  1. Fix index barrel exports to properly include all types
  2. Add tests to verify type exports
- **Potential Assignees:** sayonara

## P2: Medium-Impact Issues (Plan for near term)

### Discord Bot DM Permissions
- **Current Status:** Discussed in Discord
- **Impact Assessment:**
  - User Impact: Medium (affects Discord bot users)
  - Functional Impact: No (feature works but needs configuration)
  - Brand Impact: Medium (security/privacy concern)
- **Technical Classification:**
  - Issue Category: Documentation, UX
  - Component Affected: Discord Plugin
  - Complexity: Simple fix
- **Resource Requirements:**
  - Required Expertise: Discord API, permissions
  - Dependencies: None identified
  - Estimated Effort: 2
- **Recommended Priority:** P2
- **Next Steps:** 
  1. Update Discord plugin documentation to clearly explain permission settings
  2. Add configuration option to disable DMs by default
  3. Implement channel whitelisting via CHANNEL_IDS
- **Potential Assignees:** StealtℏyNinja.ADSC, 0xbbjoker

### Anthropic Plugin Model Configuration
- **Current Status:** Discussed in Discord
- **Impact Assessment:**
  - User Impact: Medium (affects Anthropic plugin users)
  - Functional Impact: No (works with configuration)
  - Brand Impact: Medium (usability issue)
- **Technical Classification:**
  - Issue Category: Documentation, UX
  - Component Affected: Anthropic Plugin
  - Complexity: Simple fix
- **Resource Requirements:**
  - Required Expertise: Anthropic API, environment variables
  - Dependencies: None identified
  - Estimated Effort: 1
- **Recommended Priority:** P2
- **Next Steps:** 
  1. Update documentation to clearly explain model configuration options
  2. Add example .env configurations for different Anthropic models
  3. Consider adding UI for model selection
- **Potential Assignees:** 0xbbjoker

### CommonJS Bundle for Better Compatibility
- **Current Status:** Requested in Discord
- **Impact Assessment:**
  - User Impact: Medium (affects users with CommonJS-only environments)
  - Functional Impact: Partial (ESM works but CommonJS doesn't)
  - Brand Impact: Low (affects small subset of users)
- **Technical Classification:**
  - Issue Category: Feature
  - Component Affected: Core Framework
  - Complexity: Moderate effort
- **Resource Requirements:**
  - Required Expertise: Build systems, module formats
  - Dependencies: None identified
  - Estimated Effort: 2
- **Recommended Priority:** P2
- **Next Steps:** 
  1. Configure build system to output both ESM and CommonJS formats
  2. Test in CommonJS environments
  3. Update documentation to explain module format options
- **Potential Assignees:** CJFT

## P3: Low-Impact Issues (Address when resources allow)

### AI16Z Token and ElizaOS Relationship Documentation
- **Current Status:** Questions in Discord
- **Impact Assessment:**
  - User Impact: Low (clarification only)
  - Functional Impact: No (doesn't affect functionality)
  - Brand Impact: Medium (affects perception)
- **Technical Classification:**
  - Issue Category: Documentation
  - Component Affected: Documentation
  - Complexity: Simple fix
- **Resource Requirements:**
  - Required Expertise: Project context, documentation
  - Dependencies: None identified
  - Estimated Effort: 1
- **Recommended Priority:** P3
- **Next Steps:** 
  1. Create clear documentation on the relationship (or lack thereof) between AI16Z token and ElizaOS
  2. Add to FAQ section
- **Potential Assignees:** Documentation team

### Accessible Setup Information
- **Current Status:** Mentioned in Discord
- **Impact Assessment:**
  - User Impact: Low (affects new users only)
  - Functional Impact: No (doesn't affect functionality)
  - Brand Impact: Medium (affects onboarding experience)
- **Technical Classification:**
  - Issue Category: Documentation
  - Component Affected: Documentation
  - Complexity: Simple fix
- **Resource Requirements:**
  - Required Expertise: Documentation, onboarding flows
  - Dependencies: None identified
  - Estimated Effort: 2
- **Recommended Priority:** P3
- **Next Steps:** 
  1. Create more accessible setup guide for new users
  2. Add visual aids and troubleshooting tips
- **Potential Assignees:** DorianD

## Summary of Highest Priority Issues

1. **Clean Core Build Proof (#5976)** - Critical build system issue that needs immediate attention to ensure core package integrity.

2. **Excessive PostgreSQL Database Requests** - Performance issue in Farcaster plugin causing potential resource exhaustion and database strain.

3. **Browser Compatibility for Plugins** - High-priority feature enhancement to ensure plugins work reliably in browser environments.

4. **CLI Hot Reloading** - Developer experience issue impacting workflow efficiency during plugin development.

5. **Type Issues in Client Package** - Developer experience issue affecting proper TypeScript type usage.

## Patterns and Architectural Issues

1. **Browser/Node Compatibility Layer** - Multiple issues relate to ensuring components work in both browser and Node environments. This suggests the need for a more robust architecture for handling environment differences.

2. **Plugin Configuration Complexity** - Issues with Anthropic and Discord plugins indicate a need for more standardized, user-friendly configuration approaches across plugins.

3. **Developer Experience Gaps** - Hot reloading, type export issues, and documentation questions point to areas where the developer experience could be improved.

4. **Build System Fragility** - Clean build issues and compatibility concerns suggest the build system might need a more comprehensive approach.

## Process Improvement Recommendations

1. **Standardized Plugin Configuration** - Develop a consistent pattern for plugin configuration with clear documentation templates.

2. **Automated Browser Compatibility Testing** - Implement automated tests that verify each plugin functions correctly in both Node and browser environments.

3. **Developer Experience Working Group** - Establish a team focused specifically on improving the developer experience, including documentation, tooling, and workflow.

4. **Performance Monitoring** - Add standardized performance monitoring to plugins to detect issues like the Farcaster database problem before they impact users.

5. **Documentation-as-Code** - Treat documentation as a first-class citizen in the development process, with reviews and automated checks for completeness.