Named sessions for --resume

Resolved 💬 6 comments Opened Sep 24, 2025 by sherifkozman Closed Feb 4, 2026

What feature would you like to see?

Feature Request: Named Sessions for --resume

Problem
The current --resume feature shows multiple sessions without clear identifiers. For developers who work across several projects, it’s easy to get lost and accidentally pick the wrong session since there are no names or tags to distinguish them.

Proposal
Introduce optional session names and tags:

  • codex --name "checkout-fix" to assign a human-friendly name.
  • Support --tags payments,urgent for lightweight grouping.
  • /session name <newName> and /session tags +tag -tag to rename or retag interactively.
  • Update the --resume picker to show name, repo, tags, and last_activity.
  • Allow fuzzy matching:

codex --resume checkout → resumes session with matching name.

Why

  • Reduces confusion when resuming across many sessions.
  • Keeps everything local, backwards-compatible, and low-risk.
  • Minimal implementation: store metadata (name, tags, repo, branch, last_activity) in a meta.json file alongside existing session history.

Example UX
▸ checkout-fix [repo: shop-web] [tags: payments, urgent] [updated: 12m]
flaky-tests [repo: svc-orders] [tags: tests] [updated: 2h]
spike-mcp [repo: tools] [tags: research] [updated: 3d]

Next Steps
If maintainers agree this is valuable, I can prepare a PR implementing:

  • Metadata file write/read
  • CLI flags for --name and --tags
  • Resume picker rendering improvements
  • Basic interactive /session commands

Would love feedback on whether this direction makes sense before starting work.

Are you interested in implementing this feature?

Yes

Additional information

_No response_

View original on GitHub ↗

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