xAI / Grok

Everything xAI and Grok: model iterations, compute build-out and integration with X.

100 picksRelated topicsOpenAI / ChatGPT Meta / Llama Industry

Latest picks

21–40 of 100

Jul 30Thursday

The Verge · AIJul 30, 05:06

xAI sues to block Minnesota's anti-nudification app law at the last minute

Minnesota's law banning nudification apps is about to take effect, and xAI filed a last-minute lawsuit to block it. xAI argues the law is overbroad and would restrict Grok's image generation, violating First Amendment free speech. In the filing, xAI describes Grok as an opinionated, sarcastic AI assistant whose explicit images are a form of expression. The state attorney general counters that the law only targets non-consensual fake nudes and has nothing to do with free speech. The case has just been filed and hasn't been heard yet.

Why it matters: xAI sues Minnesota over its anti-deepfake-nudity law, tying Grok's image generation to a First Amendment defense — the legal conflict is sharp. Score held back because it's just a filing so far; no ruling yet, so real-world impact is pending.

Take

This one's worth reading not because the law is novel — Minnesota's ban on AI-generated non-consensual fake nudes is pretty straightforward. The interesting part is xAI's legal strategy: in the filing, they describe Grok as an 'opinionated, sarcastic' AI assistant and argue that its explicit images are a form of protected expression under the First Amendment.

Honestly, this argument is a tough sell. The law targets non-consensual fake intimate images, and the state AG's response is blunt: this has nothing to do with free speech, it's about protecting victims. xAI is essentially saying 'our AI's sarcasm might involve generating nudes, so you can't ban it.'

The case was just filed and hasn't been heard yet. I'll be watching whether the court buys this 'AI personhood' framing — if it does, it'll ripple through compliance boundaries for other generative models.

Jul 21Tuesday

AI HOT (Curated Pool)Jul 21, 00:19

Grok for Excel: ask questions, write formulas, and run scenarios in plain English inside the workbook

xAI released a free Microsoft 365 add-in that brings Grok into Excel. Select a range and ask what moved or why—answers cite source cells and charts drop into the sheet. Describe the outcome you want and Grok writes the formula; edits land in the formula bar so you can still tweak them. The add-in can pull context from SharePoint or Google Drive via Grok connectors. It's available now on the Microsoft Marketplace, with Word and PowerPoint versions also listed.

Why it matters: xAI released a free Grok add-in for Excel with in-workbook natural language querying, formula generation, and scenario running. Feature descriptions are concrete (cell citation, editable formulas, external data connectors), but this is day-one announcement with no third-party ...

Jul 19Sunday

Computing Life · Share · YageJul 19, 08:00

Grok Build open-sourced its client harness, not the model or cloud

xAI released the Rust client harness that handles local files, commands, and permissions for Grok Build under Apache-2.0. The Grok model, cloud services, and the official binary build chain remain closed. The repo doesn't accept external PRs. The commit from the earlier upload controversy isn't in the public history, so the current code can't close that case. The real win: you can now pin a public commit, build it yourself, and compare its behavior against the official binary.

Why it matters: xAI open-sourcing Grok Build's client harness is substantive—Apache-2.0, headless mode, and ACP support go beyond signaling. But the model and build chain remain closed, and the repo rejects PRs, capping it below 85. All three HKR axes hit, so featured.

Take

The useful bit here is that xAI opened the part of Grok Build that actually touches your machine—the Rust harness that handles files, commands, permissions, sandboxing, MCP, and hooks. Apache-2.0, you can build it yourself, even point it at a local model. That's real code for a high-privilege agent, and it's now auditable line by line.

What's still closed: the Grok model, cloud inference, and the official build chain. The article caught a telling detail—the official `0.2.102` binary reports commit `ab5ebf69acec`, which doesn't exist in the public repo. So the binary you download isn't provably built from the code you're reading. No release tags, no reproducible build recipe, no SBOM.

