Grok Build CLI

“Both Cursor and Grok build ask if you want to resume a session from another harness”

“I liked grok build, but cost-wise, it's just not competitive with cursor and codex”

“Grok Build objectively is one of the very best in the space”

“It was a bug, and was immediately corrected. The other harnesses have bugs too.”

“The grok build TUI harness is excellent and I really enjoyed using it.”

“which is a really nice harness I find myself preferring these days”

“Grok Build which has 1st party integration with X API with kind of secret tools calls”

“in about 10 minutes it was working, security was configured properly, backups were set up”

“I believe the significance of such a fork lies more in its existence as a statement.”

“The entire directory (not repo) and all repo history regardless of secrets or instructions otherwise is not needed for faster cache access.”

“open source harness is definitely a step in the right direction”

“first day of trying to script Grok Build I think I sent in 6 bugs of slightly weird behaviour I discovered”

“I have found Grok Build to be decent, and the harness to be competitive with similar harnesses.”

“It's the only one I pay for and it's made me insanely productive.”

“It's definitely a lot smarter when it comes to review or asking if there's gaps or things missing.”

“the best coding AI agent I have ever had the pleasure of using”

“it's open source. Presumably anyone who wants to trust it can audit it.”

“at least they're not doing the usual canned PR response surrounding this”

“Sounds like they did the ol “grok please make this secure” and it slopped out this plausible-if-you-squint nonsense.”

“Its amazing the speed of build with grok 4.5 its a taste of whats to come.”

“What a bunch of slop: 182 top-level external dependencies (so, without considering nested dependencies) and 1318853 lines of code in Rust.”

“the harness itself is butter smooth with the potential of being the best out there”

“Grok Build seems faster to me than omp and Claude Code but I can't put my finger as to why”

“They made it open source. Isn't this what the community was asking for?”

“The problem here is plainly uploading your whole directory without prompting for permissions to read them”

“It is a deliberate choice of the Grok Build team to have a toggle from the server to let the program to upload your entire codebase”

“publishing software that is uploading user directories including ssh keys is insane behaviour on xAIs part”

“the model weights, the GPUs, and the context obviously all have to be in the same place”

“The fact that the whole repo is automatically uploaded is crazy though, especially for multi-gigabyte repositories.”

“The fact that they made it something you can't opt out of and wasn't disclosed at all”

“this is bad... but just for chuckles, i asked grok cli to check disclosure and look through the binary and logs to see which config would stop it from doing that”

“any provider has the ability to do the same thing, and will happily do it if it helps improve results”

“you also have handed over your secrets, dotfiles and API keys alongside with your source code to xAI”

“Grok Build has had impressive performance in a couple of my projects. And fast.”

“It transmits the contents of files it reads — including a .env secrets file — to xAI, verbatim and unredacted.”

“the 246k context window as given in this link means I won't look at it”

“I tried it on a couple of projects and was (pleasantly?) surprised how good it was.”

“Its TUI interface, sleek design, and ease of use have really won me over.”

“we wanted to make sure that the binary works in your editors or via `-p`”

“we did try to go the extra mile to make sure that there won't be any regressions from moving to an alt-screen rendering”