# Epic vibe codes its launcher, Anthropic merges 30,000 a day, and Postgres 19 reverts 8 to 10 features

> Vibe coding news, Oct 13 to 19, 2026: Epic's vibe-coded launcher, 30,000 merges a day at Anthropic, Postgres 19 reverts, 511 GB of Codex crash dumps.

- URL: https://acceptallhq.com/log/2026-10-19-epic-launcher-30000-merges-postgres-reverts/
- Section: Vibe Log
- Published: 2026-10-19T06:04:00-04:00
- Author: MK (https://acceptallhq.com/about/)

**TL;DR:** Epic rebuilt its game launcher by vibe coding, said so in the announcement, and spent the rest of the week being benchmarked against Steam. Anthropic published three posts that add up to one fact: the machines read the diff now, and the humans are the part the agents wait for. Meta and Reflection put two very large open-weight models on Hugging Face while open weights crossed seven in ten tokens on Vercel's gateway. Four Gemini agents beat Minecraft. Postgres 19 reverted 8 to 10 features because LLM-assisted review found bugs faster than anyone could fix them, Codex Desktop filled a Mac with 511 GB of crash dumps, OpenCode told users to rotate their provider keys, and a Swedish TV season vanished with two explanations. Sources linked on every item.

## What shipped

### Epic vibe coded its launcher and said so on the box

Epic released a preview of a rebuilt Epic Games Launcher on October 14 and led the announcement with the one quote in this post: "Programming is hard." So instead, the post says, they vibe coded a new launcher that is faster and more responsive, with a new look. It calls the first release light on features and asks you to think of it as a speedboat rather than a yacht. The number attached is a 5.47 second average cold start, which Epic calls 46% faster than Steam. The store's general manager told IGN it was rebuilt from the ground up.

Valve shipped a client update with faster startup in the same window, and the internet did what it does. RespawnFirst measured Steam at about 5.23 seconds after the update against Epic's 5.47, on unnamed test systems, with no methodology, and the Hacker News thread about it reached 347 points and 359 comments, mostly people posting their own stopwatch results. Kotaku rounded up day-one complaints, including one user who switched Fortnite to DX12 and got the Unreal Editor for Fortnite instead. Epic's preview page says, as all betas do, that there could be issues.

This is the most mainstream vibe coding story so far: a company with Fortnite's install base marketing the method as the feature, and the method's reputation getting tested in public by anyone with a stopwatch. The launcher may well end up faster. The lesson of the week is that if you say the quiet part in the press release, the benchmarks arrive the same afternoon.

Sources: [VGC: Epic says it vibe coded its new launcher](https://www.videogameschronicle.com/news/epic-says-its-vibe-coded-its-new-epic-games-launcher-with-ai-because-programming-is-hard/), [RespawnFirst: Steam is now faster than Epic's vibe coded launcher](https://respawnfirst.com/steam-client-is-now-faster-than-epics-new-vibe-coded-launcher/), [Hacker News thread](https://news.ycombinator.com/item?id=50105635), [Kotaku on the day-one reaction](https://kotaku.com/epic-dunks-on-steam-with-vibe-coded-storefront-and-gets-roasted-this-launcher-is-so-fucking-vibeslopped-its-funny-2000746031)

### The machines read now: 30,000 merges a day, 90% of Claude Code, 80% waiting

Anthropic published three posts this week that belong together. On October 13 its source control team explained why it replaced git for its monorepo. Merges went from about 2,500 a day in May to over 30,000 a day in September, main-branch history is almost 100 GB, and CI alone does on the order of 25 million checkouts a day. Nearly every client is an always-online agent, so a team of seven built **Scion**, a server-side system where the server owns history, merges and rebases and clients keep a bounded cache, plus a review tool called Antique, and migrated in five months. The post says Scion is not a general replacement for git.

On October 15 the Claude Code team described how it reviews code when Claude writes about 90% of Claude Code. Every PR gets parallel bug-hunting agents whose findings are voted on by verifier agents, then a separate security review, before any human looks. A classifier sets a risk tier: low-risk changes such as docs and flagged additive code need no human approval once checks are green, medium needs one person, high needs two. From June to September merged PRs more than doubled and the share needing a revert fell by more than 40%. Substantive review comments went from 16% to 54% of PRs, the mean number of review rounds to pass fell from 2.08 to 1.32, and one CLI PR went through more than fifty review-and-fix rounds overnight before its author stopped it. The reviewer now asks the author to step back after three rounds. An agent's approval, the post says, never fills a slot reserved for a person.

Then the economics team's October 16 report on employment inside Anthropic supplied the ratio. In March 2026 agent work hours passed human work hours for the first time. By August interactive agent hours outnumbered employee hours six to one, counting employees at 40 hours a week. And Claude sessions spend around 80% of their wall-clock time idle, waiting for human input. Coding-focused sessions by non-technical employees went from 2 a month in August 2025 to 90 in May 2026. The report flags its own limits: adoption wasn't random, quality metrics are proxies, and Anthropic is one unusual company.

A footnote from the other side of the keyboard: a Show HN on October 18 called **Sphinx** is an MIT-licensed git hook that pauses a push to a protected branch while a separate reviewer model, which never saw your agent chat, quizzes you on what the diff does when things go wrong. Wrong answer, new scenario. A pass lasts 24 hours. The escape hatch is a command called yolo, and every use of it is logged. The machines read the diff. Now one of them wants to check that you did.

Sources: [Anthropic: redesigning source control](https://www.anthropic.com/engineering/redesigning-source-control), [How the Claude Code team does code review](https://claude.dev/blog/solving-code-review-at-anthropic/), [Anthropic: how employment is changing at Anthropic](https://www.anthropic.com/research/employment-at-anthropic), [Sphinx on GitHub](https://github.com/parthh01/sphinx)

### Open weights week: Muse Spark Open, Beam, and seven in ten tokens

Meta released **Muse Spark Open** on October 15: 816 billion total parameters, 42 billion active, 256 experts with 8 active per token, a 1M-token context, natively multimodal, weights on Hugging Face. Meta's pitch is that it runs on your desktop, where your desktop is two Apple M5 Ultra Mac Studios with 512 GB of unified memory each, linked and driven by MLX. The Muse Model License asks for a Built with Muse Spark Open notice in your product and requires anyone offering the model as a service past $20 million in 12-month revenue to sign a separate agreement. Coding is where the model card is modest: Terminal-Bench 2.1 at 76.4 against Kimi K3's 85.0 and GLM 5.3's 83.9, and DeepSWE 1.1 at 60 against 68 and 67.

Reflection shipped **Beam** on October 16, its first open-weight model: 501 billion total parameters, 23 billion active, Apache 2.0, with BF16, FP8 and NVFP4 weights and a speculative-decoding drafter on Hugging Face. Meta's own comparison table puts Beam at 80.1 on Terminal-Bench 2.1, ahead of Muse Spark Open, and 44 on DeepSWE 1.1, behind it.

The demand side arrived the same week. Vercel's AI Gateway Production Index for October, covering traffic through September, says open-weight models now process more than seven in ten gateway tokens and take nearly one in four gateway dollars, up from one in twenty dollars in June. DeepSeek-V4.1-Flash alone handled nearly half of September's tokens for 2.6% of the spend. Two US labs released weights the week the meter said open weights are where the tokens go. That is not a coincidence, and it is not a loss for anyone who buys tokens.

Sources: [Meta: Muse Spark Open](https://research.meta.ai/blog/muse-spark-open), [Muse Spark Open model card](https://huggingface.co/meta-models/Muse-Spark-Open-816B-A42B), [Reflection: Beam is available](https://reflection.ai/blog/beam-is-available), [Vercel AI Gateway Production Index, October 2026](https://vercel.com/blog/ai-gateway-production-index-october-2026)

### Gemini 4 Argon goes GA, four of them beat Minecraft, and Opus 5.5 gets fast mode for real

Google made **Gemini 4 Argon** generally available on October 13 at $2 per million input tokens and $10 output through November 30, after which the price doubles to $4 and $20. We covered the details, including the ignored sampling parameters and the caching rules, in [the Diff](/diff/2026-10-13-gemini-4-argon-ga/).

Two days later a paper by Maxence Faldor, Satinder Singh and Roberta Raileanu reported that four Gemini 4 Argon agents beat Minecraft end to end. Each agent controlled a player through the open-source Mineflayer library, with no pre-scouted seed, no human-written game tools and no assigned roles, coordinating only through in-game chat and a shared memory. From the first program to the Ender Dragon's defeat took 27 hours and 14 minutes, during which the team wrote 2,783 programs, exchanged 229 messages and died 605 times. A fifth agent watched and never played. The authors call it the first autonomous completion of the game by AI agents and argue it is a long-horizon coding result dressed as a game.

Also on October 15, Anthropic took fast mode for **Claude Opus 5.5** out of research preview: no access request, no beta header, a default rate limit in the Start, Build and Scale tiers, at $8 per million input tokens and $40 output for up to 2.5x the output speed. Fast mode for Opus 5 and 4.8 still needs the header. That one is in [the Diff](/diff/2026-10-16-claude-opus-5-5-fast-mode-ga/) too.

Sources: [Gemini API changelog](https://ai.google.dev/gemini-api/docs/changelog), [arXiv: A team of Gemini 4 Argon agents beats Minecraft](https://arxiv.org/abs/2610.22319), [Claude API release notes](https://platform.claude.com/docs/en/release-notes/overview)

## What broke

### Postgres 19 reverts 8 to 10 features, and review finds a race in Linus's first LLM-assisted patches

PostgreSQL committer Peter Eisentraut wrote on October 9 that about 8 to 10 significant features, depending on how you count, were reverted from the Postgres 19 branch after beta began, some late in the cycle, when one revert per release would be normal. His explanation is the week's quietest big story: with LLM-assisted code review, the long tail of edge-case defects gets found much faster than before, so a committer ends up staring at a list of about forty reports, each small, each with a fixed cost to handle, and runs out of time. The reverted code was written before that kind of review was useful, so the quality bar moved after the features were committed. He adds that this is not vibe coding, since the code predates it, and that a security push from April to August took senior reviewers away from the beta.

The Register reported on October 16 that general availability has moved from late September or early October to around November 19, with SQL Property Graph Queries the best known of the features now pushed to Postgres 20. The Hacker News thread, at 219 points, split between people who think many of the findings are design trade-offs no model can patch and people who think the bugs were always there and the fuzzer finally showed up.

The same week, LWN reported that Linus Torvalds told the Maintainers Summit he had used a large language model on a patch series, now posted for review: ten patches that mark hot folios and delay their release past an RCU period so the read fast path needs no refcount, for an order-of-magnitude speedup on a read-heavy benchmark. LWN does not name the tool. Review has already found a race condition. So in one week, LLM review found bugs in human Postgres code and human review found a bug in LLM-assisted kernel code. Review is working. It is the thing it reviews that keeps having bugs.

Sources: [Peter Eisentraut: the reverts will continue until morale improves](https://peter.eisentraut.org/blog/2026/10/09/the-reverts-will-continue-until-morale-improves), [The Register: Postgres 19 delayed](https://www.theregister.com/databases/2026/10/16/postgres-19-delayed-after-ai-reviewers-find-more-bugs-than-humans-can-fix/5303471), [Hacker News thread](https://news.ycombinator.com/item?id=50119991), [LWN: Torvalds's LLM-assisted patch series](https://lwn.net/Articles/1100449/)

### Codex Desktop filled a Mac with 511 GB of crash dumps, one per second

Codex Desktop on macOS has a crash reporter problem. The helper process that is supposed to catch crashes crashes itself about a second after it starts, on a fatal check in its Mach exception server. The app restarts it, every crash writes a minidump to a pending folder, and because the helper never lives long enough to run its own pruning or upload anything, nothing ever leaves. Issue #25921 has been open since June 2, when the reporter found 4.9 GB and 54,504 files. Issue #47466, opened September 23, is titled after its 511 GB and roughly 3 million dump files. It reached the Hacker News front page on October 17, where the thread turned into a general swap meet about agents eating disks.

A maintainer closed #47466 on October 6, saying it seemed to affect older Mac kernels and that a fix had merged and would ship soon. No release or version is named there, Codex 0.163.0's October 15 notes do not mention it, and #25921 is still open. On October 17 a user there reported about 323 GB and about 4 million files across two Crashpad folders, with 1.4 GB left free. Reports cluster on macOS 15.x and 26.0 to 26.3, and some users on 26.5 and later say they are fine. The app, every report agrees, keeps working.

If you run Codex Desktop on a Mac, look at the Crashpad folders under Application Support for com.openai.codex and for Codex before you look at anything else. For once the agent did not delete your files. It made a few million new ones.

Sources: [openai/codex issue #47466](https://github.com/openai/codex/issues/47466), [openai/codex issue #25921](https://github.com/openai/codex/issues/25921), [Hacker News thread](https://news.ycombinator.com/item?id=50133231)

### OpenCode: provider keys may have been exposed, rotate them

OpenCode said on October 17 that it found unauthorized access to a legacy system it was in the process of decommissioning, and that third-party provider keys saved in a workspace, such as OpenAI and Anthropic keys, may have been exposed. The statement asks users to revoke and replace those keys in the provider's dashboard, update anything that uses them, review recent usage for activity they don't recognize, and watch for updates. It does not give a count of affected users or a root cause. Commenters in the Hacker News thread, which reached 953 points and 175 comments, identify the system as the hosted OpenCode Console, where bring-your-own keys are stored, rather than the CLI or desktop app, and some report keys revoked mid-session. The company has not confirmed those details.

There is no joke in this one. If you ever saved a provider key in OpenCode's hosted service, rotate it now and check the bill.

Sources: [OpenCode statement on X](https://x.com/opencode/status/2111516673953935833), [Hacker News thread](https://news.ycombinator.com/item?id=50133401)

### A TV season vanished, and there are two stories about why

Sweden's TV4 postponed the second season of its reality show The Challenge from a November 22 premiere to late spring 2027 after the edited episodes were lost. Aftonbladet reported, citing sources, that an AI agent with access to the production company's servers deleted the finished season, several hundred days of work. TV4's program director told Sveriges Radio that it is not true that some independent AI agent went in and deleted the material. TV4's account is that a backup system at the production company failed and the crew now has to edit everything from scratch.

Both versions share the part that matters to anyone running agents near production data. Whatever did the deleting, something had delete rights on the only copy, and the backup was not tested until it was needed. The Hacker News thread asked both questions in the first few comments. We are not picking a side on how the files went. We are noting that one of the two explanations is a story about agents, and nobody found it implausible.

Sources: [Sweden Herald: TV4 postpones The Challenge until 2027](https://swedenherald.com/article/tv4-postpones-the-challenge-until-2027-after-technical-failure-erases-edited-footage), [Hacker News thread](https://news.ycombinator.com/item?id=50085323)

## What it means if you build with an agent

**Review is the product now.** Anthropic's pipeline, Postgres's reverts and Linus's race condition say the same thing: writing got cheap, so finding defects is where the time goes. Put agents on the reading side too, and budget for the list they hand you.

**Tier your merges.** Docs, copy and flagged additive changes with green checks don't need your eyes. Caching, auth, updaters and prompts do. Write the tiers down before the agent files forty PRs, and never let an agent's approval count as a person's.

**Cap the loop.** One PR ran fifty review rounds overnight. If a reviewer agent and an author agent can talk to each other, give them a round limit and a rule to stop and ask a human after three.

**Check the disk.** A crash reporter can out-write an agent. Put a size alert on the folders your tools write to, not just the repo, and read the open issues for your desktop client once a month.

**Rotate anything you pasted into a hosted service.** Keys you saved in someone else's console are only as safe as their legacy systems. Keep separate keys per tool so one leak is one revoke.

**Test the restore, not the backup.** A season of television was lost either to an agent or to a backup that failed when asked. Both failures end the same way. Run a restore from your backups before an agent gets delete rights near them.

**Open weights are a budget line now.** Seven in ten gateway tokens, two new 500B-plus models with permissive licenses. Try one on your boring workloads this month and keep the frontier model for the hard 10%.

## One opinion

Our opinion: the 80% number is the week's real headline, and it is good news. Agents at Anthropic spend most of their session time waiting for a human to decide something, and that is what the whole stack now looks like: Scion merges intent, the reviewer agents read the lines, and the person in the loop is the slow, expensive, necessary part. Epic skipped the waiting and shipped. Postgres did the waiting and slipped to November. One of those will have fewer bugs in December, and we think everyone already knows which.