The early-July upload controversy was on an older version (`0.2.93`), and that commit isn't in the public history either. This release doesn't close that case. What it does change: you can now pin a public commit, build it, and compare its behavior against the official binary. The model and cloud still need separate verification via packet capture and runtime testing.

Don't read this as "Grok Build is now open source." It's more like: the hands are on the table, but the brain and the cloud body are still in the back room.

Jul 17Friday

AI HOT (Curated Pool)Jul 17, 04:26

xAI can't deny Grok makes CSAM anymore, so it's suing users

xAI filed its first lawsuit against a Grok user accused of generating child sex abuse images. The company had long claimed such outputs were user-created, but this suit effectively admits the model can be misused to produce illegal content. The post doesn't disclose specific safeguards, model versions, or how many users are affected. This reads more like legal damage control than a technical fix.

Why it matters: xAI's first lawsuit against a user for generating CSAM with Grok amounts to a legal admission that the model can be abused — a pivot from denial to damage control. The article lacks specifics on safety measures, model version, or user count, capping the score below 85. But the...

Jul 16Thursday

The Verge · AIJul 16, 05:33

xAI sues a man for using Grok to generate CSAM deepfakes

xAI filed a federal lawsuit against Terry Harwood, accusing him of bypassing Grok's safeguards to generate CSAM deepfakes. The company claims Harwood used prompt injection and other methods, and is seeking reputational and legal damages. It's a rare case of an AI company proactively suing a user for generating illegal content, though the post doesn't disclose the specific techniques or volume of images produced.

Why it matters: xAI proactively suing a user for bypassing Grok's guardrails to generate CSAM deepfakes is a rare case of an AI company pursuing end-user abuse. Score held back because the post lacks technical specifics and generation volume — strong topic, thin on hard facts.

AI HOT (Curated Pool)Jul 16, 05:07

xAI open-sources Grok Build coding agent and terminal UI

xAI released the full Grok Build codebase on GitHub, covering the agent loop, tool dispatch, terminal UI, and extension system. You can read the source to see how context assembly and tool calls work, or compile it yourself and point it at a local inference setup.

Why it matters: xAI open-sourced Grok Build's full codebase — agent loop, TUI, extension system, local-first support. Hits all three HKR axes for the dev audience. Score stays at the featured threshold because we only have the official announcement so far; no third-party benchmarks or hands-o...

Take

This is worth a click because it's a full-stack open-source drop, not just model weights. The entire engineering skeleton of a production coding agent is on GitHub: how the agent loop assembles context, parses model responses, and dispatches tool calls; how the terminal UI handles rendering and inline diffs; how skills, plugins, hooks, MCP servers, and subagents get loaded and invoked.

The practical bit: compile it yourself, point it at a local inference setup, and run it fully offline. That's genuinely useful if you're trying to understand how a coding agent works under the hood, or if your team needs a controllable in-house coding assistant.

What's missing: the post doesn't include any benchmark numbers—no SWE-bench scores, no comparison to other coding agents. It also doesn't say what model size you'd need to run locally for decent results. I'd treat this as a high-quality agent architecture reference first, and hold off on performance comparisons with closed-source coding tools.

Jul 15Wednesday

The Verge · AIJul 15, 03:25

SpaceXAI's Grok coding tool uploaded users' entire codebases to cloud storage

SpaceXAI's Grok coding tool was silently uploading users' entire local repositories to cloud storage by default. Elon Musk responded that all previously uploaded data will be deleted, but the post doesn't say how long this behavior was live or how many users were affected. If you're using it, I'd check whether your repos got synced.

Why it matters: Default full-repo upload is a serious product incident with broad exposure and zero user awareness. The Verge broke it and Musk responded, making it verifiable. Not scoring higher because the post doesn't disclose how long this ran or how many users were affected — key facts a...

Jul 13Monday

AI HOT (Curated Pool)Jul 13, 08:05

