Historical Session Browser

Problem

During long debugging sessions or parallel project work, users often want to reopen previous conversations for the current project without leaving the active terminal and manually scanning files. Historical Session Browser turns this into an interactive picker: when the user types /session or session, or asks to continue an old conversation or switch project sessions, the skill lists available sessions and opens the selected one in a new window while preserving the current session.

How It Works and Limits

The skill typically works as follows:
- Runs list-sessions to fetch sessions for the current project;
- Parses fields such as sessionId, title, lastPrompt, firstPrompt, mtime, isActive, and sizeMB;
- Presents candidates through AskUserQuestion, adds filtering when there are more than 12 sessions, and marks the current session;
- After confirmation, launches a new terminal window on Windows, macOS, or Linux to resume the session;
- Reports that the session opened in a new window while the current window remains unchanged.

It does not handle /resume, which exits first, and it is not intended for generic session-management questions or for inspecting project memory and history files. If the user selects the current session, the skill should cancel and note that they are already in that session.