Skip to content

[Feature]: Allow renaming conversation sessions to custom names #2759

@tivris

Description

@tivris

1. Why Do You NEED This Feature?

I regularly have multiple conversations going for different tasks — one for a refactor, one for debugging CI, one for a new feature, etc. Right now they're all identified by UUIDs, and when I open /conversations I'm staring at a wall of random strings trying to remember which one was which. It's genuinely annoying when you're context-switching between 3-4 things.

2. What Is NOT Possible Right Now?

There's no way to give a conversation a name. The only identifier is the auto-generated UUID, so the conversation list is just a bunch of IDs with no context. I end up having to open conversations one by one to figure out which is which, or I just give up and start a new one (losing all the prior context).

3. What WILL Be Possible With This Feature?

Being able to tag conversations with a short name so I can actually tell them apart:

/conversations
  auth-refactor        (2 hours ago)
  fix-ci-pipeline      (yesterday)
  a1b2c3d4-...         (3 days ago)    # unnamed ones keep the UUID, no breaking change

Proposed Solution (User Experience)

Something like:

  • /rename <name> inside an active session to name/rename the current conversation
  • Maybe also forge conversation rename <id> <name> from outside a session
  • /conversations shows the custom name if one is set, falls back to UUID otherwise
  • Keep it simple — freeform string, reasonable length limit, done

Alternatives Considered

Auto-generating names from the first message or an LLM summary could help too, but it doesn't replace being able to set your own name. Could be a nice complement though.

Feature Category

CLI/UX

Priority/Impact

High - Would significantly improve my workflow

Examples from Other Tools

Pretty much every chat-based tool already does this — ChatGPT, Claude web, Zed's assistant panels, etc. It's a well-established pattern.

Additional Context

Discussed briefly on Discord with a maintainer who suggested opening an issue for it.

Pre-submission Checklist

  • I have searched existing issues and confirmed this is not a duplicate
  • I am willing to submit a PR to implement this feature

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions