Roo Code — User Demand Report
Week: 2026-W14 Generated: 2026-04-03 Issues analyzed: 53 (52 included) Need clusters: 9
Top 10 User Needs
| Rank | Need | Issues | Score | Category | Examples |
|---|---|---|---|---|---|
| 1 | Provider and Model Configuration Enhancements | 17 | 7.8 | Configuration | #12044, #12037, #12024 |
| 2 | Expand AI Model Integrations and MCP Protocol Support | 8 | 4.2 | Integration | #12050, #12035, #12016 |
| 3 | Provider-specific API integration bug fixes | 6 | 3.3 | Integration | #12045, #12042, #12006 |
| 4 | AI Coding Assistant UX Improvements | 4 | 2.5 | Developer Experience | #12032, #12028, #11987 |
| 5 | Per-Context Settings and Model Provider Improvements | 8 | 2.2 | Configuration | #12038, #12034, #12014 |
| 6 | Chat Interface Visual Rendering Fixes | 3 | 2.1 | UI/UX | #12030, #12026, #11986 |
| 7 | Improve shell parsing and file exclusion reliability | 2 | 1.9 | Security | #12040, #12023 |
| 8 | CLI Feature Enhancements | 2 | 1.3 | Developer Experience | #12003, #11974 |
| 9 | Enhanced audio feedback and notification hooks | 2 | 1.2 | Integration | #12047, #12025 |
Rising Needs
| Need | Rising Score | This Week | Category |
|---|---|---|---|
| Improve shell parsing and file exclusion reliability | 3.0x | 2 | Security |
| Enhanced audio feedback and notification hooks | 3.0x | 2 | Integration |
| Chat Interface Visual Rendering Fixes | 1.5x | 3 | UI/UX |
Category Breakdown
- Integration: 3 clusters
- Configuration: 2 clusters
- Developer Experience: 2 clusters
- UI/UX: 1 clusters
- Security: 1 clusters
All Need Clusters
1. Provider and Model Configuration Enhancements
Users are requesting expanded model support across providers like Ollama, OpenRouter, and Z.ai, along with fixes for context management issues including token limit calculations and content truncation. These enhancements improve the system's flexibility and reliability when working with diverse AI models and configurations.
- Volume: 17 issues (17 open, 0 closed)
- Demand Score: 7.8
- Avg Reactions: 0.4 | Avg Comments: 3.9
- Example issues: #12044, #12037, #12024, #12020, #12018
2. Expand AI Model Integrations and MCP Protocol Support
Users are requesting expanded support for various AI model providers (including xAI/grok-4.20, Gemini 3, and Claude via VS Code LM API) along with MCP protocol enhancements. Key needs include fixing tool calling failures, supporting new MCP server versions and protocol specs, enabling agent-to-agent communication via A2A, and providing per-mode MCP server restrictions to manage context bloat.
- Volume: 8 issues (5 open, 3 closed)
- Demand Score: 4.2
- Avg Reactions: 0 | Avg Comments: 2.9
- Example issues: #12050, #12035, #12016, #12007, #12004
3. Provider-specific API integration bug fixes
Users are experiencing various integration issues with different AI providers, including response handling, configuration parameters, caching behavior, and deprecated API migrations. These fixes ensure reliable communication with Vertex AI, OpenAI-compatible endpoints, Mistral, AWS Bedrock, and Grok providers.
- Volume: 6 issues (6 open, 0 closed)
- Demand Score: 3.3
- Avg Reactions: 0.2 | Avg Comments: 3.2
- Example issues: #12045, #12042, #12006, #11996, #11983
4. AI Coding Assistant UX Improvements
Users want improvements to the AI coding assistant's core interaction behaviors, including better visual feedback when operations fail, expanded slash command functionality in multiline inputs, automatic checkpoint features for code change recovery, and consistent adherence to user-defined preferences. These issues collectively address the assistant's reliability, usability, and alignment with developer workflows.
- Volume: 4 issues (4 open, 0 closed)
- Demand Score: 2.5
- Avg Reactions: 0 | Avg Comments: 2.8
- Example issues: #12032, #12028, #11987, #11967
5. Per-Context Settings and Model Provider Improvements
Users want improved configuration management with per-project and per-mode settings persistence instead of global-only configurations, better handling of custom AI provider models (including context window detection and custom model names), and enhanced MCP server security with allowlist-based tool filtering. They also need initialization code that works reliably in offline/restricted environments without depending on proxy tool side effects.
- Volume: 8 issues (8 open, 0 closed)
- Demand Score: 2.2
- Avg Reactions: 0.1 | Avg Comments: 2.4
- Example issues: #12038, #12034, #12014, #12002, #11999
6. Chat Interface Visual Rendering Fixes
Users are experiencing multiple visual display issues in the chat window interface, including missing icons on Windows 10, improperly formatted markdown tables that stretch instead of scroll, and unwanted jitter when updating content. These rendering problems negatively impact the polish and usability of the interface.
- Volume: 3 issues (3 open, 0 closed)
- Demand Score: 2.1
- Avg Reactions: 0 | Avg Comments: 3
- Example issues: #12030, #12026, #11986
7. Improve shell parsing and file exclusion reliability
Users want the tool to replace regexp-based shell parsing with a true shell parser for more reliable command safety validation and allow/deny list enforcement. Additionally, they need consistent .rooignore exclusion behavior across all MCP tools to prevent inconsistent file filtering.
- Volume: 2 issues (2 open, 0 closed)
- Demand Score: 1.9
- Avg Reactions: 1 | Avg Comments: 1.5
- Example issues: #12040, #12023
8. CLI Feature Enhancements
Users want improvements to the ClaudeCode CLI including fixing the auto-approve feature to work properly in code mode, and adding a /plugin command for installing, listing, and removing plugins. These enhancements would improve workflow automation and extensibility for CLI users.
- Volume: 2 issues (2 open, 0 closed)
- Demand Score: 1.3
- Avg Reactions: 0.5 | Avg Comments: 4
- Example issues: #12003, #11974
9. Enhanced audio feedback and notification hooks
Users want distinct audio feedback for different event types like task completion and AI/extension replies, along with programmatic hooks that trigger external notification systems during user prompts. This enables better workflow integration and awareness without requiring constant screen monitoring.
- Volume: 2 issues (2 open, 0 closed)
- Demand Score: 1.2
- Avg Reactions: 0.5 | Avg Comments: 2.5
- Example issues: #12047, #12025
This report analyzes public GitHub issues only. It represents a signal from public issue discussions, not the full user base.
Generated by ReadYourUsers