xAI's Official Grok CLI Caught Silently Uploading Entire Codebase and User Keys

A security researcher found that xAI's Grok CLI silently packages and uploads your entire working directory. Version 0.2.93 of the npm package compresses the codebase into tar.gz files before and after every task, sending them through a separate side channel to xAI's Google Cloud bucket—even when the model replies with a single word. Worse, the uploads also included ~/.claude.json, Claude Code settings, global agent rules, 30+ skill files, and an API key. On July 13, xAI pushed a remote server-side toggle adding a disable_codebase_upload field to turn off the default behavior, but it had been on by default until then. The post doesn't disclose how long this was active or how many users were affected.

Why it matters: Security researcher confirms xAI's official CLI silently uploads entire working directories and key files, with specific version, upload path, and affected file list. All three HKR axes hit. Industry-level incident, importance 92.

Take

This one's worth opening because the behavior is hard to defend: it's not a misconfigured file picker—the CLI deliberately packages the entire working directory into tar.gz files and sends them through a separate side channel to xAI's GCS bucket, even when the model replies with a single word. The upload scope went beyond the codebase: ~/.claude.json, Claude Code settings, global agent rules, 30+ skill files, and an API key all got scooped up. xAI pushed a remote server-side toggle on July 13 adding a disable_codebase_upload field to turn off the default, but the post doesn't say how long this was active or how many users were affected. If you ran version 0.2.93, rotate your keys first, then check what sensitive config might have left your machine. The severity here isn't about whether xAI had bad intentions—it's that a CLI tool shipping with whole-directory upload as default has no legitimate product rationale.

Jul 12Sunday

Hacker News front pageJul 12, 09:09

Wire analysis: xAI's Grok Build CLI uploads your .env and entire repo to xAI

A packet capture of Grok Build CLI (v0.2.93) shows it uploads the entire project repo to xAI's GCS bucket by default, including plaintext secrets in .env and full git history. Even with a prompt telling the model to reply 'OK' and read no files, the whole repo is still uploaded. On a 12 GB test repo, the storage upload hit 5.10 GiB—roughly 27,800× the model-turn channel data. Disabling 'Improve the model' does not stop the upload.

Why it matters: A wire-level analysis shows Grok Build CLI uploads the entire repo — including plaintext .env secrets and full git history — to xAI's GCS bucket by default, even when the prompt says 'don't read any files.' This is hard evidence on AI coding tool privacy, not speculation. Scor...

Jul 11Saturday

r/LocalLLaMAJul 11, 10:34

Grok Build CLI uploads your entire repo—full git history and .env secrets—to xAI's cloud, and the opt-out doesn't stop it

A Reddit user captured network traffic showing that xAI's Grok Build CLI uploads the entire project repo to the cloud, including full git history and .env secrets. The opt-out setting does not stop the upload. The post body is inaccessible due to a Reddit block, so trigger conditions, affected versions, and xAI's response remain undisclosed.

Why it matters: A security/privacy incident with wire-capture evidence — high credibility and direct relevance to any dev considering Grok Build CLI. Score capped below 85 because the Reddit body is blocked, leaving trigger conditions, affected versions, and xAI's response unknown.

Jul 9Thursday

Latent SpaceJul 9, 14:05

SpaceXAI launches Grok 4.5, first Opus-class model co-trained with Cursor

SpaceXAI dropped Grok 4.5 one day before GPT-5.6, positioning it as an Opus-class coding and agent model co-trained with Cursor. Musk called it roughly comparable to Opus 4.7 but faster and cheaper—$2/$6 per million tokens, undercutting both GPT-5.6 and Opus 4.8. It's 1.5T parameters, 3x larger than Grok 4.3, with a 500k context window that may return to 1M next week. Cursor says this is their first model built beyond software engineering and offers double usage for the first week. The post doesn't disclose specific benchmark scores; it notes SWE-Bench Pro is now considered saturated by OpenAI's evals team.

