Skip to content

chore(models): drop retired grok-4-1-fast from metadata, tests, and provider docs (#29523) - #32260

Merged
teknium1 merged 2 commits into
mainfrom
chore/29523-drop-grok-4-1-fast
May 25, 2026
Merged

chore(models): drop retired grok-4-1-fast from metadata, tests, and provider docs (#29523)#32260
teknium1 merged 2 commits into
mainfrom
chore/29523-drop-grok-4-1-fast

Conversation

@teknium1

Copy link
Copy Markdown
Contributor

Summary

Drops the retired grok-4-1-fast model from agent/model_metadata.py's DEFAULT_CONTEXT_LENGTHS, the corresponding test assertions, and the xAI provider docs. Pure metadata + docs cleanup, no runtime behavior change for any non-retired model.

Salvages PR #29523 (@RonHillDev). Closes #29523's original issue scope (retired model still surfacing in user-facing lists, error messages, and docs).

Changes

  • agent/model_metadata.py — remove "grok-4-1-fast": 2000000 from DEFAULT_CONTEXT_LENGTHS. The grok-4-fast entry already covers the live successor at the same 2M context.
  • tests/agent/test_model_metadata.py — remove the grok-4-1-fast assertion from test_grok_models_context_lengths and the grok-4-1-fast-reasoning / -non-reasoning cases from test_grok_substring_matching.
  • website/docs/integrations/providers.md/model grok-4-1-fast-reasoning/model grok-4-fast-reasoning in the xAI Grok section.
  • scripts/release.py (follow-up) — AUTHOR_MAP entry for ronhi@buildabear1.localdomainRonHillDev so the attribution check passes (the original commit was authored from a machine-local email, not a GitHub noreply).

What's preserved

  • The historical comment block at agent/model_metadata.py:257-258 still references grok-4-1-fast-(non-)reasoning in the "REJECTS effort" list — that's documenting what was tested live on 2026-05-10, not asserting current capability. Untouched.
  • hermes_cli/models.py _XAI_STATIC_FALLBACK is also untouched — fix(xai): drop models being retired May 15, 2026 from pickers #23291 already collapsed it to live models, re-adding entries here would regress the upstream sweep.

Validation

scripts/run_tests.sh tests/agent/test_model_metadata.py
=== 102 tests passed, 0 failed in 1.3s ===

Credit

@RonHillDev did the work. Salvage just adds the AUTHOR_MAP entry needed for CI.

ronhi and others added 2 commits May 25, 2026 14:31
xAI retired grok-4-1-fast. hermes_cli/models.py already removed it from
the static fallback in an earlier commit, but the context-length
metadata, the tests pinning those values, and the provider doc still
referenced the retired ID. Clean those up so retired model names stop
appearing in user-facing output.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Maps the machine-local commit email (ronhi@buildabear1.localdomain) to
the GitHub login RonHillDev so the attribution check passes.
@github-actions

Copy link
Copy Markdown
Contributor

🔎 Lint report: chore/29523-drop-grok-4-1-fast vs origin/main

ruff

Total: 0 on HEAD, 0 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 0 pre-existing issues carried over.

ty (type checker)

Total: 9347 on HEAD, 9347 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 4946 pre-existing issues carried over.

Diagnostics are surfaced as warnings — this check never fails the build.

@teknium1
teknium1 merged commit b6ce7a4 into main May 25, 2026
27 checks passed
@teknium1
teknium1 deleted the chore/29523-drop-grok-4-1-fast branch May 25, 2026 21:51
@alt-glitch alt-glitch added type/refactor Code restructuring, no behavior change P3 Low — cosmetic, nice to have comp/agent Core agent runtime: loop, agent_init, prompt builder, context-compression, responses endpoint provider/xai xAI (Grok) labels May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/agent Core agent runtime: loop, agent_init, prompt builder, context-compression, responses endpoint P3 Low — cosmetic, nice to have provider/xai xAI (Grok) type/refactor Code restructuring, no behavior change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants