Skip to content

Let users rename sessions directly from the resume picker #4727

@wishfulcynic

Description

@wishfulcynic

Hi team! First off, huge thanks for building the resume picker, it's already a game changer for my workflow. There's just one small friction point I've run into a few times, and I thought I'd pitch an idea before i start coding.

The issue I'm facing

When I'm handling multiple long-running sessions, the picker currently labels each session with the initial user prompt. After a couple of days, these all start looking pretty similar (lots of generic prompts like "hey codex..."). This means I often open a few sessions before I finally land on the one I wanted.

A simple "rename" feature would be great here, allowing me to label each chat clearly and spot it immediately next time.

How this could work

Here's what I'm thinking: Within the picker, pressing a key (maybe r) would let you rename the selected session. It would then prompt for a new, short label and save this label alongside the existing rollout. From that point on, the picker displays your custom title instead of the initial user message.

Possible implementation

We could either extend SessionMeta to store this new title or add a small sidecar file indexed by conversation ID. If no custom title is set, we simply revert to the original behavior. I'd reuse the current editing prompt control used by the picker for consistency.

Open points for discussion

  • Would extending SessionMeta be okay, or would it be better to use a separate file to avoid modifying older JSON lines?
  • Should the custom titles also appear in other areas (like codex resume --help or session headers within the TUI), or keep them limited to the picker for now?

Let me know your thoughts. I'm happy to tweak based on your feedback. If the general direction feels good, I'll jump straight into implementation!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions