[FEATURE] Session restoration after reboot - can't identify which conversation is which

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

When I reboot my computer and restore iTerm2 sessions, all my Claude Code terminal sessions come back, but:

1. Can't identify which session is which - I have 5 terminals with 5 Claude sessions, but no way to tell

which conversation was about what project

1. Resume messages are useless - The "resume" preview doesn't give enough context to identify the

conversation

1. No session IDs or names - There's no way to label or identify sessions for later restoration

## Expected Behavior
When resuming a Claude Code session, I should be able to:

• See a meaningful summary/preview of what the conversation was about
• Optionally name/label sessions for future reference
• See the working directory or last files touched
• Have session IDs that are human-readable or correlate to something useful

## Workaround Currently Using
None - I just have to guess which terminal had which conversation or start over

Cluade Code 2.0.22

Proposed Solution

I want to provide nice names to my conversations. I've tried asking it to name them but that doesn't work either.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

I run five projects at the same time, and so I have five separate terminal windows

I then take each terminal window and split it into more terminal windows to represent the different conversation strands that I'm doing on that particular project.

I use item and I have remember history when reloading or rebooting, but the Claude code instance closes out to the terminal and there's nothing like a session ID for the conversation visible so then when I use over -C option in that conversation Terminal it just does the last conversation that was modified for the project.

Or if I do /resume I get really vague messages that aren't helpful and sometimes I noticed that there's even conversation I know should exist and they're not there at all and I know this by pressing resume multiple times and testing the different variationsI get really vague messages that aren't helpful and sometimes I noticed that there's even conversation set. I know should exist and they're not there at all and I know this by pressing resume multiple times and testing the different variations trying to find the conversation I had been working on earlier..

This is such a painful situation having to reset up environments over and over again.

Additional Context

_No response_