ci(warden): Use Kimi K3 for Warden reviews - #211
Open
gricha wants to merge 2 commits into
Open
Conversation
Move the org-wide security review from Grok 4.5 at high effort to Kimi K3 at max effort. Co-Authored-By: GPT-5.6 Sol <noreply@anthropic.com>
Set the shared workflow fallback explicitly so repository-local skills without a model do not use Pi's K2.6 default. Co-Authored-By: GPT-5.6 Sol <noreply@anthropic.com>
gricha
marked this pull request as ready for review
August 22, 2026 04:30
Contributor
There was a problem hiding this comment.
Technically sound as an immediate mitigation: it removes the K2.6 fallback for repo-local skills without overriding an explicit repo model. I would still prefer the layered-default fix in getsentry/warden#514 long-term, because this workflow fallback cannot propagate effort, turn limits, auxiliary, or synthesis settings.
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.
Move the org-wide Warden security review from Grok 4.5 at high effort to Kimi K3 at max effort.
Also set the shared workflow fallback explicitly to Kimi K3. Repository-local skills that omit a model previously fell through to the Pi default, K2.6. They will now use K3 while still respecting any model or effort configured by the repository.
In the latest seven-day telemetry window, 128 of 133 workflows over 20 minutes were K2.6-only, and 85 K2.6 traces contained a provider error. The Sentry vulnerability corpus also put K3 within one known finding of Grok while using about half the total cost.
Auxiliary calls remain on Luna. Repository-local skills that omit an effort continue to use the Pi default effort; the workflow cannot set that separately today.