Archive report

Continue · 2026-W14

Continue — User Demand Report

Week: 2026-W14 Generated: 2026-04-03 Issues analyzed: 38 (34 included) Need clusters: 7

Top 10 User Needs

RankNeedIssuesScoreCategoryExamples
1Bug Fixes and Documentation for Multi-Provider Integration112.1Developer Experience#11999, #11985, #11978
2Document config profiles and improve API error handling71.9Developer Experience#12026, #12004, #11968
3Fix API Provider Authentication and Key Configuration41.9Configuration#12008, #11961, #11956
4Fix Response Streaming and Error Handling Bugs41.9Reliability#11994, #11983, #11926
5Fix IDE stability and reliability issues31.4Reliability#11959, #11932, #11919
6Fix Tool Calling Reliability Across AI Providers30.0Reliability#11976, #11964, #11929
7Fix IntelliJ extension resource limits and CPU usage20.0Performance#11977, #11966

Rising Needs

NeedRising ScoreThis WeekCategory
Document config profiles and improve API error handling8.0x7Developer Experience
Fix API Provider Authentication and Key Configuration5.0x4Configuration
Fix IntelliJ extension resource limits and CPU usage3.0x2Performance
Bug Fixes and Documentation for Multi-Provider Integration1.6x11Developer Experience
Fix IDE stability and reliability issues1.5x3Reliability

Category Breakdown

  • Reliability: 3 clusters
  • Developer Experience: 2 clusters
  • Configuration: 1 clusters
  • Performance: 1 clusters

All Need Clusters

1. Bug Fixes and Documentation for Multi-Provider Integration

Users are requesting various bug fixes to improve reliability across different LLM providers (OpenAI, Ollama, LM Studio, OpenRouter) and IDE integrations (IntelliJ/JetBrains). These issues affect core functionality like streaming, tool calls, file editing, and process management. Additionally, users need documentation for CLI commands and provider-specific API headers.

2. Document config profiles and improve API error handling

Users need comprehensive documentation for the .continue/configs/ directory feature that supports local configuration profiles, making it easier to discover and use this functionality. Additionally, users want better error handling and visibility for API-related issues including maxTokens edge cases near context limits, API usage limits, and proxy connection failures so they are warned rather than experiencing silent failures.

3. Fix API Provider Authentication and Key Configuration

Users are experiencing issues with API authentication across multiple providers (Gemini, Anthropic, continue-proxy). Issues include authentication errors, API key configuration lookup failures, and the system not properly using user-provided keys over proxy credits. Users need reliable API key handling and support for custom request headers to successfully connect to external AI providers.

  • Volume: 4 issues (4 open, 0 closed)
  • Demand Score: 1.9
  • Avg Reactions: 0 | Avg Comments: 1
  • Example issues: #12008, #11961, #11956, #11952

4. Fix Response Streaming and Error Handling Bugs

Users are encountering multiple bugs that affect the reliability of the application: incorrect item emission ordering when using reasoning-enabled models, premature close errors during streaming, unhelpful 'Unknown error' messages for API quota issues, and 404 errors with certain Claude models. These issues cause unexpected failures and poor user experience during normal operation.

  • Volume: 4 issues (2 open, 2 closed)
  • Demand Score: 1.9
  • Avg Reactions: 0 | Avg Comments: 0.5
  • Example issues: #11994, #11983, #11926, #11925

5. Fix IDE stability and reliability issues

Users are experiencing critical reliability issues when using the IDE including crashes while editing files, rendering problems in Firefox with code-server, and document tracking errors when switching between text editors. These bugs prevent users from effectively using the IDE in various environments and workflows.

  • Volume: 3 issues (3 open, 0 closed)
  • Demand Score: 1.4
  • Avg Reactions: 0.3 | Avg Comments: 0.3
  • Example issues: #11959, #11932, #11919

6. Fix Tool Calling Reliability Across AI Providers

Users are experiencing critical failures when using tool calling features across different AI providers (OpenAI o1/o3-mini, Claude Opus 4.6) and environments (JetBrains IDEs, Android Studio). Issues include 500 API errors, execution hangs, and message sequencing problems that prevent tools from working properly. These reliability issues block developers from using essential functionality in their workflows.

  • Volume: 3 issues (2 open, 1 closed)
  • Demand Score: 0.0
  • Avg Reactions: 0 | Avg Comments: 0
  • Example issues: #11976, #11964, #11929

7. Fix IntelliJ extension resource limits and CPU usage

Users are experiencing the IntelliJ extension becoming unresponsive due to high CPU usage and unbounded file search results causing token overflow. These resource consumption issues make the extension unreliable and unusable during development. Users want fixes to prevent resource exhaustion and maintain stable extension performance.

  • Volume: 2 issues (2 open, 0 closed)
  • Demand Score: 0.0
  • Avg Reactions: 0 | Avg Comments: 0
  • Example issues: #11977, #11966

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

Generated by ReadYourUsers