# elizaOS Issue Triage - 2025-06-06

## Issue #1: Plugin Callback Replacement by ATTACHMENTS Provider

**Issue Title & ID**: Custom Plugin - callback from action is getting replaced by `ATTACHMENTS` provider (#4947)

**Current Status**: Open

**Impact Assessment**:
- User Impact: High - Custom plugin developers cannot receive action callbacks
- Functional Impact: Partial - Core functionality works but custom actions are limited
- Brand Impact: Medium - Affects developer experience and plugin ecosystem

**Technical Classification**:
- Issue Category: Bug
- Component Affected: Plugin System
- Complexity: Moderate effort

**Resource Allocation Factors**:
- Required Expertise: Plugin architecture, action handling system
- Dependencies: Bootstrap plugin functionality
- Estimated Effort: 3

**Recommended Priority**: P1

**Next Steps**: 
1. Investigate the callback handling mechanism in the bootstrap plugin
2. Fix the action handler to preserve custom callbacks from plugin actions
3. Add regression tests to verify callback preservation

**Potential Assignees**: 0xbbjoker, wtfsayo

## Issue #2: Room Creation API Returns Empty Rooms Array

**Issue Title & ID**: Creating room via REST API first works but then returns empty rooms array (#4955)

**Current Status**: Open

**Impact Assessment**:
- User Impact: Medium - Affects programmatic agent integration
- Functional Impact: Partial - Initial creation works but subsequent actions fail
- Brand Impact: Medium - Damages reliability perception for API-driven workflows

**Technical Classification**:
- Issue Category: Bug
- Component Affected: API
- Complexity: Moderate effort

**Resource Allocation Factors**:
- Required Expertise: API design, database interactions
- Dependencies: Message server refactoring (#4864)
- Estimated Effort: 2

**Recommended Priority**: P1

**Next Steps**:
1. Reproduce the issue with a minimal test case
2. Analyze API route handling for room creation endpoint
3. Investigate database query issues for rooms retrieval
4. Implement fix to ensure consistent room visibility

**Potential Assignees**: lalalune, geooner

## Issue #3: Agent Not Responding to Twitter Mentions

**Issue Title & ID**: Successive replies on target users (#4940)

**Current Status**: Open

**Impact Assessment**:
- User Impact: High - Social media agents not functioning as expected
- Functional Impact: Yes - Blocks core Twitter integration functionality
- Brand Impact: High - Public-facing agents failing to respond damages reputation

**Technical Classification**:
- Issue Category: Bug
- Component Affected: Twitter Plugin
- Complexity: Moderate effort

**Resource Allocation Factors**:
- Required Expertise: Twitter API integration, plugin architecture
- Dependencies: Twitter plugin update (v1.0.3)
- Estimated Effort: 3

**Recommended Priority**: P1

**Next Steps**:
1. Review recent Twitter plugin changes (v1.0.3)
2. Test response patterns with different target user configurations
3. Fix the detection logic for mentions
4. Add monitoring for Twitter reply failures

**Potential Assignees**: standujar, wtfsayo

## Issue #4: Agent ID and Room ID Required Error

**Issue Title & ID**: agentId and roomId are required (#4933)

**Current Status**: Open

**Impact Assessment**:
- User Impact: High - Prevents agent startup for many users
- Functional Impact: Yes - Blocks core functionality
- Brand Impact: High - Basic usage failures damage perception

**Technical Classification**:
- Issue Category: Bug
- Component Affected: Core Framework
- Complexity: Moderate effort

**Resource Allocation Factors**:
- Required Expertise: Core runtime, socket handling
- Dependencies: Bootstrap plugin, message server refactoring
- Estimated Effort: 3

**Recommended Priority**: P0

**Next Steps**:
1. Review recent changes to socket initialization
2. Fix default room creation during agent startup
3. Implement better error handling for missing configuration
4. Add comprehensive tests for agent initialization paths

**Potential Assignees**: lalalune, standujar

## Issue #5: Web Client Shows Incorrect Version

**Issue Title & ID**: Web client thinks it is on a different version (#4924)

**Current Status**: Open

**Impact Assessment**:
- User Impact: Medium - Causes confusion about updates
- Functional Impact: No - Cosmetic issue only
- Brand Impact: Medium - Appears unprofessional

**Technical Classification**:
- Issue Category: Bug
- Component Affected: GUI
- Complexity: Simple fix

**Resource Allocation Factors**:
- Required Expertise: Client versioning, frontend development
- Dependencies: Release versioning in client (#4952)
- Estimated Effort: 1

**Recommended Priority**: P2

**Next Steps**:
1. Review version synchronization between packages
2. Fix client-side version detection to properly read from server
3. Ensure version is consistently updated across components during releases

**Potential Assignees**: wtfsayo, ChristopherTrimboli

## Issue #6: Agent Cross Interference Loop

**Issue Title & ID**: Agent cross interference loop (#4935)

**Current Status**: Merged (fix in progress)

**Impact Assessment**:
- User Impact: Critical - Multiple agents responding to each other infinitely
- Functional Impact: Yes - Makes multi-agent setups unusable
- Brand Impact: High - Core stability issue

**Technical Classification**:
- Issue Category: Bug
- Component Affected: Message System
- Complexity: Complex solution

**Resource Allocation Factors**:
- Required Expertise: Message handling, agent coordination
- Dependencies: Message server refactoring
- Estimated Effort: 4

**Recommended Priority**: P0

**Next Steps**:
1. Verify fix in latest builds
2. Document for users the fix release in v1.0.5
3. Add regression tests to prevent future occurrences
4. Monitor for related issues after deployment

**Potential Assignees**: lalalune, standujar

## Issue #7: Bootstrap Plugin Requirements

**Issue Title & ID**: Bootstrap plugin is mandatory for agent functionality (Discord discussion)

**Current Status**: Identified in Discord, needs documentation

**Impact Assessment**:
- User Impact: Medium - Affects all new users
- Functional Impact: Partial - Missing plugin breaks expected functionality
- Brand Impact: Low - Documentation issue

**Technical Classification**:
- Issue Category: Documentation
- Component Affected: Plugin System
- Complexity: Simple fix

**Resource Allocation Factors**:
- Required Expertise: Documentation, plugin system
- Dependencies: None
- Estimated Effort: 1

**Recommended Priority**: P2

**Next Steps**:
1. Update documentation to clarify bootstrap plugin requirement
2. Add warnings in UI when bootstrap plugin is not included
3. Consider making bootstrap automatically included by default in all setups

**Potential Assignees**: wtfsayo, 0xbbjoker

## Issue #8: OpenRouter Embedding Support

**Issue Title & ID**: OpenRouter doesn't support embeddings (Discord discussion)

**Current Status**: Identified in Discord, needs implementation

**Impact Assessment**:
- User Impact: Medium - Affects users trying to use OpenRouter as primary provider
- Functional Impact: Partial - Knowledge features don't work without embeddings
- Brand Impact: Low - Integration limitation

**Technical Classification**:
- Issue Category: Feature Request
- Component Affected: Plugin Integration
- Complexity: Moderate effort

**Resource Allocation Factors**:
- Required Expertise: OpenAI API, OpenRouter integration, embedding models
- Dependencies: Knowledge plugin
- Estimated Effort: 3

**Recommended Priority**: P2

**Next Steps**:
1. Document current limitation clearly for users
2. Implement automatic fallback to OpenAI for embeddings when using OpenRouter
3. Add configuration option to specify separate embedding provider

**Potential Assignees**: 0xbbjoker, standujar

## Issue #9: Knowledge Plugin Environment Variable Configuration

**Issue Title & ID**: Knowledge plugin error "TEXT_PROVIDER is required when CTX_KNOWLEDGE_ENABLED is true" (Discord discussion)

**Current Status**: Identified in Discord, needs fix

**Impact Assessment**:
- User Impact: Medium - Affects users trying to use knowledge features
- Functional Impact: Partial - Knowledge features unavailable
- Brand Impact: Medium - Error messages confuse users

**Technical Classification**:
- Issue Category: Bug
- Component Affected: Knowledge Plugin
- Complexity: Simple fix

**Resource Allocation Factors**:
- Required Expertise: Plugin configuration, environment variables
- Dependencies: None
- Estimated Effort: 2

**Recommended Priority**: P2

**Next Steps**:
1. Add clearer error messages explaining required environment variables
2. Update documentation with complete knowledge setup guide
3. Implement better defaults or guided setup in UI

**Potential Assignees**: DrakeDinh, wtfsayo

## Issue #10: MCP Plugin Documentation

**Issue Title & ID**: Missing MCP plugin documentation on eliza.how website (Discord discussion)

**Current Status**: Identified in Discord, needs documentation

**Impact Assessment**:
- User Impact: Low - Only affects users needing MCP integration
- Functional Impact: No - Documentation issue only
- Brand Impact: Low - Minor documentation gap

**Technical Classification**:
- Issue Category: Documentation
- Component Affected: Documentation
- Complexity: Simple fix

**Resource Allocation Factors**:
- Required Expertise: MCP plugin, documentation
- Dependencies: None
- Estimated Effort: 1

**Recommended Priority**: P3

**Next Steps**:
1. Add MCP plugin documentation to eliza.how website
2. Include code examples for integration
3. Link from main plugin documentation page

**Potential Assignees**: Stan ⚡, shaw

## Summary of Highest Priority Issues

1. **P0: Agent ID and Room ID Required Error (#4933)** - Prevents basic agent startup and affects many users with a confusing error message. This is a fundamental issue blocking core functionality.

2. **P0: Agent Cross Interference Loop (#4935)** - Critical issue causing infinite loops between agents. While a fix has been merged, it needs verification and may require follow-up work.

3. **P1: Plugin Callback Replacement (#4947)** - Impairs plugin development experience by breaking key functionality for custom plugins, limiting the ecosystem growth.

4. **P1: Room Creation API Returns Empty Rooms Array (#4955)** - Causes API-driven integrations to fail, making programmatic use of agents unreliable.

5. **P1: Twitter Mentions Response Issue (#4940)** - Breaks social media agent functionality in a highly visible way, affecting public-facing agents.

6. **P2: Web Client Version Discrepancy (#4924)** - Causes confusion about updates but doesn't block functionality.

7. **P2: Bootstrap Plugin Requirements (Discord)** - Documentation issue that affects new users but has a straightforward fix.

## Identified Patterns and Architectural Concerns

1. **Message System Architectural Issues**: Multiple problems stem from the recent message server refactoring (#4864). The transition to a standalone message system is causing agent communication and coordination issues.

2. **Plugin System Complexity**: Several issues relate to plugin dependencies, configuration, and integration. The plugin system may be too complex for users to configure correctly.

3. **Environment Configuration Challenges**: Many reported problems involve environment variables and configuration settings that users struggle with. The current approach to configuration may be too complex.

4. **Version Synchronization Problems**: Inconsistent versioning across packages leads to confusion. There appears to be no automated mechanism to ensure versions stay synchronized.

5. **Documentation Gaps**: Several issues could be prevented with better documentation, especially around plugin requirements and configuration.

## Process Improvement Recommendations

1. **Implement a Comprehensive Testing Strategy**:
   - Add end-to-end tests for common user workflows
   - Create specific tests for multi-agent interactions
   - Implement regression tests for all fixed bugs

2. **Improve Plugin Management**:
   - Create a plugin dependency visualization tool
   - Implement automated validation of plugin configurations
   - Move toward a more declarative plugin configuration model

3. **Enhance Documentation Process**:
   - Create documentation tickets alongside feature development
   - Implement a documentation review step in the PR process
   - Develop an automated changelog generation system

4. **Strengthen Release Management**:
   - Implement version synchronization across packages
   - Create a more rigorous pre-release testing process
   - Establish a structured beta program for early feedback

5. **Improve Discord Support Process**:
   - Create a systematic way to convert Discord issues into GitHub issues
   - Develop a knowledge base from common Discord questions
   - Implement automated tracking of recurring support themes