feat(session): continue from safe assistant and tool boundaries - #116
Open
danielkov wants to merge 1 commit into
Open
feat(session): continue from safe assistant and tool boundaries#116danielkov wants to merge 1 commit into
danielkov wants to merge 1 commit into
Conversation
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
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.
Summary
Extend
/branchto continue after committed assistant messages and tool-result boundaries, in addition to editing earlier user prompts. Assistant and tool checkpoints retain the selected item and open an empty draft for the next user message.Motivation
Builds on #115 toward message-level transcript navigation without discarding alternate futures.
Impact
Only a result that closes its complete tool-call batch is eligible; partial batches, orphan or duplicate results, and invalid ordering are rejected. Before-user checkout and its original-prompt prefill remain unchanged.
Technical details
Exact continuation prefixes
An ordered validator checks call/result structure without repairing, reordering, or borrowing later context. The existing historical address, provisional checkout, durable completion, and retry pipeline is reused without changing persistent lineage metadata.
Role-aware selection
The chooser labels User, Assistant, and Tool checkpoints and supports role filters. Roles are additive on the private response shape, with missing legacy values interpreted as User; preview text remains separate from the editable draft.