Grok Build is open source

skp1995 367 points 398 comments July 15, 2026
github.com · View on Hacker News

Discussion Highlights (18 comments)

loufe

I wonder if releasing this may have been on the roadmap, but been prioritized as a bit of whiplash following the "you forfeit the entirety of your working directory as a condition of working with this tool" upset from a few days ago.

petesergeant

Neat, trying to reverse engineer some specifics of how it does stuff has been a pain in the ass, and this will make it easier.

arcanemachiner

I'll probably never use this, but at least they're not delusional enough to attempt to justify keeping their coding agent closed-source, especially after their recent data-harvesting cockup: https://cereblab.com/

simianwords

Sigh, why has the industry converged on TUI? Branding and aesthetics over functionality? TUI is just much worse for me. I tried Codex CLI vs Codex UI and Codex UI beats it at every level.

tommica

Interesting - seen some good experiencences in using grok by some devs, so maybe could be considered as an alternative to my beloved chinese models. Also, hard to give up on pi agent.

lifthrasiir

Is this the infamous "cloud upload" routine? I'm not sure it is indeed insidious, though it is of course possible that the code has been filtered out. https://github.com/xai-org/grok-build/blob/main/crates/codeg...

losvedir

But I thought just cutting and pasting your whole source code file into grok.com was the way to go? Better than a harness like Cursor. https://xcancel.com/elonmusk/status/1943178423947661609

ahmadyan

i think xai is now in pure damage control mode, after they caught exfiltrating data from users. - There is a huge difference between logging user queries (which would include only the portion the model is reading) and exfiltrating user data (including env files, entire source code etc) which is what grok-build did here ( https://github.com/xai-org/grok-build/blob/main/crates/codeg... ). I would stay away from this open-source malware with a 10ft pole. - if you like grok-4.5 model (it is a good model), i suggest use the model directly via API, or use Grok's oauth tokens if you are using supergrok+heavy subscriptions and connect it to your own agent.

kamikazechaser

It's a shame that they exfiled private data. The model is actually good (better than opus 4.8 imo) and the harness itself is butter smooth with the potential of being the best out there.

maxloh

Has anyone tried building from source? The commit message says "initial sync from the monorepo." Is this even compilable without the rest of the source code?

GodelNumbering

This is not the right thing, this is the tactical thing. If you have an LLM with less than 1% of the share to begin with, you suffer from bad rep and you got caught uploading user data, one of the very few remaining tactical moves to try to climb out of it is this.

buremba

I would recommend using https://pi.dev/ over Grok Build with your xAI subscription at this point

charcircuit

It's awesome to see openness in these coding agents from the labs making the agents: Codex, Kimi Code, and now Grok Build.

cherryteastain

Why bother with this when they already paid $60B for Cursor?

ninjagoo

They claim to have deleted or will be deleting all the data they exfiltrated. There are independent agencies that will certify destruction of data. For example FTI Tech, Kroll, Epiq, HaystackID and others. No such certificates have been presented. Nothing less is trustworthy.

nickreese

This is 100% smoke and mirrors. Prove the bucket is empty and nothing was transferred out and I'll believe they deleted it.

gidellav

What a bunch of slop: 182 top-level external dependencies (so, without considering nested dependencies) and 1318853 lines of code in Rust. Building efficient agents is doable (I did it myself, github.com/gi-dellav/zerostack), companies just want to tokenmaxx, and as a by-product, produce and publish slop.

phillipcarter

This is an incredible amount of code for what it offers. I don't think this was intentionally designed at all.

Semantic search powered by Rivestack pgvector
14,015 stories · 131,331 chunks indexed