Skip to content

chore(xai): deactivate retired Grok models on 2026-05-15 - #2172

Merged
steebchen merged 1 commit into
mainfrom
chore/deactivate-retired-xai-models
May 6, 2026
Merged

steebchen merged 1 commit into
mainfrom
chore/deactivate-retired-xai-models

Conversation

@smakosh

@smakosh smakosh commented May 6, 2026 •

Copy link
Copy Markdown
Member

Summary

  • xAI is retiring the following models from its API effective May 15, 2026 at 12:00pm PT. After that date, requests to these models will fail.
  • Mark each affected xai provider entry with deactivatedAt: 2026-05-15 so the gateway stops routing to them at the cutoff.
  • Models deactivated: grok-3, grok-4-0709, grok-code-fast-1, grok-4-fast-reasoning, grok-4-fast-non-reasoning, grok-4-1-fast-reasoning, grok-4-1-fast-non-reasoning, grok-imagine-image-pro.
  • The unified grok-4-fast and grok-4-1-fast route entries also have their xAI providers (both reasoning and non-reasoning variants) marked deactivated.
  • The azure-ai-foundry providers for grok-4-1-fast-reasoning / grok-4-1-fast-non-reasoning are unaffected and remain active.

Note on Veo: the screenshot references Veo 2 / Veo 3 retirement on 2026-06-30. The gateway only ships Veo 3.1 entries, and PR #2082 already migrated the Vertex modelName to the GA -001 IDs, so no changes are needed here.

Test plan

  • Verify retired Grok models stop being routed via xAI after 2026-05-15
  • Verify grok-4-1-fast-reasoning / grok-4-1-fast-non-reasoning still resolve via azure-ai-foundry after the cutoff
  • Verify non-retired Grok models (grok-4, grok-4.3, grok-3-mini, etc.) continue to route normally

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated deactivation schedules for select XAI model providers, including image and vision-related capabilities. Changes take effect on 2026-05-15 and 2026-03-27.

Per xAI's retirement notice, the following models are retired from the
xAI API effective 2026-05-15: grok-3, grok-4-0709, grok-code-fast-1,
grok-4-fast-reasoning, grok-4-fast-non-reasoning, grok-4-1-fast-reasoning,
grok-4-1-fast-non-reasoning, grok-imagine-image-pro. The unified
grok-4-fast and grok-4-1-fast routes are also marked deactivated on the
xAI side; azure-ai-foundry providers remain active.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 6, 2026 •

Copy link
Copy Markdown
Contributor

Walkthrough

Deactivation timestamps are added to multiple XAI model provider entries in the models configuration, primarily setting deactivatedAt to 2026-05-15 across various Grok model variants and vision models.

Changes

Model Deactivation Configuration

Layer / File(s) Summary
Model Deactivation Dates
packages/models/src/models/xai.ts
Deactivation timestamps added to ten model entries: Grok-3, grok-4-0709, grok-4-fast-reasoning, grok-4-fast-non-reasoning, grok-code-fast-1, grok-4-1-fast-reasoning, grok-4-1-fast-non-reasoning, and grok-imagine-image-pro all marked with deactivatedAt: new Date("2026-05-15").

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(xai): deactivate retired Grok models on 2026-05-15' directly and clearly summarizes the main change: marking xAI Grok models with deactivatedAt timestamps for 2026-05-15.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/deactivate-retired-xai-models

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai 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.

🧹 Nitpick comments (1)
packages/models/src/models/xai.ts (1)

479-556: grok-4-fast will have zero active providers post-deactivation — confirm graceful error handling.

Unlike grok-4-1-fast, the grok-4-fast router has no azure-ai-foundry fallback. After May 15, all its providers are deactivated, so any request to this model ID will result in no routable provider. Verify that the gateway surfaces a clean user-facing error (e.g., "model unavailable" or "no active provider") rather than an internal routing failure for this and other single-provider models (grok-3, grok-4-fast-reasoning, grok-4-fast-non-reasoning) in the same situation.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/models/src/models/xai.ts` around lines 479 - 556, grok-4-fast
currently lists only deactivated providers ("grok-4-fast-non-reasoning",
"grok-4-fast-reasoning") so after 2026-05-15 requests will find no active
provider; update the routing/gateway resolver that selects a provider for a
model ID (the code that inspects providers for a model like "grok-4-fast") to
detect the zero-active-provider case and return a clear user-facing error (e.g.,
"model unavailable" / "no active provider") or route to an explicit fallback if
desired; ensure the change handles other single-provider models (e.g., "grok-3",
"grok-4-fast-reasoning", "grok-4-fast-non-reasoning") and that the error is
surfaced as a user-level response rather than an internal routing exception.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@packages/models/src/models/xai.ts`:
- Around line 479-556: grok-4-fast currently lists only deactivated providers
("grok-4-fast-non-reasoning", "grok-4-fast-reasoning") so after 2026-05-15
requests will find no active provider; update the routing/gateway resolver that
selects a provider for a model ID (the code that inspects providers for a model
like "grok-4-fast") to detect the zero-active-provider case and return a clear
user-facing error (e.g., "model unavailable" / "no active provider") or route to
an explicit fallback if desired; ensure the change handles other single-provider
models (e.g., "grok-3", "grok-4-fast-reasoning", "grok-4-fast-non-reasoning")
and that the error is surfaced as a user-level response rather than an internal
routing exception.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2ed32de8-6e4b-46d8-ac1f-98b07099c902

📥 Commits

Reviewing files that changed from the base of the PR and between 3fdd36a and f923778.

📒 Files selected for processing (1)
  • packages/models/src/models/xai.ts

@steebchen
steebchen merged commit b00b880 into main May 6, 2026
17 of 18 checks passed
@steebchen
steebchen deleted the chore/deactivate-retired-xai-models branch May 6, 2026 17: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.

2 participants