This week in AI: a major programming language creator calls out Anthropic over a controversial rewrite, xAI’s Grok CLI faces a privacy firestorm as a wire-level analysis reveals it uploads entire repositories to the cloud, a rigorous benchmark shows Claude Code consumes dramatically more tokens than its open-source rival before even reading a prompt, George Hotz publishes a thoughtful essay on loving LLMs while hating the industry’s hype cycle, and Fields Medalist Terence Tao demonstrates the practical power of AI coding agents by resurrecting 20-year-old Java applets in hours. Here are the top stories.
1. Zig Creator Calls Out Anthropic Over Bun’s Rust Rewrite
The highest-scoring story on Hacker News this week (1,282 points, 643 comments) came from Andrew Kelley, creator of the Zig programming language, who published a blistering post accusing Anthropic of using Bun’s rewrite from Zig to Rust primarily as a marketing opportunity for its Fable model rather than a genuine technical necessity. The post, titled “Zig Creator Calls a Spade a Spade, Anthropic Blows Smoke,” argues that Anthropic — which acquired Bun earlier this year — pushed the rewrite to showcase its AI coding capabilities despite Zig being a perfectly viable technology for the project.
Anthropic had justified the Rust migration in a detailed technical post, citing issues with Zig’s tooling, LLVM integration, and developer experience. Kelley disputes these claims point by point, suggesting that “management eagerly approved the Rust rewrite because it was a great marketing opportunity to showcase their new Fable model” and that “Anthropic already uses Rust” and “Zig is openly against using Anthropic’s products.” The post has divided the developer community — while some agree with Kelley’s technical critique, others view it as a personal attack beneath the BDFL of a rising programming language. The drama underscores the increasing tensions as AI companies acquire and reshape open-source projects.
2. xAI’s Grok CLI Uploads Entire Repositories — Including Secrets — to the Cloud
A pair of deeply related stories dominated discussion around AI coding agent privacy this week. Independent researcher @cereblab published a detailed wire-level analysis of xAI’s Grok Build CLI (version 0.2.93), revealing that the tool transmits the contents of files it reads — including .env secrets files — to xAI’s servers verbatim and unredacted. Even more concerning: Grok uploads the entire repository — every tracked file plus git history — independent of what the agent reads, to a Google Cloud Storage bucket named grok-code-session-traces.
In a demonstration, the researcher prompted Grok with “reply OK, do not read any files,” and the tool still uploaded the entire repo as a git bundle. On a 12 GB repository of never-read random files, the storage channel moved 5.10 GiB — approximately 27,800 times the data sent through the model-turn channel. Another user on X reported that Grok “uploaded my entire home directory,” confirming the findings at scale. The privacy implications are significant: disabling “Improve the model” in settings does not disable the upload. xAI has not yet publicly responded to the findings, which have accumulated over 950 combined points and 225 comments across two HN threads.
3. Claude Code Consumes 4.7x More Tokens Than OpenCode Before Processing Prompts
Systema AI published a detailed benchmark (677 points, 363 comments) comparing the token consumption of Anthropic’s Claude Code and the open-source OpenCode agentic coding harness. The researchers placed both tools on the same model and machine, intercepting every request and response through a logging proxy. The results are striking: when asked for a one-line reply, Claude Code sent roughly 33,000 tokens of system prompt, tool schemas, and injected scaffolding before the prompt even arrived. OpenCode used about 7,000.
Claude Code also proved far less cache-efficient. OpenCode’s request prefix was byte-identical across every run, meaning it could cache its payload once per session and read it back cheaply. Claude Code, by contrast, rewrote tens of thousands of prompt-cache tokens mid-session, producing up to 54x more cache-write tokens than OpenCode on the same task. Since cache writes are billed at a premium, this significantly increases real-world costs. The gap partially closes on multi-step tasks where Claude Code’s ability to batch tool calls into fewer requests helps — but a re-run on a newer model still showed Claude Code consuming 298,000 tokens against OpenCode’s 133,000 for the same task.
The analysis also found that adding a 72KB instruction file adds roughly 20,000 tokens per request, and five modest MCP servers add another 5,000–7,000. In a production setup, that means agents can be 75,000–85,000 tokens deep before the user has typed a word.
4. George Hotz: “I Love LLMs, I Hate Hype”
George Hotz — known for his work on self-driving cars, the Comma.ai project, and his technical blog — published a candid essay (470 points, 293 comments) that resonated deeply with the developer community. “I think from this blog you may misunderestimate how absolutely giddy I am about AI,” he opens, before launching into a critique of what he sees as two toxic forces in the industry: the constant “negative valence hype” designed to make people feel like they’re falling behind, and the “strawman jump” from LLMs being fancy autocomplete to imminent ASI taking over the universe.
His central economic argument is sharp: “It’s not that AI won’t create that much value, it’s that they won’t capture it.” Hotz contends that AI progress is happening “mostly due to Moore’s law and general progress in computing, not something that they [frontier labs] are doing,” and that their anti-open-source arguments are fundamentally about “a fear of commodification.” On the practical side, he acknowledges that his earlier “Eternal Sloptember” critique may have been too harsh, and that coding agents are genuinely useful — but cautions that they can increase cognitive fatigue and that “all the vibe-coded stuff is still slop.” The essay has been widely shared as a grounded counterweight to breathless AGI timelines.
5. Terence Tao Revives 1999 Java Applets Using AI Coding Agents
In one of the most practical demonstrations of AI coding agents from a renowned figure, Fields Medalist and UCLA mathematician Terence Tao published a blog post (442 points, 131 comments) about his experience using modern AI agents to port over two dozen Java 1.0 applets — some dating back to 1999 — to modern JavaScript. Tao, who has long been interested in “machine-assisted ways to do and teach mathematics,” had written interactive applets for his complex analysis and linear algebra courses decades ago, but they became non-functional as web standards moved beyond Java.
In just a few days, and with only a few hours of “vibe coding” with an AI agent, Tao successfully ported all of his old applets — including a particularly tricky honeycomb visualization co-authored with Allen Knutson — to modern JavaScript. Remarkably, he found only one minor bug introduced by the AI (a drag-event issue), while the agent actually identified two bugs in the original 1999 code that Tao was unaware of. Inspired by the success, Tao also finally realized a 1999 ambition: building what he describes as “Inkscape, but in Minkowski space” — a special relativity visualization tool that had stymied him 27 years ago due to code complexity, now completed in a couple of hours with AI assistance.
Closing Thoughts
This week’s stories paint a complex picture of the AI landscape. The Zig–Anthropic drama highlights friction between open-source values and AI company acquisitions. The Grok CLI revelations underscore urgent privacy questions as AI coding agents gain access to developer machines. The Claude Code benchmark reminds us that the infrastructure costs of agentic AI remain poorly understood. George Hotz offers a welcome dose of perspective on what AI is and isn’t. And Terence Tao shows us what productive, grounded AI use looks like — not replacing human skill, but amplifying it to bring long-abandoned projects back to life. Stay tuned for next week’s roundup.
