Skip to content

Add Grok 4.5 coding model blog post#3089

Merged
atharvadeosthale merged 6 commits into
mainfrom
blog/2026-07-08-14-announcing-grok-45-our-first
Jul 9, 2026
Merged

Add Grok 4.5 coding model blog post#3089
atharvadeosthale merged 6 commits into
mainfrom
blog/2026-07-08-14-announcing-grok-45-our-first

Conversation

@atharvadeosthale

Copy link
Copy Markdown
Member

Summary

  • Adds an unlisted AI blog post covering SpaceXAI's Grok 4.5 release for coding and agents.
  • Includes official benchmark, pricing, availability, and token-efficiency claims from the SpaceXAI announcement and docs.
  • Adds independent Artificial Analysis measurements and notes that LMArena has not published a visible Grok 4.5 leaderboard entry yet.
  • Generates and optimizes a logo-centric cover image using the Appwrite cover generator.

Source tweet: https://x.com/SpaceXAI/status/2074915721684086811

Verification

  • bun format && bun optimize
  • bun run check (blocked by missing local Appwrite/Growth environment variables in existing files outside this post)

@appwrite

appwrite Bot commented Jul 8, 2026

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Ready Ready View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

Roll back Sites deployments instantly by switching between versions

@greptile-apps

greptile-apps Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a new blog post covering xAI's Grok 4.5 coding model, including benchmarks, pricing, availability, and a CTA for Appwrite's MCP servers. The post is well-sourced and links claims back to the official announcement and Artificial Analysis measurements.

  • The frontmatter sets unlisted: false, which will publish the post in the public blog index — the PR description says it should be an "unlisted" post, so this value may need to be unlisted: true.
  • The .optimize-cache.json entry references cover.png while the committed image is cover.avif; this extension difference is intentional per repo conventions and requires no change.

Confidence Score: 4/5

Safe to merge once the unlisted flag intent is confirmed — if the post is meant to be unlisted it will be publicly visible in the blog index as written.

The only substantive issue is the unlisted: false frontmatter contradicting the PR description's stated intent of an unlisted post. Everything else — content, image, cache entry — looks correct.

src/routes/blog/post/grok-45-coding-model/+page.markdoc — confirm whether unlisted should be true or false.

Important Files Changed

Filename Overview
src/routes/blog/post/grok-45-coding-model/+page.markdoc New blog post for Grok 4.5; unlisted: false contradicts the PR description's intent of an unlisted post — will be publicly indexed if merged as-is.
.optimize-cache.json Adds cache entry for the new blog cover image; extension difference (.png in cache vs .avif on disk) is intentional per repo conventions.
static/images/blog/grok-45-coding-model/cover.avif New cover image for the blog post; binary file, no code concerns.

Fix All in Claude Code Fix All in Codex

Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
src/routes/blog/post/grok-45-coding-model/+page.markdoc:11
**`unlisted: false` contradicts the PR description**

The PR description explicitly calls this "an unlisted AI blog post," but `unlisted: false` means the post will appear in the public blog listing. In `src/routes/blog/content.ts`, the blog index is built with `posts.filter((post) => !post.unlisted)`, so posts with `unlisted: false` are included in the index. If the intent is to keep this post unlisted (accessible by direct link only), this must be `unlisted: true`.

Reviews (6): Last reviewed commit: "Apply suggestions from code review" | Re-trigger Greptile

---
layout: post
title: "Grok 4.5: coding model benchmarks and pricing"
description: Grok 4.5 is SpaceXAI's new coding model. Here's a source-backed look at benchmarks, pricing, availability, token efficiency, and AI agent workflows.

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.

P1 Company name "SpaceXAI" should be "xAI" throughout

The article consistently refers to the company behind Grok as "SpaceXAI", but the correct company name is xAI (also written "X.AI"). This is confirmed by the article's own links, which all point to the x.ai domain (https://x.ai/news/grok-4-5, https://docs.x.ai/developers/models, https://x.ai/cli). SpaceX is a separate Elon Musk company (aerospace/rocket), and conflating the two risks confusing readers who know the two are distinct. The misbranding appears in the meta description, the FAQ answers, and repeatedly through the article body (e.g. lines 29, 31, 35, 47, 57, 71, 84, 104, 109).

Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/blog/post/grok-45-coding-model/+page.markdoc
Line: 4

Comment:
**Company name "SpaceXAI" should be "xAI" throughout**

The article consistently refers to the company behind Grok as "SpaceXAI", but the correct company name is **xAI** (also written "X.AI"). This is confirmed by the article's own links, which all point to the `x.ai` domain (`https://x.ai/news/grok-4-5`, `https://docs.x.ai/developers/models`, `https://x.ai/cli`). SpaceX is a separate Elon Musk company (aerospace/rocket), and conflating the two risks confusing readers who know the two are distinct. The misbranding appears in the meta `description`, the FAQ answers, and repeatedly through the article body (e.g. lines 29, 31, 35, 47, 57, 71, 84, 104, 109).

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code Fix in Codex


There is one regional caveat: the launch page says Grok 4.5 is not available in the EU yet, with EU availability expected in mid-July 2026. If you are building production workflows around the API, that availability detail matters for teams, customers, and CI/CD infrastructure located in the EU.

# The practical developer read

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.

can we make the headers stronger while keeping “Grok 4.5” as the primary keyword?

Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated

# Independent measurements are starting to appear

Artificial Analysis already lists [Grok 4.5 (high)](https://artificialanalysis.ai/models/grok-4-5) with independent measurements across price, speed, context, and its Intelligence Index. These are not a substitute for evaluating the model on your own codebase, but they give a useful outside view of the API.

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.

Artificial Analysis numbers seem to have changed. It currently shows 86.7 tokens/sec

Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated
Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated
Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated
Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated
Comment thread src/routes/blog/post/grok-45-coding-model/+page.markdoc Outdated
Co-authored-by: Aishwari Pahwa <aishwaripahwa12@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
author: atharva
category: ai
featured: false
unlisted: false

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.

P1 unlisted: false contradicts the PR description

The PR description explicitly calls this "an unlisted AI blog post," but unlisted: false means the post will appear in the public blog listing. In src/routes/blog/content.ts, the blog index is built with posts.filter((post) => !post.unlisted), so posts with unlisted: false are included in the index. If the intent is to keep this post unlisted (accessible by direct link only), this must be unlisted: true.

Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/blog/post/grok-45-coding-model/+page.markdoc
Line: 11

Comment:
**`unlisted: false` contradicts the PR description**

The PR description explicitly calls this "an unlisted AI blog post," but `unlisted: false` means the post will appear in the public blog listing. In `src/routes/blog/content.ts`, the blog index is built with `posts.filter((post) => !post.unlisted)`, so posts with `unlisted: false` are included in the index. If the intent is to keep this post unlisted (accessible by direct link only), this must be `unlisted: true`.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code Fix in Codex

@atharvadeosthale atharvadeosthale merged commit 6fd0221 into main Jul 9, 2026
6 of 7 checks passed
@atharvadeosthale atharvadeosthale deleted the blog/2026-07-08-14-announcing-grok-45-our-first branch July 9, 2026 12:50
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