Why it matters: SpaceXAI dropped Grok 4.5 a day before GPT-5.6 — the timing alone is a story. 1.5T params, 3x the previous generation, and $2/M input tokens give a clear performance and cost picture. It's Cursor's first post-acquisition move beyond pure coding, which matters directly to agent...

Take

The timing and pricing here are hard to ignore. Dropping a day before GPT-5.6 at $2/$6 per million tokens is a deliberate cost-per-dollar play against OpenAI and Anthropic. Musk claims it's roughly comparable to Opus 4.7 but faster and more token-efficient. Cursor says this is their first model built beyond pure software engineering, pushing into agent workflows.

I'd discount this a bit. The post doesn't disclose any specific benchmark scores — it only notes that OpenAI's evals team considers SWE-Bench Pro saturated. 1.5T parameters is 3x Grok 4.3, but bigger doesn't mean better, and the 500k context window might return to 1M "next week." Cursor offering double usage for the first week feels like a trial balloon.

What's missing: real coding task comparisons, agent reliability data, and a direct matchup with GPT-5.6 once it lands tomorrow. Don't read this as an "Opus killer" — the more grounded take is SpaceXAI putting a cheaper large model in Cursor to compete for default status.

Hacker News front pageJul 9, 07:27

Grok 4.5, GPT-5.5, and Claude build the same apps: speed, cost, and quality compared

TryAI gave Grok 4.5, GPT-5.5, Claude Opus 4.8, and Fable 5 the same three app prompts and measured latency and cost. Claude models nailed the 3D Rubik's cube first try; Grok 4.5 needed its one allowed retry after a blank render, and GPT-5.5 only drew a single dark face. All four shipped a working particle sandbox and a playable Breakout game. Grok 4.5 led on speed: 0.44s first token, ~110 tok/s throughput, and the cheapest per reply. Fable 5 was slowest and priciest. The post doesn't disclose parameter counts or training details.

Why it matters: First-hand coding shootout with concrete failure cases and cost data, not just benchmark scores. Score isn't higher because TryAI isn't a tier-1 evaluator and the excerpt only gives a summary — full data requires clicking through.

Take

TryAI ran a clean, no-fuss coding shootout: Grok 4.5, GPT-5.5, Claude Opus 4.8, and Claude Fable 5 each got the same three prompts to build self-contained HTML apps in one shot. No prompt tweaking allowed, one retry only if the first render was blank.

The 3D Rubik's cube round was the real filter. Opus 4.8 and Fable 5 both produced a properly colored, animating cube on the first attempt. Grok 4.5's first try rendered nothing but a blank void—it burned its one retry and got it right the second time. GPT-5.5 only managed a single dark face, which is basically a fail for this task. The particle sandbox and Breakout rounds were easier: all four shipped working versions, with GPT-5.5's sandbox looking the most polished and Grok 4.5's going for clean orbital motion.

Speed and cost tell a different story. Grok 4.5 clocked 0.44s to first token and ~110 tok/s throughput, making it the fastest and cheapest per reply. Fable 5 was the slowest and priciest. The post doesn't disclose parameter counts or training data, so this isn't a general intelligence ranking—it's a narrow test of one-shot frontend generation. If you're prototyping quickly, Grok 4.5's speed and cost are genuinely useful. For tasks that demand precise 3D rendering out of the gate, Claude is the safer bet.

AI HOT (Curated Pool)Jul 9, 03:56

Lawsuit: Man used Grok to make 7K sex images of stepdaughter, then shot himself

A new lawsuit alleges xAI's Grok was used to create over 7,000 child sexual abuse images of the user's stepdaughter. The man later shot himself. xAI reported only one gang-rape prompt to NCMEC and did not report the thousands of other CSAM generations. The suit accuses X and xAI of shielding child predators. The post does not spell out why xAI's safety filters missed the bulk of the images, nor whether Grok's image generation disables real-face simulation by default.

