Repository navigation
fix(prime): recover completed tool cycles after reconnecting - #521
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
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. |
34 of 51 tasks
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.
A native Prime tool call and its matching result can reach a complete reconnect snapshot before their live events. Pylon rejected this valid completed cycle and failed the turn.
Recover ordered, uniquely matched completed cycles for the same delivered prompt, while retaining exact transcript overlap, connection/proof fences, and the no-queued-input requirement. Reject unmatched or reused calls, wrong names, duplicate results, and extra user messages. Resolve delayed assistant starts and deltas against their exact completion before publishing them, within the existing event bounds. New prompt IDs stream normally. Suppress exact recovered completions so recovery cannot duplicate output or transcript progress.
Validation: the focused regression failed before the fix; all 483 adapter/runtime/event tests pass, scoped lint passes, and the server typecheck passes. The bounded adversarial checkpoint passed after verifying complete delayed assistant event sequences. Fresh real web/mobile acceptance is underway under #114. The original acceptance snapshot was not retained; this regression proves the specific valid schedule, without claiming the failed snapshot's exact shape was recovered.
Model: GPT-6 Codex. Harness: Pylon/Codex API.