Repository navigation
Add multi-provider research and automatic continuation (v1.9.0) - #81
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.
Research previously required Brave, and a completed research phase could leave a parent in Plan Mode waiting for another user command. This change selects native, Brave and Firecrawl search separately for each participant and uses fenced checkpoint and final events to continue analysis automatically.
--manual-continuekeeps the manual workflow available.The dispatcher sends only saved workflow events to the verified native parent. The new
PostToolUseandInterrupthooks require separate trust. Cancellation, interruption, owner changes, uncertain acknowledgements and duplicate events retain their fences. Local search correlation labels remain worker-reported evidence; missing results are rejected.Protected reviews now require stable Claude Code 2.1.321 or later. Fable 5.2 attribution has regression coverage, and expired OAuth sessions retain the authentication failure category. Model and effort defaults are unchanged.
Validation:
Refs #27.