It would be convenient if --resume /resume could take a /rename session name as an argument

[antoinecellerier]

Describe the feature or problem you'd like to solve

This would allow easily resuming without having to memorize a session id

Proposed solution

If a user /rename s a session, allow using that as an alternate identifier. If matching is ambiguous, fallback to the current session picker experience.

Example prompts or workflows

start a session
do stuff
/rename foo
exit

copilot /resume foo
you're ready to go

Additional context

No response

[jakissel]

Found this feature request after wanting to request the same thing! I'm going to add additional context/workflows here that I was going to include in my initial request, so I don't create duplicate request noise.

Current Naive Workaround Latent Feature

I figured out you can just rename the session-state folders yourself to replicate this functionality. Renaming the folder causes --resume= to work already so you could possibly leverage that already too like I am. I don't know the ramifications of this manual folder rename though, and if this causes some other things to break internally, like if that guid is used in more places than just the folder name. Formalizing this feature would make it resilient to weird edge cases where the original guid is respected or expected explicitly.

Additional Context for feature request

Allow /rename with a flag (or a new command like /alias) to set a unique, human-readable identifier for a session that renames the session-state folder and can be used with copilot --resume=<name>.
The key point being that the session-state folder name is actually changed by the additional /rename option or new command.
Possibly the named sessions could live in a sub folder of session-state/named-sessions instead of the base where the guids live, so you don't have to sift between all the guids for the differently named sessions.
Assumption: If the developer chose to take a second to use the /rename command, it is likely that they want to easily recall and browse to that session, or reference it again in the future in more ways than just with the --resume feature. So making it easy to browse to in folder hierarchy is also high value.

Additional Workflows

1. Browsing session files in VS Code: I often keep ~/.copilot/session-state/ open as a VS Code workspace. If I had named folders like db-schema-migration and onboarding-flow they would immediately be more obvious in the file explorer, letting me browse plan.md files and session artifacts by meaningful names instead of scanning dozens of anonymous GUID folders.
2. Cross-session reference: You remember a useful plan from a prior session. Because that session's folder is named perf-optimization, you can point your current copilot to read ~/.copilot/session-state/perf-optimization/plan.md and ask it to use some part of it as a reference - no hunting through GUIDs or --resume lists to locate the right guid. This could even be done with a prompt "From my 'perf-optimization' session, can you use a similar plan and apply those to this current repository i am working in". Nicer to write "From my 'perf-optimization' session, can you..." than writing "Open ~/.copilot/session-state/session guid/plan.md, can you..."

[copilot-cli-bot]

This appears to be resolved as of GitHub Copilot CLI v1.0.89. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.