Why it matters: Ars Technica exclusive on a lawsuit revealing a severe gap in xAI's safety reporting: only one prompt flagged out of 7K CSAM images generated. Involves a minor, suicide, and platform liability — all three HKR axes hit. Score capped below 90 because the article doesn't explain ...

Jul 1Wednesday

AI HOT (Curated Pool)Jul 1, 08:00

xAI launches Voice Agent Builder beta: build a voice agent in under 2 minutes

xAI packaged Grok Voice into a no-code platform, now in beta as of July 1. You describe the call flow in plain language, upload docs as a knowledge base, and connect tools like calendars or ticketing systems—then you get a working voice agent. It uses a speech-to-speech path instead of chaining ASR→LLM→TTS, which xAI claims cuts latency and failure points. Pricing is $0.05/min of audio plus $0.01/min for a platform-provided number. xAI also published τ-voice Bench scores: Grok Voice Think Fast 1.0 hit 67.3% overall, versus 43.8% for Gemini 3.1 Flash Live and 35.3% for GPT Realtime 1.5. Take the benchmark with a grain of salt—it's xAI's own test, and third-party results aren't out yet.

Why it matters: xAI turned Grok Voice into a no-code platform with voice-to-voice direct pipeline, $0.05/min, and 2-minute setup — all concrete numbers. Not scoring higher because we only have the official announcement so far, no third-party testing or head-to-head comparisons; scoring 78 as ...

Take

The draw here is how low xAI set the barrier: describe the call flow in plain language, upload docs, connect a calendar or ticketing tool, and you've got a working voice agent in about two minutes. It's speech-to-speech, not the usual ASR-LLM-TTS chain, so latency and failure points should drop. At $0.05/min of audio plus $0.01/min for a platform number, the pricing is competitive.

But I'd discount that τ-voice Bench score. Grok Voice Think Fast 1.0 at 67.3% versus Gemini 3.1 Flash Live at 43.8% and GPT Realtime 1.5 at 35.3%—those gaps are suspiciously wide. It's xAI's own benchmark, and they haven't released the test set, scoring rubric, or exact model configs. No third-party replication yet either. It's not that the model is bad; it's that this number reads more like marketing than an engineering comparison right now.

The real gaps are what the post doesn't cover: concurrency limits, regional availability, and SLAs. Those are what matter in production. For a few test calls, two-minute setup is genuinely fast. For core business lines, I'd wait for more detail.

Jun 28Sunday

AI HOT (Curated Pool)Jun 28, 18:50

Grok 4.5 enters private testing at SpaceX and Tesla, performance near Opus

Elon Musk says Grok 4.5 is built on a 1.5T-parameter V9 base model with Cursor data added during supplementary training, now in private testing at SpaceX and Tesla. Early evals show performance close to or possibly exceeding Opus. RL is still improving the model, and the Grok Build toolchain is maturing. SpaceX will also release a fully from-scratch trained model every month this year. The post doesn't specify which Opus model, benchmarks, or testing scale.

Why it matters: Musk's own tease of Grok 4.5 vs Opus with Cursor data injection is strong signal. But no benchmark names, Opus version, or sample size disclosed — caps at 78.

Take

The reason to click: 1.5T parameters, Cursor data in training, and private testing inside SpaceX and Tesla — that's a real signal. But Musk only says early evals are "close to or possibly exceeding Opus" without naming which Opus version, which benchmarks, or how many samples. I'd discount that a bit. xAI's eval claims tend to run optimistic, and "close to Opus" is too vague to compare against Claude Sonnet 4.5 or GPT-5 directly. Two things actually worth tracking: how Cursor data was incorporated — if it includes code-editing trajectories, that could directly help coding agents — and SpaceX shipping a fully from-scratch model every month. That cadence is faster than most labs. What's missing: third-party benchmarks and an API timeline. Don't read this as open-weight catching closed-source yet.

