chore(agents): tier subagent models by judgment vs execution - #225
Merged
Merged
Conversation
Opus for implementers, authors and contract/security review where a miss is costly. Sonnet stays on qa, quality review and cleanup. The consumer template moves builder and debugger to opus.
zaxovaiko
requested review from
damianrzepka,
jakubfilinger-b,
klaudia-blazyczek-blurify,
marek-chmielowski-blurify,
mp-blurify and
okapitula
as code owners
September 25, 2026 20:39
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
1 participant
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.
Summary
dev,module-author,plugin-author,contract-reviewerandoperatormove to opus, joiningsecurity-reviewerandexpert.qa,quality-reviewer,cleanerandexplorestay on sonnet,docsstays on haiku.builderanddebuggerto opus, consumers pick it up on the next@openora/createbump.Why
Opus goes where a miss is costly - money-path implementation, module and plugin authoring, breaking-change and security review, root-cause debugging. Well-specified execution and pattern-matching work (tests, convention review, cleanup, search) stays on sonnet, which is cheaper per token for the same context.
Alternatives considered
Keeping
devandbuilderon sonnet. It is cheaper, but they are the main implementers on the money path, so rework from a weaker first pass would eat the saving.Risks
Higher cost per run for the five openora agents plus
builderanddebuggerdownstream. No code changes.