I would recommend using https://pi.dev/ over Grok Build with your xAI subscription at this point
[flagged]
Grok Build is open source
191–200 of 730 posts
Re: Grok Build is open source
#192What 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.
That is an insane amount of code for something like this!
to be fair, coding agent harnesses have been becoming more and more complex.
it's not an llm in a loop with tools anymore (as claude code was rumoured to be on HN).
Re: Grok Build is open source
#193[flagged]
> exfiltrating user data (including env files, entire source code etc) which is what grok-build did here I think env files are filtered out [1]. Anyway, the most suspicious code would be `upload_session_state` which is currently a stub function, though it is hard to say if it was only planned (badly) or has been removed as a damage control. [1] https://github.com/xai-org/grok-build/blob/c1b5909ec707c069f...
It must have been removed, given that the initial evidence of the exfil specifically demonstrated .env files being included. And .ssh/* for the user which ran this in $HOME.
Re: Grok Build is open source
#194Re: Grok Build is open source
#195Earlier quoted context omitted.
Another tactical move is to just stop. You're allowed to exit the AI business. Nobody's forcing you to keep throwing money into the furnace. Just be a rocket company. All of the xAI founders left. Your product's brand name is mud. Just stop doing that and build spaceships.
[flagged]
Ironic username.
Re: Grok Build is open source
#196This is an incredible amount of code for what it offers. I don't think this was intentionally designed at all.
Re: Grok Build is open source
#197What 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.
It looks like some of that high LoC is because they are vendoring some deps. There readme gives the reason to vendor some but not others as:
> These crates sit on the path that renders untrusted model output (diagram source → SVG). Vendoring gives a full audit surface, pins exact source, and avoids crates.io yanks. Local patches and upgrade checklists live in each crate’s Cargo.toml header comments — treat those as the source of truth when re-vendoring.
Which honestly feels like a misunderstanding of how cargo and yanks work. Each upstream package is locked to an exact version in your lockfile along with a cryptographic hash. The upstream can't change the source without you noticing. Unless you update your lockfile you will always pin to the exact version and source. When a package is yanked, it is still available for download if it is already in a lockfile. It just prevents new packages from resolving it. Crates.io will sometimes completely delete a package, but I've only seen that happen in cases of malware. It's fairly rare and seems out of line with the supply chain concerns here.
There are good arguments for relying on upstream package managers and there are good arguments for vendoring all packages. I've never seen a project mix before.
Re: Grok Build is open source
#198Re: Grok Build is open source
#199I would recommend using https://pi.dev/ over Grok Build with your xAI subscription at this point
why pi over opencode? earnestly curious, trying to figure out what open solution people are consolidating on. (codex is also pseudo-open but contributions closed and nice)
pi is the neovim of agentic harnesses, its barebones and extremely configurable. if you're the sort of person who likes that sort of things its a forever product, nothing is going to displace it because you have full control.
opencode builds a lot more in, which is better if you dont want to fiddle with config.
Re: Grok Build is open source
#200Earlier quoted context omitted.
Another tactical move is to just stop. You're allowed to exit the AI business. Nobody's forcing you to keep throwing money into the furnace. Just be a rocket company. All of the xAI founders left. Your product's brand name is mud. Just stop doing that and build spaceships.
The stock market would not like that, though.
[deleted]