#065

Claude writes 80% of Anthropic's own code, Cloudflare buys Vite, ChatGPT ships Dreaming memory

Anthropic says Claude now writes 80%+ of the code in its own codebase, up from single digits 16 months ago. Cloudflare buys Vite. ChatGPT ships Dreaming.

Anthropic just put a number on it: more than 80% of the code merged into its own production codebase is now written by Claude. Sixteen months ago that figure sat in the low single digits. One engineer says they haven’t hand-written code in five months.

Then Anthropic did the rare thing and undercut its own headline. The “8x more code per engineer” stat in the same report? They call it “almost certainly an overstatement.” Claude’s code only hit human parity recently.

In today’s indie hacker news:

  • 🤖 Claude writes 80%+ of the code in Anthropic’s own codebase
  • ⚡ Cloudflare buys Evan You’s VoidZero, the Vite toolchain
  • 🧠 ChatGPT’s “Dreaming” memory upgrade reaches free users
  • 💸 A founder says Google Cloud nuked his ~$1M ARR app for 72h
  • 🐈 A reading app made $1K in a year, a desktop cat $150 in a day

TOP STORIES

THE BUILD TOOL GOT A LANDLORD

⚡ Cloudflare acquires VoidZero, the team behind Vite, Vitest, Rolldown and Oxc

Cloudflare acquires VoidZero, the team behind Vite

The story: Cloudflare announced on June 4 that it’s acquiring VoidZero, Evan You’s company behind Vite, Vitest, Rolldown and the Oxc toolchain. The whole team moves into Cloudflare’s incubation org. Evan keeps leading the projects, and they stay MIT-licensed and vendor-agnostic. Cloudflare also committed $1M to a fund for Vite maintainers that the core team runs on its own, independent of both companies. Evan was blunt about why: sponsorship money couldn’t fund a full-time core team for tooling with 100M+ weekly downloads.

The details:

  • Vite pulls 130M+ weekly downloads and sits under Vue, SvelteKit, Nuxt, Astro, Solid, Qwik, Angular and React Router.
  • Cloudflare wasn’t a stranger here. Its own @cloudflare/vite-plugin already does ~13.9M weekly downloads, north of 10% of Vite’s total.
  • VoidZero had raised $17.1M total, including a $12.5M Accel Series A in October 2025, less than a year before the deal.
  • Price and team size weren’t disclosed by anyone.
  • The HN thread (592 points) read the playbook out loud: npm went to GitHub, Turbopack and Svelte’s maintainers went to Vercel. Now Vite.

Why builders care: A vendor-agnostic pledge holds exactly as long as the MIT license, which says nothing about where the smoothest DX flows. If Vite’s best edge-deploy story quietly starts pointing at Workers, you get lock-in without a single license being broken. Pick your JS stack today, then watch the next 12 months: does “deploy anywhere” actually hold, or does the happy path keep bending toward Cloudflare?



IT REMEMBERS YOU NOW, FOR FREE

🧠 OpenAI ships “Dreaming,” its biggest ChatGPT memory upgrade, and it’s reaching free users

OpenAI ships Dreaming, its biggest ChatGPT memory upgrade

The story: OpenAI rolled out “Dreaming” on June 4. It’s a background memory system that synthesizes context from your past chats on its own, no “remember this” required. Between sessions it rolls up your preferences, constraints and ongoing projects into a memory page you can actually read and edit. Plus and Pro users in the US got it first. Free and Go users follow over the coming weeks.

The details:

  • OpenAI says it cut the compute to serve Dreaming by ~5x. That’s the lever that finally makes giving it away to hundreds of millions of people pencil out.
  • Paid users get double the memory storage as part of the rollout.
  • Controls ship with it: a readable summary page, manual add/edit/delete, per-topic instructions, and a toggle back to legacy saved memories (per Engadget).
  • OpenAI floated a recall-accuracy jump (82.8% vs 67.9% a year ago), but that’s its own benchmark, not independently checked. Treat it as a vendor claim.
  • No word on whether Dreaming-style synthesis is exposed through the API.

Why builders care: Persistent “it just knows me” memory was a paid edge that standalone memory startups have been charging for. It’s now the free-tier baseline. Two takeaways. Any assistant app without background cross-session memory will feel broken next to ChatGPT. But until OpenAI ships an API surface for this, app-level memory (your own threads, your own vector store) is still your job. The day that API drops is the day a lot of memory wrappers lose their reason to exist.


THE CODERS WHO STOPPED CODING

🤖 Anthropic says Claude now writes 80%+ of the code merged into its own codebase

Anthropic says Claude writes 80%+ of its own code

The story: The figure comes from a report Anthropic’s Institute published on June 4. What makes it worth reading isn’t the headline number, it’s that Anthropic spends most of the writeup poking holes in its own stats. They define the 80%+ narrowly (lines actually merged to production, not commits or PRs), flag every place the data flatters them, and cite outside research showing engineers tend to overrate their own gains. It reads less like a victory lap and more like a company nervous about being believed.

The details:

  • That 80%+ counts lines merged to production. A looser leadership estimate hits 90%+ once you fold in scripts and throwaway experiments.
  • Engineers merge ~8x more code per day than in 2024, but Anthropic itself waves that off, since counting lines rewards volume, not whether the code was any good.
  • Task scope went from ~4-minute jobs (Opus 3, March 2024) to ~12-hour jobs (Opus 4.6, March 2026), though the benchmark tasks aren’t defined.
  • A March survey of 130 researchers self-reported ~4x output, and Anthropic flags METR research showing devs overrate their own AI gains.
  • On quality: Claude’s code was “somewhat worse” than human in late 2025, is “roughly at parity” now, and Anthropic bets “strictly better within the year.” For context, GitHub pegged AI at 40%+ of new code in Copilot repos back in 2024.

