2026-11-10 12:53 UTC

Qwenputer embeds a RISC-V CPU in Qwen; builder now claims an internal NPU runs a small LLM

state: significantheat: lowuncertainty: highrelevance: mediummodel-internal-computation open-models hardware-emulationdivagr

What is this?

Qwenputer is an experimental Qwen3.5-4B derivative by builder divagr (identified in secondary results as Divyansh Agrawal). The builder presents it as embedding a 32-bit RISC-V CPU in model weights, using Gated DeltaNet state as RAM; linked repositories, model weights and a demo are cited, and a separate Reddit post reports a slow Doom demonstration. On Nov. 1, a newer post quoting the builder’s X thread announced QwenPU: a neural processing unit compiled into Qwen’s weights to run the C program stories260k, with the builder claiming bit-exact matrix multiplication, softmax and attention and no external tools. The full write-up is still pending. The supplied evidence does not independently establish correctness, reliability or performance; much of the technical detail is in attributed claims, summaries and discussion.

Why it matters

The striking idea is to make a model’s recurrent state perform exact, structured computation rather than merely have the model describe or call an external computer. If dependable, this could enable unusual forms of self-contained computation and persistent state inside inference. For now, the demonstrations are experimental, and no evidence here shows an advantage over ordinary code execution or tool use. The newer QwenPU claim extends the idea from CPU emulation toward running a small neural network internally, but its account and optimizations remain forthcoming.

Current assessment

Qwenputer is a Qwen3.5-4B derivative presented by its builder as implementing a 32-bit RISC-V CPU and filesystem using model computation and state; a separate project reportedly ran Doom on its virtual machine, slowly. The builder later announced QwenPU, linking code and weights and claiming an NPU compiled into Qwen’s weights can run Karpathy’s stories260k program with bit-exact matrix multiplication, softmax and attention, without external tools. A separate post describes Qwen interpreting model weights, but it does not establish that Qwenputer or QwenPU works reliably. These remain experimental project claims; correctness, supported workloads, speed and practical advantage over ordinary execution remain open. The latest attention increase is on a distinct, adjacent post rather than new validation of this case.

Measured heat

now 0 pts/hpeak 308 pts/hcomments 0/hpeers p25momentum: steady3 platformsage 312h
points/hour across evidence · reading as of 2026-11-10 23:26:04.141941+11:00 · deterministic, not a model opinion

How the heat travelled

10-28 13:32 (minted)⭐ origin echo-reconstructedA write-up describes Qwenputer, a Qwen-derived model presented as implementing a 32-bit RISC-V CPU in its weights; the post also links a Hug
divagr on blog (echo) · attributed from reddit.post.1xhmo1q · published time unknown
—
10-28 12:26first on r/LocalLLaMA · published · lag ?Someone built a 32-bit RISC-V CPU directly inside Qwen's model weights so it can execute instructions internaly!
LatentSpacer
—
10-28 17:45first on hacker news · published · lag ?A RISC-V CPU compiled into the weights of an LLM
UncleOxidant
—
10-28 12:26amplified on r/LocalLLaMAreddit.post.1xhmo1q
LatentSpacer
peak 1035 · 149 comments · 25% of case engagement
10-28 17:45amplified on hacker newshn.story.50277757
UncleOxidant
peak 4 · 1 comments · 0% of case engagement
10-28 22:24amplified on r/LocalLLaMAreddit.post.1xi2jfm
mapestree
peak 86 · 10 comments · 2% of case engagement
10-29 00:25amplified on hacker newshn.story.50282838
csmantle
peak 708 · 143 comments · 30% of case engagement
10-30 04:58amplified on hacker newshn.story.50300006
titusblair
peak 2 · 0 comments · 0% of case engagement
10-31 19:18amplified on r/LocalLLaMAreddit.post.1xkiuut
LatentSpacer
peak 328 · 69 comments · 8% of case engagement
2 more amplifiers in ainews.case_chain
10-28 13:25our radar first saw it · lag ?discovery anchor: reddit.post.1xhmo1q—
10-28 18:34reached heat=high · lag ? · via ledger——
pace: p98 vs 1783 stories at the 168h mark (now 312h old) — ahead of swedish-agencies-block-chatgpt-claude (1.0x), behind claude-reverse-engineers-lg-webos-media-stack (1.0x)

Evidence (9) — ⭐ canonical anchor

sourceobjectauthorscorecomments
🟠 redditSomeone built a 32-bit RISC-V CPU directly inside Qwen's model weights so it can execute instructions internaly!
LocalLLaMA
LatentSpacer1035149
🟧 echo.blog ⭐A write-up describes Qwenputer, a Qwen-derived model presented as implementing a 32-bit RISC-V CPU in its weights; the post also links a Hugdivagr——
🟧 hnA RISC-V CPU compiled into the weights of an LLMUncleOxidant41
🟠 redditI ran Doom inside the Qwen model weights!
LocalLLaMA
mapestree869
🟧 hnQwenputer: A functioning, deterministic RISC-V CPU inside Qwen3.5csmantle708143
🟧 hnQwenputer turns Gated DeltaNet state into exact RAM for a CPUtitusblair20
🟠 redditAn LLM inside an LLM - Same guy who put a RISK-V CPU inside Qwen has now made Karpathy's stories260k run on an NPU compiled inside Qwen 3.5-4B's weights
LocalLLaMA
LatentSpacer32869
🟠 redditQwenBend : Qwen writes a Bend program, then the same model type checks it with Bend2 rules and runs it inside its own forward pass
LocalLLaMA
Affectionate_Hat_585284
🟧 hnQwen 3.8 27B on my laptop can interpret model weights, tootheanonymousone736209

Interpretation history

Decision trace