Skip to content

feat(providers): add xAI grok-4.5 model#5511

Merged
waleedlatif1 merged 2 commits into
stagingfrom
add-model-grok-4-5
Jul 8, 2026
Merged

feat(providers): add xAI grok-4.5 model#5511
waleedlatif1 merged 2 commits into
stagingfrom
add-model-grok-4-5

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • Add xAI's new grok-4.5 flagship model to the provider registry ($2/1M input, $6/1M output, 500K context, always-reasoning)
  • Move recommended: true from grok-4.3 to grok-4.5

Type of Change

  • New feature

Testing

Tested manually (verified pricing/context/release date against docs.x.ai live docs + secondary sources, biome-clean on the changed file)

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Jul 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Skipped Skipped Jul 8, 2026 6:45pm

Request Review

@cursor

cursor Bot commented Jul 8, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Static catalog metadata only; no runtime provider or auth changes, aside from which xAI model appears as recommended in pickers.

Overview
Registers grok-4.5 in the xAI section of the provider model catalog with pricing ($2/1M input, $6/1M output), a 500K context window, release metadata, and standard temperature bounds.

Recommended xAI pick moves from grok-4.3 to grok-4.5, so UIs and helpers that surface recommended models (e.g. copilot model options and unknown-model suggestions) will promote the new flagship instead of 4.3. The xAI defaultModel stays grok-4.3.

Reviewed by Cursor Bugbot for commit b96b4b9. Configure here.

@greptile-apps

greptile-apps Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds xAI's grok-4.5 model to the provider registry and moves the recommended flag from grok-4.3 to grok-4.5. Pricing ($2/1M input, $6/1M output), context window (500K), and capabilities are consistent with the official xAI documentation.

  • New model entry: grok-4.5 is inserted as the first model in the xAI models array with recommended: true, pricing, temperature range, and context window correctly set.
  • Release date off-by-one: releaseDate is '2026-07-09' but the model shipped on July 8, 2026, which also matches the pricing.updatedAt date already on the same entry.
  • defaultModel not updated: The xAI provider definition still declares defaultModel: 'grok-4.3' even though recommended moved to grok-4.5; getProviderDefaultModel('xai') returns the hardcoded string, so new blocks/configs will default to the older model.

Confidence Score: 4/5

The change is a straightforward model registry addition; the logic is simple and isolated to one file, but the defaultModel field being out of sync with the recommended flag means new users will silently get the older model.

The defaultModel: 'grok-4.3' field was not updated when recommended moved to grok-4.5, so getProviderDefaultModel('xai') will keep returning grok-4.3 — routing new blocks to a model that is no longer the recommended flagship. The release date being one day in the future is minor metadata noise but straightforward to fix.

apps/sim/providers/models.ts — verify the defaultModel field and releaseDate before merging.

Important Files Changed

Filename Overview
apps/sim/providers/models.ts Adds grok-4.5 as the recommended xAI model with correct pricing/context window; release date is off by one day (should be 2026-07-08), and the provider's defaultModel field was not updated from 'grok-4.3' to 'grok-4.5' to stay in sync with the recommended flag.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[xAI Provider Definition] --> B["defaultModel: grok-4.3 — not updated"]
    A --> C[models array]
    C --> D["grok-4.5 — recommended: true — 500K context"]
    C --> E["grok-4.3 — 1M context"]
    C --> F["grok-4-latest — deprecated"]
    B --> H["getProviderDefaultModel returns grok-4.3"]
    D --> I["recommended models list includes grok-4.5"]
    style B fill:#f99,stroke:#c00
    style D fill:#9f9,stroke:#0a0
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[xAI Provider Definition] --> B["defaultModel: grok-4.3 — not updated"]
    A --> C[models array]
    C --> D["grok-4.5 — recommended: true — 500K context"]
    C --> E["grok-4.3 — 1M context"]
    C --> F["grok-4-latest — deprecated"]
    B --> H["getProviderDefaultModel returns grok-4.3"]
    D --> I["recommended models list includes grok-4.5"]
    style B fill:#f99,stroke:#c00
    style D fill:#9f9,stroke:#0a0
Loading

Comments Outside Diff (1)

  1. apps/sim/providers/models.ts, line 1847 (link)

    P1 The defaultModel for the xAI provider is still 'grok-4.3', but recommended: true has been moved to grok-4.5. getProviderDefaultModel('xai') returns this hardcoded value, so the provider's default model will remain grok-4.3 rather than the newly flagged flagship. If the intent is to make grok-4.5 the default, this field should be updated to match.

Reviews (1): Last reviewed commit: "feat(providers): add xAI grok-4.5 model" | Re-trigger Greptile

Comment thread apps/sim/providers/models.ts Outdated
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