Tabby — User Demand Report

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

Top 10 User Needs

Rising Needs

Category Breakdown

• Developer Experience: 5 clusters
• Platform Support: 2 clusters
• Configuration: 2 clusters
• Integration: 2 clusters

All Need Clusters

1. Platform support and deployment flexibility enhancements

Users are requesting improvements across multiple dimensions: better plugin stability for Eclipse and IntelliJ, expanded deployment options for air-gapped/CPU-only environments, support for new model architectures (Qwen3-Coder-Next, candle backends), and fixes for infrastructure compatibility issues with Homebrew and ROCM. These changes would make Tabby more robust and usable across diverse development environments.

• Volume: 17 issues (11 open, 6 closed)
• Demand Score: 1.7
• Avg Reactions: 0.6 | Avg Comments: 1
• Example issues: #4471, #4460, #4452, #4446, #4415

2. IDE Plugin Bug Fixes and Context Improvements

Users are experiencing various reliability issues with IDE plugins (IntelliJ IDEA, VSCode, JetBrains Rider) including stuck loading states, unresponsive autocompletion, and connection failures in remote development scenarios. Additionally, users want improved context handling to include split view files, imported dependencies, and related files in AI code completion and chat suggestions.

• Volume: 7 issues (6 open, 1 closed)
• Demand Score: 1.4
• Avg Reactions: 0.3 | Avg Comments: 0.7
• Example issues: #4420, #4418, #4404, #4396, #4388

3. Improve Git Integration and Repository Operations

Users want better Git integration across multiple platforms, including support for GitLab subgroups, self-hosted Gitea, and advanced Git features like SHA256 object format and semantic merge drivers. They also need improved repository operations such as incremental git pulls, branch selection for indexing, and better handling of Git LFS errors. These improvements would enhance developer workflows for teams working with complex Git repositories and branching strategies.

• Volume: 8 issues (6 open, 2 closed)
• Demand Score: 1.2
• Avg Reactions: 0.3 | Avg Comments: 1.3
• Example issues: #4451, #4449, #4431, #4408, #4407

4. Improve Code Completion Speed and Context Awareness

Users want faster, more intelligent code completion suggestions. The first request seeks to eliminate perceived delay by precomputing accept and reject branches for instant follow-up suggestions, while the second wants to enhance completion relevance by integrating screen context from Screenpipe for better context-aware recommendations.

• Volume: 2 issues (2 open, 0 closed)
• Demand Score: 1.0
• Avg Reactions: 2.5 | Avg Comments: 0.5
• Example issues: #4472, #4428

5. Improve self-hosted deployment flexibility and configuration

These issues request greater flexibility for self-hosted and offline deployments, including alternative authentication methods like x-token-auth for Bitbucket, configurable security policies to disable password complexity requirements, and improved user registration workflows with case-insensitive email handling. Users need the ability to adapt the software to their specific infrastructure requirements rather than being forced into a one-size-fits-all approach.

• Volume: 3 issues (2 open, 1 closed)
• Demand Score: 0.6
• Avg Reactions: 1.3 | Avg Comments: 2.3
• Example issues: #4434, #4426, #4400

6. Expand model support and API integrations

Users are requesting expanded support for new AI model types and API integrations, including thinking/reasoning models and Mistral's codestral-embed API for embeddings. Additionally, users want local model loading to work without network connectivity. These enhancements would improve the platform's flexibility and enable offline functionality.

• Volume: 3 issues (1 open, 2 closed)
• Demand Score: 0.5
• Avg Reactions: 1.7 | Avg Comments: 0.7
• Example issues: #4422, #4412, #4374

7. Tabby Agent Code Assistance Improvements

Users want to integrate the Agent Skills framework to enhance Tabby's code assistance capabilities, while also addressing a regression in code completion functionality that appeared between versions 1.7.0 and 1.8.0. These improvements would strengthen Tabby Agent's effectiveness as a code completion tool.

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

8. Enhanced configuration file and settings support

Users want improved configuration management including support for custom katana configuration files, proper control of resource settings like max_input_length and completion timeout, and cross-platform config.toml support on Windows. These enhancements would give developers more flexibility in customizing tool behavior and resource usage.

• Volume: 4 issues (3 open, 1 closed)
• Demand Score: 0.3
• Avg Reactions: 1 | Avg Comments: 1.3
• Example issues: #4401, #4358, #4356, #4351

9. OpenAI/LiteLLM Integration Tool Calling

Users want enhanced OpenAI and LiteLLM API integration with support for structured tool calling using Pydantic schemas. They also need fixes for compatibility with newer models like gpt-5 to ensure smooth integration with the latest AI capabilities.

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

10. Fix incorrect information display in CLI and endpoints

Users are encountering bugs where the system displays inaccurate information - specifically incorrect version numbers in CLI tools and Homebrew packages, as well as wrong port numbers showing the default instead of the configured value. These display errors reduce trust in the tool's accuracy and make it difficult for developers to properly understand their environment configuration.

• Volume: 2 issues (0 open, 2 closed)
• Demand Score: 0.2
• Avg Reactions: 0 | Avg Comments: 1.5
• Example issues: #4369, #4364

11. GPU Hardware Support and Acceleration

Users want broader GPU hardware support, specifically for Nvidia 10xx series GPUs like the GTX 1050 Ti, as well as proper GPU acceleration when Tabby runs inside Docker containers. GPU acceleration is critical for performance, so users need both expanded hardware compatibility and correct configuration in containerized environments.

• Volume: 2 issues (1 open, 1 closed)
• Demand Score: 0.1
• Avg Reactions: 0 | Avg Comments: 0.5
• Example issues: #4368, #4359

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

Generated by ReadYourUsers