Repository navigation
Default optional triage path hints - #56
Merged
Merged
Conversation
jacobprall
force-pushed
the
triage-default-paths
branch
from
October 25, 2026 21:01
724b59c to
a55e535
Compare
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.
Fix
Default
relevantPathsto an empty array when the Triage agent omits it. The prompt still asks for path hints, but this advisory field no longer blocks an otherwise valid decision.Live evidence
Autopilot root and child orchestration succeeded on the demo deployment. Triage then exhausted all three submit attempts because Claude repeatedly omitted only
relevantPaths.Verification
npm run check(23 files, 133 tests)