fix(coding-agent): keep fork session id aligned#4799
Merged
Conversation
Collaborator
|
cheers! |
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
2 participants
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.
Forking a session from the first message would generate two different session IDs: one is used in the file name and the other in the JSONL header.
How to reproduce:
/fork/sessionExpected result: the file and the header IDs are the same.
Actual result: the IDs are different:
Also, the forked session does not reference the original one as its parent. The two sessions are stand-alone.
This PR aligns the IDs and fixes the parent reference:
The ID mismatch was problematic for me, because my session search script would get the header session ID and try to
findthe session file by that ID – to no avail.