fix(server): recover Prime turns after daemon reconnect - #85
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
A live Prime Agent turn could fail when only Pylon’s daemon transport reconnected, even though Prime kept the native execution alive. The recovered prompt request could also remain unresolved or reject after the worker had already admitted it.
This change keeps the existing adapter context and turn through a proven in-process reconnect. It accepts complete Prime replay metadata or an exact completed-message suffix, reconstructs missing response/tool/child state, gates descendant quiescence on the new connection generation, and fails closed when continuity cannot be proven. It never sends an admitted prompt again. Pylon process-restart adoption remains separate in #84.
Verification:
PYLON_TRANSPORT_RECONNECT_OKCloses #79
Model: GPT-5.6 Sol
Harness: Prime Agent
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.