fix: restore --resume functionality for most recent session #5401
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.
This PR fixes the
--resumeflag to correctly resume the most recent session when used without additional parameters, restoring functionality that I accidentally regressed in PR #5360After PR #5360, using
goose run --resumeorgoose session --resumewithout specifying a session name or ID would create a new session instead of resuming the last used sessionImplementation details:
get_or_create_session_id()function incrates/goose-cli/src/cli.rsto check theresumeflag when no identifier is providedresumeis true and no identifier given, fetches sessions viaSessionManager::list_sessions()and resumes the first (most recent byupdated_at)resumeis false and no identifier given, creates a new session as before--nameand--session-idparameters from PR fix: --session-id shouldn't work without --resume, but --name should #5360