Conversation
Introduces `goose session rename` allowing users to rename a session by ID or via interactive session selection. The underlying SessionUpdateBuilder::user_provided_name already existed, so no new storage layer was needed. Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #12235
Important
Goose follows an issues-first contribution process. Before opening an external pull request, make sure the linked issue is on the Goose Issues board with the Ready status. Pull requests for issues in Inbox, Needs info, or Accepted / design are not ready for implementation. PRs without a linked issue or an issue in the wrong state can be closed with a one-liner "no correct issue".
Summary
Introduces
goose session renameallowing users to rename a session by ID or via interactive session selection.The underlying SessionUpdateBuilder::user_provided_name already existed, so no new storage layer was needed.
Testing
2b. Run goose session rename --new-name "New session name", and chose the session in the interactive selection
Related Issues
Discussion: LINK (if any)
Screenshots/Demos (for UX changes)
Before: N/A
After:
$ ./target/debug/goose session rename --new-name "Goose: Session working dir"
◇ Select a session to export:
│ 2026-09-18 18:31:14 UTC - Goose session filepath (20260918_1)
│
Session
20260918_1renamed to 'Goose: Session working dir'.