[FEATURE] Descriptive session naming or aliasing.

Resolved 💬 3 comments Opened Mar 5, 2026 by mth3r Closed Mar 9, 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 session directory is not human readable so I can't easily restart a conversation or session the way I can when I use Claude via the URL interface. I currently have claude create a human readable index file of the session names that I then cross reference with the directories

Proposed Solution

I'd like to be able to navigate to the session directory and the name of the folder be relevant to what the session was about. Or have the ability to tell Claude Code to name the session 'Vacation Planning' or 'Test validation' etc. It would allow better context switching for me when I'm working on several projects at the same time. relatedly I would really like that the tabs in the cmd terminal would show the something other than 'claude code.' That would help if I have multiple tabs open. Again, helps with the context switching

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

1) I am working on a family project in the evening. I wrap up the session and go to bed.
2) Start work the following day and work on several different projects and programs such that I initiate multiple Claude Code cmd terminals.
3) I want to rejoin one of those sessions with new input from a colleage and dont want to start from scratch. The problem is I can't remember which session to restart because the name doesn't mean anything to me. If I could make an alias or have claude code name the directory based on what was talked about during the session, it would be easy.
4) got home and want to continue to work on my family project. Having an alias or human readable directory would greatly ease my context switching.

Additional Context

_No response_

View original on GitHub ↗

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