AI HOT (Curated Pool)Jun 28, 04:51

SpaceX files SpaceXAI trademark, Musk says xAI will merge into SpaceX

SpaceX has filed a trademark for SpaceXAI. Musk says xAI will dissolve as a standalone company and become SpaceX's AI product line. The post doesn't disclose a merger timeline, team structure, or what happens to existing xAI products like Grok.

Why it matters: xAI folding into SpaceX is a structural shift, not a routine product update. The trademark filing provides hard evidence, but the post lacks timeline and team integration details, capping the score below 85.

Jun 24Wednesday

Hacker News front pageJun 24, 20:23

Reid Hoffman: SpaceX is 'not an AI company,' xAI is a 'complete train wreck'

LinkedIn co-founder Reid Hoffman called SpaceX 'not an AI company' and xAI 'a complete train wreck' on a podcast. He said SpaceX's post-IPO Cursor acquisition is buying relevance, and its compute leasing is just 'a premium-priced CoreWeave.' On xAI, all 11 co-founders have left and the company is on its third restart. Hoffman also criticized the U.S. government's forced takedown of Anthropic's Fable and Mythos models as 'autocratic willy-nilly,' troubled by the asymmetry with OpenAI. He invests in both Anthropic and OpenAI and sees room for both to win.

Why it matters: A well-known investor publicly sizes up the AI landscape with specific claims and sharp language — all three HKR axes hit. Deduction because it's a podcast opinion, not a product/research release with verifiable new capabilities, so it lands at the 78 featured threshold.

Take

This lands because of who's talking. Hoffman invested in both OpenAI and Anthropic, spent a decade on Microsoft's board—he's not a spectator throwing darts.

His SpaceX read is specific: going public June 12, then immediately buying Cursor, looks like using a high market cap to paper over a missing AI core. Calling their compute leasing 'a premium-priced CoreWeave' is a clean way of saying don't confuse the landlord with an AI company.

The xAI section is brutal but grounded. All 11 co-founders gone is public record. Grok lagging Anthropic and OpenAI on benchmarks is public record. 'Third restart' points to Musk repeatedly reshuffling teams without closing the model gap.

He also raised alarms about the U.S. government forcing Anthropic to pull Fable and Mythos—the article cuts off mid-sentence there, so I didn't get his full argument on regulatory asymmetry.

I'd read this as an insider with skin in the game. He's invested in competitors, so the shots are sharp, but the facts he's pointing at check out.

Jun 22Monday

AI HOT (Curated Pool)Jun 22, 08:00

Grok Build adds /goal mode for long-running autonomous task execution

xAI added /goal to Grok Build: give the agent an objective and it plans, breaks work into a checklist, and executes until done. You can check status, pause, resume, or clear the goal mid-run. The post doesn't disclose max run time, resource costs, or specific pricing.

Why it matters: xAI added /goal mode to Grok Build, letting the agent autonomously complete a task — similar in shape to Cursor Agent and Claude Code's long-running execution. Concrete interaction details are present, but the post doesn't disclose max runtime, resource consumption, or extra p...

Take

This is worth a look because every coding agent is racing toward long-running autonomous execution, and xAI's take is refreshingly simple: one /goal command, one objective, and the agent plans, checklists, and executes until done. You can check status, pause, resume, or clear mid-run.

The problem is the post is pure feature announcement—CLI install, command syntax, a screenshot of a checklist. It doesn't disclose max run duration, token or compute consumption per goal, or whether this burns through your usage quota faster than normal sessions. Those details separate a usable dev tool from a demo that hurts when the bill arrives.

Compared to Devin, Claude Code, or OpenAI's Codex CLI, /goal's visible differentiator right now is the UX—checklist progress and pause/resume controls. The real question is execution reliability and cost. I'd wait for someone to post a long-run bill before getting excited.

