[FEATURE] Configurable session limit in /resume picker

Resolved 💬 3 comments Opened Feb 26, 2026 by rakesh-vs Closed Mar 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The /resume session picker displays a hardcoded maximum of 50 sessions.

As a power user working across multiple branches and projects daily, older sessions fall off the list within a couple weeks and become unreachable through the picker. The cleanupPeriodDays setting controls how long sessions are retained on disk, but there's no way to control how many are shown in the picker UI.

Proposed Solution

Add a setting like resumeSessionLimit (or similar) to control how many sessions the /resume picker displays:

{ "resumeSessionLimit": 100 }

The default can remain 50 for performance, but power users should be able to increase it.

Alternative Solutions

Alternatives:

  • claude -r <name> works if you remember the exact session name
  • claude --from-pr <number> works for PR-linked sessions
  • /rename helps make sessions findable via search

But none of these solve browsing older sessions through the picker

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

Use Case Example:

  1. I work on 5-10 branches per week across a large monorepo
  2. Each branch spawns multiple Claude Code sessions
  3. After ~2 weeks, early sessions drop off the 50-item picker
  4. I want to resume a session from 3 weeks ago but can't find it
  5. With a configurable limit (e.g., 100-200), I could scroll back

further and find it

Additional Context

cleanupPeriodDays already controls disk retention (I set mine to 365), so the data is there - it's just not shown in the picker.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