Repository navigation
Restore summary fallback for recovered agent threads - #124
Merged
Merged
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.
Fixes #102.
When two full-fidelity agents share a thread across a command, restarting during the command currently resumes successfully but sends only the second agent's new prompt. Recover the thread's prior use from its recorded events and supply the documented
summary:highfallback. Retain the rebuilt conversation so the following agent returns to normal full-fidelity reuse. Previously unused threads still start fresh.The runtime supplies
ResumeInfoas an execution-local capability on both resume paths. This reuses existing recorded events and stage outputs; it adds no persistent transcript store or log format change.Verification:
56ec3849and Fabro mainebb1f0bbb(0.387.0-nightly.0), which already includes Preserve workflow context during native skill expansion #118. The uninterrupted control carriesQA_FIRST_CONTEXT; the recovered request carries neither that answer nor a summary.QA_FIRST_CONTEXTin its stage summary, and a third agent reused the rebuilt conversation. The uninterrupted control also passed.The existing failed-predecessor-after-compaction regression passed separately. Direct-agent resume was not separately retested. The full routine gate, Docker/Daytona tiers, and compatibility corpus were not run. Issue #102 should remain open until this fix lands.