Why builders care: Strip out the line-count inflation and the real signal still matters for solo founders. The leverage shows up as features you can ship without a hire, not literal 8x output. The first hire you can probably defer is a second backend engineer, since Claude Code now eats tasks that used to burn an engineer-day. The catch is in Anthropic’s own footnotes: quality only just hit parity, review burden scales with how much the AI generates, and one HN reviewer was staring down a 600-file, 40k-line AI PR. Use the leverage. Keep your hand on the review.


NVIDIA’s Nemotron 3 Ultra goes open - NVIDIA dropped a 550B / 55B-active MoE with a 1M-token context and a genuinely open license: weights, training data and recipes under OpenMDW-1.1. It’s the top-scoring US open model on the Artificial Analysis index (48), though it still trails China’s Kimi K2.6 (54). Catch for the local crowd: even a 4-bit quant needs an 8xH100 node, so it’s the smaller Nano and Super variants people will actually run, not Ultra.

🗜️ KV-cache quantization is the new local-LLM battleground - Huawei open-sourced KVarN (Apache 2.0), a vLLM backend that compresses the KV cache 3-5x at 2-bit while holding FP16-level reasoning accuracy. Prior 2-bit methods fell apart on reasoning tasks. The variance-normalization trick is the fix, and it turns on with a single flag, no calibration. Net effect: 3-5x more context or concurrent requests on the same VRAM, plus ~1.3x throughput. The paper claims SOTA at 2-bit on MATH500 and AIME24.

💸 Build-in-public revenue threads are flooding the feeds again - r/SaaS’s latest “what’s your MRR?” megathread is doing big numbers, mirrored by a wave of X revenue-milestone posts. It’s a monthly genre by now, and the numbers are self-reported with heavy survivorship bias, so read it as a mood check, not a leaderboard. The useful signal isn’t any one figure. It’s that public revenue has fully replaced “we raised a round” as the flex.


DRAMA

GOOGLE PULLED THE PLUG

💥 A founder says Google Cloud killed his ~$1M ARR app for 72 hours after a hacker abused Google’s own API design

A viral r/startups post from a founder claiming ~100k users, 1M+ stored photos and ~$1M ARR: Google Cloud suspended his whole project for ~72 hours, with no warning, after a hacker exploited an API. The specific numbers are self-reported and the post itself couldn’t be independently verified. The mechanism underneath it, though, is well documented. Google’s public-by-design Maps and Firebase keys (the AIZA-prefix ones) were silently enabled to reach paid Gemini endpoints without telling developers. Researchers found ~3,000 of them exposed in public apps. One leaked key racked up $15,400 in minutes. Railway, on ~$2M/mo of GCP spend, got suspended with no notice in May.

Why builders care: Following Google’s own docs is exactly what left people exposed, and when a third party abuses your key, Google’s automation can suspend the entire project, not just the key, with no committed review window. Audit every AIZA-prefix key in your client-side code and lock it down in the console today. Keep a cloud-agnostic backup of customer media (S3/R2) you can flip to. Set billing alerts at roughly 10 times your normal spend, since Google can auto-raise your cap. And past ~$50K ARR on GCP, get a named account contact, because self-serve accounts have no real escalation path when the hammer drops.


FIRST DOLLAR

THE CAT OUTEARNED THE APP

🐈 A reading app made ~$1K in a year. A “cute desktop cat” then made ~$150 in a day

Solo maker Simon spent three months building a reading-notes app that earned roughly $1,000 over a full year. Then he shipped a tiny desktop-cat app almost as a throwaway, and it made ~$150 in a single day. Both numbers are self-reported, but the lesson lands either way: the thing you sweat over for months and the thing you toss off in a weekend don’t always pay out the way your effort says they should. Attention is the asset. Sometimes a desktop cat just has more of it than your serious app.


STACK OF THE DAY

🎬 Reloops

A self-hosted, open-source take on Frame.io for client video review and approval, shipped after ~6 months of solo building. You get annotations, version comparison, AI tagging, approval workflows and Kanban, plus an agent API, all running on your own box via docker compose. Stack is React + Vite + Supabase. One footnote worth knowing: it’s AGPL-3.0, so it’s copyleft, not the permissive MIT you might assume. Early days at ~35 stars, but a real alternative if you’re tired of per-seat SaaS for client sign-off.

Not sponsored. We just feature tools builders would actually use.


BOOKMARKED TODAY

🐘 Multigres v0.1 Alpha - Supabase’s Vitess-style orchestration layer for Postgres hits its first alpha: HA failover, smart pooling and backup orchestration now. Sharding, the eventual flagship, is still to come. This v0.1 is single-shard.

🐧 Azure Linux 4.0 - Microsoft’s first general-purpose Linux. Versions 1.0 through 3.0 ran hidden under AKS. The 4.0 preview is deployable on any Azure VM, scale set or WSL, built on Fedora 43 with kernel 6.18.

📦 Boxes.dev - Run Claude Code and Codex on isolated cloud VMs instead of localhost, each agent thread in its own box with snapshot forking. Priced by box-hours, auto-suspends when the agent is done. Mac-only for now, and EU-restricted on GDPR grounds.



Curated by AI, built by a human. That’s the whole model.

How was today’s edition? Just hit reply, we read every one.

Subscribe to indiehacker.news · X (Twitter) · Telegram