claude-code - 💡(How to fix) Fix Configurable session limit for /resume picker [2 comments, 2 participants]

TL;DR

Implementing a configurable resumeLimit setting or pagination in the picker UI is likely the most effective fix to address the issue of only displaying the 50 most recent sessions.

Guidance

• Consider adding a resumeLimit setting in settings.json to allow users to configure the number of sessions displayed in the picker.
• Implement pagination or a "load more" feature in the picker UI to enable users to access older conversations beyond the initial batch.
• Evaluate the feasibility of introducing a --resume-limit N CLI flag as an alternative solution.
• Review prior issues (#35698, #29052, etc.) to ensure that all concerns and requirements are addressed in the proposed solution.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The proposed solutions aim to address the limitation of the hardcoded 50-session limit, but the implementation details and potential impact on performance or user experience are not discussed in the issue.

Recommendation

Apply a workaround by introducing a configurable resumeLimit setting, as it seems to be a more straightforward solution that can be implemented without significant changes to the existing codebase. This approach allows power users to access older conversations while minimizing potential disruptions to the existing functionality.