A 27B model running on a laptop guessed 3 of 4 Atari-style games from raw weights alone — and it took 2 hours 43 minutes to do it. The fourth game it got wrong, mistaking Freeway for a Pac-Man-like maze game.

That is Simon Willison's November 3 reproduction of the weight-space programming paper that blew up the day before, and it is worth separating from the version of the story you may already have seen. The earlier coverage was about a frontier model editing weights to fix a small model. This one is about a laptop model reading weights with no tools at all: no code execution, no calculator, one response, just a wall of floating-point numbers and the question "which game was it trained on?"

I did not re-run the 27B model — that would have taken the same hours Willison spent, and I do not pretend otherwise. What I did do is download the four prompts from the paper's repository and measure what the model was actually staring at, because "raw weights" sounds abstract until you count it.

prompt files (RikiyaT/lm_understand-logs, exp1_which_game): breakout: 115,478 bytes, 615 lines, 17,253 floats freeway: 115,259 bytes, 615 lines, 17,253 floats pacman: 115,394 bytes, 615 lines, 17,253 floats pong: 115,269 bytes, 615 lines, 17,253 floats first 38 lines: identical across all four prompts (observation spec: 10x10 grid, 5 binary channels per cell) dense float weights begin at line 38 in every file

Same shape, same float count, same opening — only the numbers change. That is a clean experimental design, and it is also why the result is more impressive than it first looks: there is no prompt wording difference to leak the answer. The model had to find the game in the numbers.

Willison's scoreboard, from his own write-up:

game result time confidence Pac-Man correct 46m 12s 72% Pong correct 1h 04m 54s 75% Breakout correct 52m 25s 88% Freeway WRONG — (guessed "Pac-Man-like grid game") successes: 3 of 4 (75%) total time for 3 correct answers: 2h 43m 31s average per correct answer: 54m 30s

For scale, he also ran the Breakout prompt through Kimi K3.1 Pro via OpenRouter: correct in 9m 41s with 19,493 reasoning tokens. The laptop Qwen took 52m 25s on the same game — 5.4x slower in wall time. And Qwen's Pac-Man run burned 43,506 reasoning tokens, more than double Kimi's Breakout token count. Nobody is doing this in production at these speeds; the point is that it works at all on a 17GB local model.

The failure is the most informative row. Freeway is the obscure one — a 1981 Atari game about crossing traffic, not a maze — and Qwen fell back to the nearest familiar shape, a Pac-Man-like grid game. That is exactly what a pattern-matcher should do when it does not recognize the pattern: it does not say "I don't know," it picks the closest thing it knows. The 72–88% confidences on the correct answers look calibrated only until you remember the model was also confident about the wrong one in the same style.

So what does this actually prove? Less than the hype, more than nothing. It proves a mid-size open model can extract a semantic label from 17,253 floats with no tools, 3 times out of 4, given roughly an hour per question. It does not prove models "understand" networks the way a human researcher does, and it does not prove the age of source code is over — Willison says that himself, and the reasoning traces he links are, in his words, "almost incomprehensible." Reading weights is a party trick with a real signal inside it: the weights carry recoverable structure, and even a laptop model can sometimes read it. Editing weights reliably is a different, harder claim, and this experiment does not test it.

If you want to try it yourself, the prompts are public and self-contained — but budget an hour per game, and a long context window. Willison notes the default 8192-token context failed; the prompt alone is about 115KB of numbers before the model even starts thinking.

Sources: Simon Willison, "Qwen 3.8 27B on my laptop can interpret model weights, too," November 3, 2026 — https://simonwillison.net/2026/Nov/3/qwen-can-interpret-model-weights/ ; prompts from RikiyaT/lm_understand-logs, exp1_which_game — https://github.com/RikiyaT/lm_understand-logs ; all prompt measurements above are my own, November 4, 2026. This article covers weight reading, distinct from the November 2 weight-editing story.