Skip to content

feat: add grok-4.6 xhigh reasoning effort - #901

Open
RIERS wants to merge 1 commit into
chenyme:mainfrom
RIERS:agent/grok-4.6-xhigh-reasoning
Open

feat: add grok-4.6 xhigh reasoning effort#901
RIERS wants to merge 1 commit into
chenyme:mainfrom
RIERS:agent/grok-4.6-xhigh-reasoning

Conversation

@RIERS

@RIERS RIERS commented Aug 13, 2026

Copy link
Copy Markdown

What changed

  • Register grok-4.6 as a model that actually accepts low / medium / high / xhigh.
  • Stop the Build compatibility boundary from rewriting reasoning.effort: "xhigh" to high for this model.
  • Emit grok-4.6-low|medium|high|xhigh aliases from /v1/models when the base model is available.
  • Document the Grok Build alias support in the admin i18n copy.

Why

Grok 4.6 supports extra-high thinking. Before this change it was treated as an unknown model, so client xhigh / grok-4.6-xhigh requests were defensively downgraded to high. That made Codex-style reasoning.effort=xhigh silently weaker than requested.

Related: #897

Impact

  • Clients can send model: "grok-4.6" with reasoning.effort: "xhigh" (or grok-4.6-xhigh) and the upstream Build payload keeps xhigh.
  • grok-4.5 and unknown models still downgrade xhigh/max to high.
  • Unverified max on grok-4.6 still maps to high.
  • Console catalog is unchanged; this does not invent a Console-only grok-4.6 route.

Validation

  • RED first: go test showed grok-4.6 levels=none and Build normalize xhighhigh.
  • GREEN: go test ./internal/domain/model ./internal/infra/provider/cli ./internal/infra/provider/console ./internal/transport/http/inference -count=1
  • go vet on the same packages

Grok 4.6 accepts xhigh as a real thinking level. Keep it on the
Build request path and generate grok-4.6-xhigh aliases instead of
downgrading unknown-model xhigh to high. Unverified max stays guarded.
@RIERS
RIERS marked this pull request as ready for review August 13, 2026 01:13
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