Skip to content

ci(warden): Use Kimi K3 for Warden reviews - #211

Open
gricha wants to merge 2 commits into
mainfrom
feat/warden-kimi-k3
Open

ci(warden): Use Kimi K3 for Warden reviews#211
gricha wants to merge 2 commits into
mainfrom
feat/warden-kimi-k3

Conversation

@gricha

@gricha gricha commented Aug 22, 2026

Copy link
Copy Markdown
Member

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.

gricha and others added 2 commits August 21, 2026 21:00
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 gricha changed the title ci(warden): Use Kimi K3 for org reviews ci(warden): Use Kimi K3 for Warden reviews Aug 22, 2026
@gricha
gricha marked this pull request as ready for review August 22, 2026 04:30

@sentry-junior sentry-junior Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant