aider — User Demand Report

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

Top 10 User Needs

Rising Needs

Category Breakdown

• Reliability: 7 clusters
• Developer Experience: 2 clusters
• Integration: 1 clusters

All Need Clusters

1. Resolving CLI crashes and enhancing terminal error handling

Users want the application to stop crashing due to Unicode encoding failures, path resolution issues, missing dependencies, and permission checks during startup and execution. They also request new CLI flags for headless automation and clearer workflow documentation to streamline their development process. Implementing these fixes will ensure consistent, uninterrupted operation across different operating systems and deployment setups.

• Volume: 20 issues (9 open, 11 closed)
• Demand Score: 6.2
• Avg Reactions: 0.1 | Avg Comments: 0.7
• Example issues: #4986, #4985, #4984, #4966, #4963

2. Gracefully Handle Git Errors and Prevent Startup Crashes

Users want the application to manage Git permission issues, missing working trees, and configuration problems gracefully to avoid application failures during startup. They also request improved exception handling and accurate gitignore warnings to prevent auto-commit blockages and ensure underlying bugs are properly surfaced rather than masked. These enhancements will improve system stability and provide a smoother, more predictable development workflow.

• Volume: 6 issues (2 open, 4 closed)
• Demand Score: 3.4
• Avg Reactions: 0 | Avg Comments: 0.7
• Example issues: #4971, #4956, #4947, #4944, #4932

3. Graceful Handling Of Missing Or Incompatible Dependencies

Users want the application to manage optional or conflicting third-party packages gracefully instead of failing during initialization. They specifically request actionable error messages that guide users on how to resolve missing or incompatible library versions. Addressing these issues will prevent unexpected startup crashes and streamline the overall development experience.

• Volume: 2 issues (0 open, 2 closed)
• Demand Score: 1.9
• Avg Reactions: 0 | Avg Comments: 1
• Example issues: #4979, #4961

4. Resolve startup crashes caused by dependency version conflicts

Users are experiencing application startup failures triggered by missing or incompatible Python package dependencies. Resolving these library conflicts and import errors is critical to prevent crashes and guarantee a stable, reliable launch experience.

• Volume: 4 issues (2 open, 2 closed)
• Demand Score: 1.8
• Avg Reactions: 0 | Avg Comments: 0.5
• Example issues: #4983, #4964, #4962, #4904

5. Fix Crashes From Unmapped LiteLLM Exception Types

Users are reporting application crashes due to newly added or missing exception mappings in the LiteLLM client. They request proper handling and mapping of these errors to prevent unexpected runtime failures. Addressing this ensures stable operation and graceful error recovery when interacting with external LLM providers.

• Volume: 2 issues (0 open, 2 closed)
• Demand Score: 1.7
• Avg Reactions: 0 | Avg Comments: 1
• Example issues: #4978, #4897

6. Improve Core CLI Reliability, Setup, and Execution Handling

Users are requesting improvements to the application’s installation process, startup resilience, and terminal command handling to minimize setup friction and runtime errors. They also seek secure subprocess execution, flexible provider configurations, and local processing options to support safer and more customized development workflows. These enhancements collectively aim to deliver a more stable, predictable, and efficient developer tooling experience.

• Volume: 8 issues (8 open, 0 closed)
• Demand Score: 1.7
• Avg Reactions: 0.3 | Avg Comments: 0.1
• Example issues: #4980, #4976, #4955, #4954, #4949

7. Graceful Handling of Symlink Loops During File Scanning

Users want the system to detect and safely bypass circular symbolic link references when traversing directories or resolving paths. This prevents infinite recursion and application crashes that currently interrupt development workflows. Proper loop handling ensures consistent and reliable file operations across complex filesystem structures.

• Volume: 2 issues (0 open, 2 closed)
• Demand Score: 1.7
• Avg Reactions: 0 | Avg Comments: 1
• Example issues: #4965, #4892

8. Fix startup crash from duplicate analytics module arguments

Users are reporting application failures at startup due to a duplicate parameter conflict in the analytics and telemetry module. Resolving this initialization error is critical to ensure stable application launches and prevent tracking disruptions.

• Volume: 2 issues (0 open, 2 closed)
• Demand Score: 1.6
• Avg Reactions: 0 | Avg Comments: 1
• Example issues: #4951, #4905

9. Fix tree-sitter query parsing crashes during repo map generation

Users want to resolve crashes triggered by unhandled tree-sitter queries when generating repository maps. These parsing failures interrupt development workflows and block access to essential repository navigation features. Addressing these errors will ensure stable and uninterrupted codebase exploration.

• Volume: 2 issues (1 open, 1 closed)
• Demand Score: 1.1
• Avg Reactions: 0.5 | Avg Comments: 0.5
• Example issues: #4919, #4888

10. Graceful Error Handling for Missing or Unrecognized LiteLLM Exceptions

Users are experiencing application crashes when encountering missing, renamed, or unrecognized exception types from the LiteLLM library. They are requesting more robust error handling logic to catch and manage these edge cases gracefully without interrupting execution. Implementing this will improve overall system stability when interacting with evolving third-party dependencies.

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

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

Generated by ReadYourUsers