feat(langgraph): retain completed checkpoint fork authority - #1156
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
blove
enabled auto-merge (squash)
September 24, 2026 17:45
Contributor
This branch was successfully deployed
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.
The private LangGraph session can now submit new input from an exact completed root checkpoint. It retains the resulting position across later submissions, loads, dynamic-pause responses, reconnects, tool continuations and serialized result writes, so another writer advancing the thread tip cannot redirect its work.
Checkpoint authority requires the owned physical run and its exact persisted state. Uncertain acknowledgments retain staged results without retrying. Consumed pauses and contradictory tool evidence block further effects. Branch-local settled executor facts survive loads without treating historical ToolMessages as completion proof. The contributor README documents single-request transport obligations and the remaining cross-client resume race.
Validation:
This is a private runtime capability, with no public package-root migration, replay API, historical pending-tool execution, or release.