What changed
Roder 0.1.10 updates the xAI-backed provider catalog. The direct xai provider and the SuperGrok OAuth provider now expose grok-4.5 as their default model.
The new model entry carries a 500k context window and defaults to high reasoning. It also keeps the supported reasoning choices explicit: low, medium, and high. Existing Grok 4.3, Grok 4.20, SuperGrok Build, and SuperGrok Composer entries remain selectable, so existing pinned workflows do not need to move immediately.
Why it matters
- xAI API-key users and SuperGrok OAuth users now get the same current default model in Roder.
- Long-context coding sessions can use Grok 4.5’s 500k context window without custom catalog overrides.
- Reasoning behavior is predictable. New sessions start at high reasoning, while users can still lower reasoning for faster or cheaper turns when the provider path supports it.
- Existing Grok model selections remain available, which keeps saved configs, scripts, and comparisons stable while the default advances.
Using it
For the direct xAI API-key path, configure the xAI credential and select the provider normally:
export XAI_API_KEY="..."
RODER_PROVIDER=xai RODER_MODEL=grok-4.5 cargo run -p roder-cli
For SuperGrok, keep using the OAuth-backed provider flow:
roder auth login supergrok
RODER_PROVIDER=supergrok RODER_MODEL=grok-4.5 cargo run -p roder-cli
You can omit RODER_MODEL when you want the provider default. Pin one of the older Grok entries only when a workflow depends on that exact model behavior.