Continue — User Demand Report
Week: 2026-W15 Generated: 2026-04-06 Issues analyzed: 37 (33 included) Need clusters: 2
Top 10 User Needs
| Rank | Need | Issues | Score | Category | Examples |
|---|---|---|---|---|---|
| 1 | API Integration and Authentication Fixes | 28 | 4.7 | Integration | #12004, #11963, #11934 |
| 2 | Document .continue/configs/ directory support | 5 | 0.0 | Documentation | #12040, #12036, #12026 |
Rising Needs
| Need | Rising Score | This Week | Category |
|---|---|---|---|
| Document .continue/configs/ directory support | 1.3x | 5 | Documentation |
Category Breakdown
- Integration: 1 clusters
- Documentation: 1 clusters
All Need Clusters
1. API Integration and Authentication Fixes
Users are experiencing multiple API integration issues including authentication failures with Anthropic and OpenAI keys, proxy connection problems, and custom headers not being passed correctly. These issues prevent proper communication with model providers and affect both the Continue proxy and direct API connections. Fixing these will ensure reliable API access and proper error handling for edge cases like context length limits.
- Volume: 28 issues (25 open, 3 closed)
- Demand Score: 4.7
- Avg Reactions: 0.1 | Avg Comments: 0.3
- Example issues: #12004, #11963, #11934, #11933, #11978
2. Document .continue/configs/ directory support
Users want documentation for the .continue/configs/ directory feature that supports local config profiles. This documentation is needed so users can understand how to organize and manage multiple configuration profiles locally. Without clear documentation, users may struggle to discover or properly utilize this configuration capability.
- Volume: 5 issues (5 open, 0 closed)
- Demand Score: 0.0
- Avg Reactions: 0 | Avg Comments: 0
- Example issues: #12040, #12036, #12026, #11968, #11944
This report analyzes public GitHub issues only. It represents a signal from public issue discussions, not the full user base.
Generated by ReadYourUsers