Archive report

Void · 2026-W14

Void — User Demand Report

Week: 2026-W14 Generated: 2026-04-03 Issues analyzed: 50 (42 included) Need clusters: 11

Top 10 User Needs

RankNeedIssuesScoreCategoryExamples
1Enhanced AI provider configuration and authentication30.7Configuration#952, #892, #886
2Fix UI rendering and interaction bugs30.6UI/UX#939, #938, #914
3Expand AI Provider Integration and Capabilities90.4Integration#906, #894, #891
4MCP Server Integration Fixes and Features60.3Integration#945, #907, #899
5Critical Bug Fixes for Core Functionality40.3Developer Experience#924, #898, #890
6Build environment and tooling configuration20.2Developer Experience#931, #882
7Enhanced AI provider and model configuration options40.2Configuration#905, #904, #887
8Improve IDE interface controls and interactions40.2Developer Experience#934, #895, #872
9Chat Panel UI Enhancements and Bug Fixes20.2UI/UX#925, #877
10Fix Gemini API integration bugs20.2Integration#902, #874

Rising Needs

NeedRising ScoreThis WeekCategory
Enhanced AI provider configuration and authentication2.0x3Configuration

Category Breakdown

  • Configuration: 3 clusters
  • Integration: 3 clusters
  • Developer Experience: 3 clusters
  • UI/UX: 2 clusters

All Need Clusters

1. Enhanced AI provider configuration and authentication

Users want more flexible options for connecting to AI model providers, including support for multiple provider profiles, API key authentication for servers like vLLM, and the ability to connect to endpoints with self-signed SSL/TLS certificates. These enhancements would enable integration with a wider variety of AI services and deployment scenarios.

  • Volume: 3 issues (1 open, 2 closed)
  • Demand Score: 0.7
  • Avg Reactions: 0 | Avg Comments: 0.7
  • Example issues: #952, #892, #886

2. Fix UI rendering and interaction bugs

Users are experiencing multiple UI rendering failures where content appears blank white, dropdowns don't expand when clicked, and the editor fails to render properly on startup or when opening folders. These issues prevent users from effectively interacting with and using the editor interface.

  • Volume: 3 issues (3 open, 0 closed)
  • Demand Score: 0.6
  • Avg Reactions: 0.3 | Avg Comments: 2
  • Example issues: #939, #938, #914

3. Expand AI Provider Integration and Capabilities

Users want to add support for new AI providers including LLaMa, Mistral, nano-gpt.com, kimi 2k, Claude Code, and automatic OpenRouter free tier fetching. They also want internet search and web scraping capabilities for AI models, along with fixes for existing AI features like file search and Unicode character handling.

  • Volume: 9 issues (7 open, 2 closed)
  • Demand Score: 0.4
  • Avg Reactions: 1 | Avg Comments: 1.6
  • Example issues: #906, #894, #891, #885, #876

4. MCP Server Integration Fixes and Features

Users are experiencing issues with MCP (Model Context Protocol) server connectivity, tool invocation with local LLMs, and SSE-based server support for decorated Python functions. They also want new capabilities like dynamic LLM model switching via API hooks and prompt inspection through request proxying. These issues collectively indicate a need for improved MCP integration robustness and extended functionality.

  • Volume: 6 issues (6 open, 0 closed)
  • Demand Score: 0.3
  • Avg Reactions: 0 | Avg Comments: 1.2
  • Example issues: #945, #907, #899, #873, #868

5. Critical Bug Fixes for Core Functionality

Users are reporting multiple bugs that need to be addressed to ensure the application works correctly. These include agent output formatting problems, security vulnerabilities in dependencies, path handling issues on Windows systems, and bundling errors with the Excalidraw integration. Fixing these issues will improve application reliability and developer experience.

  • Volume: 4 issues (3 open, 1 closed)
  • Demand Score: 0.3
  • Avg Reactions: 0.3 | Avg Comments: 1
  • Example issues: #924, #898, #890, #869

6. Build environment and tooling configuration

Users need proper build environment setup for smooth development workflows. This includes adding support for new IDE versions like Visual Studio 2026 and resolving PATH issues that prevent tools like tailwindcss from being accessible during builds.

  • Volume: 2 issues (2 open, 0 closed)
  • Demand Score: 0.2
  • Avg Reactions: 0.5 | Avg Comments: 2.5
  • Example issues: #931, #882

7. Enhanced AI provider and model configuration options

Users want more flexibility to customize their AI integration experience. This includes UI customization options like hiding floating widgets, configurable provider endpoints for custom proxies, per-model routing support for providers like OpenRouter, and the ability to manage custom model tags without modifying core files. These features would give users greater control over their AI setup and reduce the need for manual code modifications.

  • Volume: 4 issues (2 open, 2 closed)
  • Demand Score: 0.2
  • Avg Reactions: 0.3 | Avg Comments: 2
  • Example issues: #905, #904, #887, #884

8. Improve IDE interface controls and interactions

Users want improvements to the IDE interface, including direct numeric input for reasoning budget settings, better popup menu positioning that doesn't interfere with text selection, browser-based IDE support for Void Agent settings, and expanded model support for qwen3-coder in file editing. These changes aim to enhance usability and functionality of the development environment.

  • Volume: 4 issues (3 open, 1 closed)
  • Demand Score: 0.2
  • Avg Reactions: 2.5 | Avg Comments: 4.8
  • Example issues: #934, #895, #872, #857

9. Chat Panel UI Enhancements and Bug Fixes

Users want improvements to the chat panel interface, including fixing a CSS bug where file drag-and-drop overlays fail to display due to missing positioning. Additionally, they want new UI features like parallel tool calling, web search integration, image attachments, thinking process visualization, tool call pending animations, and improved search functionality.

  • Volume: 2 issues (2 open, 0 closed)
  • Demand Score: 0.2
  • Avg Reactions: 1 | Avg Comments: 1
  • Example issues: #925, #877

10. Fix Gemini API integration bugs

Users are experiencing bugs in the Gemini API integration including broken request handling when proxying through OpenAI-compatible endpoints with specific settings, and invalid function name generation when .voidrules is empty. These issues prevent proper functionality in AI provider integrations.

  • Volume: 2 issues (2 open, 0 closed)
  • Demand Score: 0.2
  • Avg Reactions: 0.5 | Avg Comments: 1
  • Example issues: #902, #874

11. LLM Provider Configuration and Model Support

Users need improved support and configuration options for various LLM providers including Gemini, GPT-OSS, and LM Studio. These issues involve fixing model selection, supporting non-standard model tags, and enabling file access for local models. This improves flexibility for users working with different LLM ecosystems.

  • Volume: 3 issues (0 open, 3 closed)
  • Demand Score: 0.1
  • Avg Reactions: 1 | Avg Comments: 1
  • Example issues: #893, #889, #865

This report analyzes public GitHub issues only. It represents a signal from public issue discussions, not the full user base.

Generated by ReadYourUsers