Quake SRP Forbids Unsafe Rust and Credits Claude for the Code

Quake SRP, a port of id Software's 1996 shooter to Rust that runs in a browser tab, forbids unsafe code in every crate, according to its README. The same README says "Claude (Anthropic's model) wrote the code and docs in Claude Code," with a human setting the rules, playing the game and reporting bugs.

The project page calls it Quake "ported to Rust from its GPL source and software-rendered in your browser," with no GPU and no dependencies. A Show HN post reached 207 points.

What the README promises

The README lists three rules: zero dependencies, no unsafe, and the "Classic" preset must match id's game. It says #![forbid(unsafe_code)] is set on every crate and binary, including the browser build, and that the port uses only the standard library.

Claim	What the README says	Limit
No unsafe code	forbid(unsafe_code) on every crate and binary	Compiler-enforced, says nothing about idiom
Matches id's game	Pixel-by-pixel comparison against id's WinQuake C source, built headless	"Not one pixel may differ" applies to the Classic preset on an SSE2 floating-point build
Default build	x87 floating point	"Differs on scattered single pixels"
Dependencies	Standard library only	No crate list given

That second row is the sentence worth reading twice. The repository's oracle/classic_check.py runs ten checks and is meant to print "ALL PASS," and its exact check compares the 3-D view pixel by pixel across many views. The guarantee holds for one preset on one floating-point mode, and the README says so itself.

How it was built

The README describes most of the work as running in parallel agents, each on its own git branch, with a "chair" agent that merged a branch only after the full check passed. The repository shows 1,035 commits on main, 49 stars and 2 forks. It is licensed GPL-2.0-or-later, matching the source it derives from.

On Hacker News, a commenter named airesQ, who replied as the author, called the project a hobby that took about four months and said it was "made by AI with human assistance." Another commenter, flohofwoe, wrote that all commits in the project are from Claude. The README's own account is consistent with that, though the page does not name the human.

Where the argument is

The thread did not dispute the pixel check. aroman praised the harness. The dispute was over what "safe" buys. dwroberts wrote that equating safe Rust with no unsafe is shallow, since code can avoid the keyword and still be non-idiomatic or sidestep the borrow checker. flohofwoe argued that the original C compiled to WebAssembly is "just as 'safe'" in a browser, and jagged-chisel answered a joking question about safety by saying the browser sandbox is the layer that matters.

Neither side produced an unsafe count, because there is nothing to count: the compiler refuses to build one. What the thread did not settle is whether a line-for-line translation, checked against the C original, is better software or only a different language.

What it costs a player in friction

The shareware episode is bundled from id's original 9.1 MB quake106.zip. Episodes two to four need your own id1/pak1.pak, mission packs need their own pak0.pak files, and the page says files you add "stay in this browser."

The page lists its own rough edges. On a Mac, a gaming mouse starts slow because macOS passes along only part of its movement. F12 screenshots reach the game only in fullscreen. Switching mission packs ends an unsaved game, and a browser sees a gamepad only after a button is pressed. A commenter, furoTmark, wrote that multiplayer does not work.

The same shape of project has appeared here before: a PSP game recompiled to run in a browser, and a browser engine generated from specs whose own completion figure was 0.6 percent. Quake SRP is the one that publishes a test it can fail.

A commenter, rvz, predicted the repository would be abandoned within a month. The repository's commit history will answer that by early November.