# elizaOS Issue Triage - 2025-10-14

## Issue #6061: [DOCS] Every plugin link in docs leads to a 404

**Current Status:** OPEN (reported 2025-10-13)

**Impact Assessment:**
- User Impact: High (All users accessing documentation affected)
- Functional Impact: Partial (Core functionality works, but documentation is broken)
- Brand Impact: High (Makes project appear unpolished/unmaintained)

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

**Resource Allocation Factors:**
- Required Expertise: Documentation structure, web routing
- Dependencies: None
- Estimated Effort: 1

**Recommended Priority:** P1

**Next Steps:**
1. Verify all affected links in documentation
2. Determine if links should point to `/plugins/` or `/plugin-registry/`
3. Update link patterns in documentation source
4. Validate fix on staging environment before deploying

**Potential Assignees:** douglasg14b (reporter), letmehateu (previous doc fixes)

## PR #6062: feat(core): implement generateText() API

**Current Status:** OPEN (created 2025-10-13)

**Impact Assessment:**
- User Impact: Medium (New API enhances capabilities)
- Functional Impact: No (Adding new functionality)
- Brand Impact: Medium (Improves developer experience)

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

**Resource Allocation Factors:**
- Required Expertise: Core API design, TypeScript
- Dependencies: Core framework
- Estimated Effort: 3

**Recommended Priority:** P2

**Next Steps:**
1. Review code changes for API design consistency
2. Ensure documentation covers the new API
3. Add tests for the new functionality
4. Verify integration with existing components

**Potential Assignees:** tylermcwilliams (PR author), 0xbbjoker (core contributor)

## ElizaOS Token Migration

**Current Status:** PLANNED (scheduled for 2025-10-21)

**Impact Assessment:**
- User Impact: Critical (Affects all token holders)
- Functional Impact: No (External to core functionality)
- Brand Impact: High (Financial aspect of project)

**Technical Classification:**
- Issue Category: Feature Request
- Component Affected: Blockchain/Token System
- Complexity: Complex solution

**Resource Allocation Factors:**
- Required Expertise: Blockchain, smart contracts, token migration
- Dependencies: External blockchain platforms
- Estimated Effort: 5

**Recommended Priority:** P1

**Next Steps:**
1. Finalize migration documentation
2. Communicate timeline and process to community
3. Prepare technical infrastructure for token swap
4. Test migration process with sample accounts
5. Create support process for migration issues

**Potential Assignees:** Dean, Odilitime (mentioned in Discord)

## Plugin Naming Convention - elizacloud vs services

**Current Status:** RESOLVED (decided on "plugin-elizacloud")

**Impact Assessment:**
- User Impact: Low (Internal naming convention)
- Functional Impact: No (Naming only)
- Brand Impact: Low (Internal consistency)

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

**Resource Allocation Factors:**
- Required Expertise: Plugin architecture
- Dependencies: None
- Estimated Effort: 1

**Recommended Priority:** P3 (already resolved, just need to ensure consistent implementation)

**Next Steps:**
1. Update all references to use the agreed naming convention
2. Update documentation to reflect naming decision
3. Verify no legacy references remain

**Potential Assignees:** sayonara, Odilitime (mentioned in Discord)

## Tool Router Implementation

**Current Status:** IN PROGRESS

**Impact Assessment:**
- User Impact: Medium (Improves agent capabilities)
- Functional Impact: Partial (Enhances core functionality)
- Brand Impact: Medium (Technical capability improvement)

**Technical Classification:**
- Issue Category: Feature Request
- Component Affected: MCP-gateway/core
- Complexity: Moderate effort

**Resource Allocation Factors:**
- Required Expertise: Tool routing, Composio integration
- Dependencies: plugin-composio
- Estimated Effort: 4

**Recommended Priority:** P2

**Next Steps:**
1. Complete implementation in plugin-composio
2. Test integration with ElizaOS core wrapper
3. Document the feature for developers
4. Add example usage in templates

**Potential Assignees:** Stan (mentioned in Discord)

## Voice/Avatar Integration Possibilities

**Current Status:** PROPOSED

**Impact Assessment:**
- User Impact: Medium (Enhances user interaction capabilities)
- Functional Impact: No (New feature)
- Brand Impact: High (Visual appeal and modernization)