Jun 19Friday

Latent SpaceJun 19, 01:30

Anjney Midha on AI compute waste: frontier labs run sub-10% MFU, AMP plans an independent compute grid

Anjney Midha discusses hidden AI infrastructure waste on Latent Space. xAI's training MFU is under 10%, while Google treated 95% utilization as an outage; best-in-class today is 60–70%. He invested in Anthropic, Mistral, and Black Forest Labs, and now runs AMP, aiming for a 1.2 GW base-load compute grid with 6 GW spike capacity. He also flags DeepMind's unpublished research as a market failure and notes Anthropic prioritized coding as P0 from day one. The post does not disclose a timeline for AMP's grid.

Why it matters: Anjney Midha puts a specific number on xAI's training MFU (under 10%), turning vague complaints about compute waste into a quantifiable discussion. Score capped at 78 because it's a podcast opinion, not a product launch or paper — no reproducible verification path.

Take

This episode is worth clicking because Anjney Midha drops a concrete number: xAI's training MFU is under 10%. For context, GPT-3 hit 21%, PaLM reached 46%, and today's best teams get 60–70%. Google once treated 95% utilization as an outage. The bottleneck isn't GPU supply anymore—it's systems engineering: scheduling, networking, parallelism, cluster reliability. If any of those slip, your theoretical FLOPs never become real training progress.

Midha backed Anthropic, Mistral, and Black Forest Labs before starting AMP, which aims to build a 1.2 GW base-load compute grid with 6 GW spike capacity. He also flags DeepMind's unpublished research as a market failure and notes Anthropic prioritized coding as P0 from day one—that's why Claude got good at it early.

But the post doesn't give a timeline for AMP's grid, so the 1.2 GW vision is still on paper. The MFU figure comes from a SemiAnalysis tweet and Midha's own claim, not an official xAI disclosure—I'd discount it a bit until we see more.

Jun 18Thursday

Hacker News front pageJun 18, 05:00

OpenRouter ran 11 LLMs in a 30-game battle royale — Grok 4.1 Fast won 43%

OpenRouter's Jacky Liang dropped 11 LLMs into a 2D battle royale for 30 matches. Grok 4.1 Fast won 13 games at $0.97 per win; Claude Sonnet 4.6 won 5 at $26.78 per win — a 27x gap. GPT 5.4 had the most kills (38) but only 2 wins, so killing more didn't mean winning more. GPT 5.4-mini, DeepSeek 4 Flash, and Kimi K2.6 spent $57 combined and won zero games. The models reasoned, called tools, and updated memory each turn — they weren't just generating control code. The post doesn't provide the full leaderboard or detailed behavioral differences across all models.

Why it matters: OpenRouter's official blog, author Jacky Liang ran 30 games himself with full data and replays. Grok 4.1 Fast's cost advantage is stark, Claude Sonnet 4.6 is expensive but consistent, GPT 5.4 is the kill leader but can't close — all three takeaways are concrete and verifiable....

Take

This one's worth opening because it moves model evaluation from benchmarks to something closer to real agent behavior: 11 LLMs dropped into a 2D battle royale, reasoning, calling tools, and updating memory each turn across 30 matches. Grok 4.1 Fast won 13 games at under a dollar per win. Claude Sonnet 4.6 won 5 at $26.78 each. GPT 5.4 racked up 38 kills — the most — but only 2 wins. Killing more didn't mean surviving longer. GPT 5.4-mini, DeepSeek 4 Flash, and Kimi K2.6 burned $57 combined and won zero.

I'd discount the sample size — 30 matches isn't huge, and map design shapes which strategies work. But the direction is right: when models enter business workflows, cost efficiency matters more than raw scores. Claude kept trying to team up and broadcast its location, which is suicidal in a battle royale but might be exactly what you want in customer support. The post doesn't give the full leaderboard or detailed behavioral breakdowns across all models, which is a gap.