aider — User Demand Report
Week: 2026-W15 Generated: 2026-04-06 Issues analyzed: 58 (57 included) Need clusters: 3
Top 10 User Needs
| Rank | Need | Issues | Score | Category | Examples |
|---|---|---|---|---|---|
| 1 | Error handling and CLI robustness improvements | 53 | 12.3 | Developer Experience | #4992, #4989, #4988 |
| 2 | Handle unencodable Unicode characters in Windows console | 2 | 0.9 | Reliability | #4986, #4948 |
| 3 | Fix TypeError when distinct_id passed multiple times | 2 | 0.8 | Developer Experience | #4951, #4905 |
Rising Needs
| Need | Rising Score | This Week | Category |
|---|---|---|---|
| Handle unencodable Unicode characters in Windows console | 2.0x | 2 | Reliability |
| Error handling and CLI robustness improvements | 1.4x | 53 | Developer Experience |
Category Breakdown
- Developer Experience: 2 clusters
- Reliability: 1 clusters
All Need Clusters
1. Error handling and CLI robustness improvements
Users are requesting better error handling across various failure scenarios including missing configurations, network failures, invalid data, and dependency issues. Additionally, there are requests to improve CLI argument validation, add non-interactive single-pass execution modes for automation, and fix cross-platform compatibility issues with Windows glob patterns.
- Volume: 53 issues (28 open, 25 closed)
- Demand Score: 12.3
- Avg Reactions: 0.1 | Avg Comments: 0.5
- Example issues: #4992, #4989, #4988, #4963, #4952
2. Handle unencodable Unicode characters in Windows console
Users want the application to handle Unicode characters that cannot be encoded in the Windows console (cp1252 encoding) without crashing. When the console encounters characters outside the supported character set, the application currently fails instead of gracefully handling orfalling back to a safe alternative. This is important for reliability and preventing unexpected crashes in Windows environments.
- Volume: 2 issues (0 open, 2 closed)
- Demand Score: 0.9
- Avg Reactions: 0 | Avg Comments: 1
- Example issues: #4986, #4948
3. Fix TypeError when distinct_id passed multiple times
Users are encountering a TypeError when distinct_id is passed multiple times to Client.capture() in analytics.py, causing the tracking functionality to fail. This bug prevents events from being properly captured and tracked. Fixing this issue will ensure the analytics library functions correctly.
- Volume: 2 issues (0 open, 2 closed)
- Demand Score: 0.8
- Avg Reactions: 0 | Avg Comments: 1
- Example issues: #4951, #4905
This report analyzes public GitHub issues only. It represents a signal from public issue discussions, not the full user base.
Generated by ReadYourUsers