**Technical Classification:**
- Issue Category: Feature Request
- Component Affected: Plugin System, GUI
- Complexity: Complex solution

**Resource Allocation Factors:**
- Required Expertise: Voice generation, avatar systems, frontend integration
- Dependencies: External APIs (vapi.ai, xpressioncamera.com)
- Estimated Effort: 5

**Recommended Priority:** P3

**Next Steps:**
1. Create research document on integration possibilities
2. Evaluate existing plugins with similar functionality
3. Develop proof-of-concept for voice/avatar integration
4. Assess performance and cost implications

**Potential Assignees:** DorianD (proposed feature in Discord)

## GitHub Detection Issue

**Current Status:** REPORTED

**Impact Assessment:**
- User Impact: Medium (Affects GitHub integration users)
- Functional Impact: Partial (GitHub functionality impaired)
- Brand Impact: Medium (Affects core integration)

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

**Resource Allocation Factors:**
- Required Expertise: GitHub API, plugin architecture
- Dependencies: GitHub API
- Estimated Effort: 3

**Recommended Priority:** P2

**Next Steps:**
1. Request additional information from reporter
2. Reproduce the issue in a controlled environment
3. Identify cause of detection failure
4. Implement and test fix

**Potential Assignees:** Ronaldooooos (reporter)

## Credits System Architecture Documentation

**Current Status:** IN PROGRESS

**Impact Assessment:**
- User Impact: Low (Internal documentation)
- Functional Impact: No (Documentation only)
- Brand Impact: Medium (Financial system clarity)

**Technical Classification:**
- Issue Category: Documentation
- Component Affected: Credits System
- Complexity: Moderate effort

**Resource Allocation Factors:**
- Required Expertise: Credits system architecture, technical writing
- Dependencies: None
- Estimated Effort: 3

**Recommended Priority:** P3

**Next Steps:**
1. Complete initial draft of architecture documentation
2. Review for technical accuracy and completeness
3. Add diagrams illustrating system flow
4. Integrate with existing documentation

**Potential Assignees:** sam-developer (mentioned in Discord)

## Top Priority Issues Summary

1. **Documentation Link Fixes (P1)** - Critical user-facing issue affecting all documentation users. Simple fix with high visibility impact.

2. **Token Migration (P1)** - Scheduled for October 21st, requires preparation and clear communication to ensure smooth transition.

3. **GitHub Detection Issue (P2)** - Technical bug affecting integration with a major development platform.

4. **Tool Router Implementation (P2)** - Important enhancement to core agent capabilities already in progress.

5. **generateText() API Implementation (P2)** - New core API that will enhance developer experience and capabilities.

6. **Credits System Architecture Documentation (P3)** - Important for long-term maintainability but not user-facing.

7. **Voice/Avatar Integration (P3)** - Promising future enhancement that requires research and proof-of-concept.

## Common Themes and Architectural Concerns

1. **Documentation Fragmentation** - Several issues relate to documentation problems, suggesting a need for a more comprehensive approach to maintaining documentation alongside code.

2. **Plugin Naming and Structure Consistency** - The discussion about naming conventions points to a need for clearer standards in plugin architecture.

3. **Integration with External Services** - Multiple issues involve integration with external services (GitHub, voice/avatar APIs), indicating a potential need for a more standardized approach to external API connections.

4. **Token/Financial Infrastructure** - The token migration represents a significant shift in the project's financial foundation that may require dedicated attention.

5. **Bridging Technical and Community Communication** - Several issues (especially token migration) involve both technical implementation and clear community communication.

## Process Improvement Recommendations

1. **Documentation CI Pipeline** - Implement automated link checking in documentation to catch broken links before they reach production.

2. **Plugin Development Standards** - Create and enforce clearer guidelines for plugin naming, structure, and API patterns to ensure consistency.

3. **Integration Testing Framework** - Develop a more robust framework for testing external service integrations to catch issues like the GitHub detection problem earlier.

4. **Cross-Functional Issue Triage** - Establish regular cross-functional triage sessions that include both technical and community team members to better prioritize issues affecting different aspects of the project.

5. **Architecture Decision Records** - Implement a system for documenting architectural decisions (like the plugin naming convention) to provide context for future contributors and prevent repeated discussions.