Skip to content

Refresh grok docs: CLI now serves grok-4.5, not grok-build/grok-composer-2.5-fast - #92

Open
tillemetry wants to merge 2 commits into
NateBJones-Projects:mainfrom
tillemetry:docs/grok-4.5-model-refresh
Open

Refresh grok docs: CLI now serves grok-4.5, not grok-build/grok-composer-2.5-fast#92
tillemetry wants to merge 2 commits into
NateBJones-Projects:mainfrom
tillemetry:docs/grok-4.5-model-refresh

Conversation

@tillemetry

@tillemetry tillemetry commented Aug 3, 2026

Copy link
Copy Markdown

What

The Grok Build CLI collapsed its model lineup. As of v0.2.111 (grok models on an OAuth plan) the CLI serves a single model id, grok-4.5. The old slugs grok-build and grok-composer-2.5-fast now return Invalid params: "unknown model id".

Because config.sample.toml ships model_default = "grok-composer-2.5-fast" and the README's plan-lane example routes to grok-build / grok-composer-2.5-fast, anyone whose Grok CLI has auto-updated past ~v0.2.81 hits an "unknown model id" error the moment they enable the grok lane — the sample default is dead on arrival.

Changes (docs, sample-config, and registry — no engine code)

  • config.sample.toml: model_defaultgrok-4.5; comments now state the CLI serves grok-4.5, flag that the old slugs return "unknown model id", and point readers at grok models to see what their installed CLI actually offers. Version stamps bumped to v0.2.111 (--no-auto-update and the no-token-fields note re-verified on v0.2.111).
  • README.md: plan-lane routing example → "model": "grok-4.5", with the same grok models pointer and a note that older v0.2.x also exposed the retired slugs.
  • registry/model-identity.toml: adds an [engines.grok.models."grok-4.5"] identity entry and makes it the grok engine default, so runs on the current CLI stop showing as unregistered in the scoreboard. The retired grok-build / grok-composer-2.5-fast entries stay for historical row identity; the noncanonical opencode→grok misroute mapping moves onto grok-4.5. All identity/taxonomy tests pass (29).

How verified

  • grok --versiongrok 0.2.111; grok models lists only grok-4.5 (default).
  • Ran a one-task Ringer probe through engine: "grok", model: "grok-4.5": worker authored working code, the executed check ran it green (exit 0). First-attempt PASS. The same probe with model: "grok-composer-2.5-fast" failed with unknown model id.

Not included

registry/model-capabilities/grok-4.5.toml (the detailed capability/evidence file) is not added — those files carry sourced auth/streaming/rate-limit claims that need a real research pass, and I didn't want to fabricate them. The existing grok-build.toml / grok-composer-2.5-fast.toml capability files are left as-is. Happy to add a properly-sourced grok-4.5.toml in a follow-up.

…ser-2.5-fast

Grok Build CLI v0.2.111 collapsed its model lineup to a single model id,
grok-4.5; the old grok-build / grok-composer-2.5-fast slugs now return
'unknown model id'. Update config.sample.toml default + comments and the
README plan-lane routing example, and point readers at 'grok models'.
Adds an [engines.grok.models."grok-4.5"] identity entry and makes it the
grok engine default, so runs on the current CLI (which serves grok-4.5) no
longer show as 'unregistered' in the scoreboard. The retired grok-build /
grok-composer-2.5-fast slugs stay registered for historical row identity;
the noncanonical opencode->grok misroute mapping moves to grok-4.5. All
identity/taxonomy tests pass (29).
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