hermes - 💡(How to fix) Fix Add pagination or configurable limit to /resume recent sessions list [1 pull requests]

Problem

The in-chat /resume picker is capped at 10 recent sessions and has no pagination or way to request more results. For users with many CLI sessions, this makes older-but-still-relevant sessions effectively invisible from the interactive resume flow.

This is especially confusing because hermes sessions list --limit 50 can show more sessions, while /resume with no argument only shows the first 10.

Current behavior

Running /resume without a target prints a “Recent sessions” list with at most 10 entries.

The limit appears to be hard-coded in the CLI helper methods:

• cli.py: _list_recent_sessions(self, limit: int = 10)
• cli.py: _show_recent_sessions(self, ..., limit: int = 10)
• /resume empty-argument path calls _show_recent_sessions(reason="resume") without a larger limit or paging state.

It also filters to CLI sessions only via list_sessions_rich(source="cli", exclude_sources=["tool"], limit=limit), which is separate and reasonable, but the hard 10-row cap is the immediate UX issue.

Expected behavior

The /resume picker should support browsing beyond the first 10 sessions.

Suggested UX options:

1. Add pagination to /resume:

   • /resume shows page 1
   • /resume --page 2 or /resume page 2 shows the next page
   • maybe show a footer like Showing 1-10 of N. Use /resume --page 2 for more.

2. Or support a limit argument:

   • /resume --limit 30
   • /resume --all if safe

3. Or both pagination and a configurable default page size:

   • config key like sessions.resume_page_size: 10|20|30

Why it matters

Session continuity is one of Hermes' core workflows. A hard-coded 10-item resume list makes long-running users constantly fall back to hermes sessions list --limit N, copy IDs manually, and then return to /resume <id>. It is a small paper cut but happens often for users who rely on many named/long-running sessions.

Acceptance criteria

• /resume can display sessions beyond the first 10 without leaving the CLI.
• The UI communicates whether more sessions are available and how to get them.
• Existing /resume <session id or title> behavior remains unchanged.
• Tests cover the empty-argument /resume list with more than 10 eligible CLI sessions.