#122

Fable-OS wrote its own sound driver, and Qwen3.8-Max opens at $2 per million input

A kernel with 0 lines of AC'97 code took one typed sentence and shipped a working driver, then published the miss: 1000 ms asked for, 251 ms delivered. Karpathy burned $10 and 2 hours trying to retire the pelican test.

Listen to this edition

A from-scratch x86_64 kernel shipped with 0 lines of AC’97 driver code. Someone typed one sentence at it. The model read the PCI config space, wrote the driver, installed it, and played a 440.4 Hz tone.

Then the README published what missed. The demo asked for 1000 ms of tone and got 251 ms, truncated by a 16 bit length field.

In today’s indie hacker news:

  • 🔊 A kernel wrote the driver it was missing
  • ⚙️ 66 stars, 10 followers, one parametric gearbox script
  • 🌳 A desktop AI that skips your pixels entirely
  • 💰 Alibaba lists 2.4T at $2 per million in
  • 🐦 Karpathy retires the pelican, HN wants the prompt
  • ✅ A language that proves your code is correct

TOP STORIES

SUDO MAKE ME A DRIVER

🔊 A one-person kernel hands a language model all 64 of its syscalls

A one-person kernel hands a language model all 64 of its syscalls

The story: Fable-OS is a from-scratch x86_64 kernel with no shell and no commands. You type a sentence, and the kernel sends it straight to Anthropic’s API from ring 0. It does its own DNS and TLS with lwIP and mbedTLS compiled in, and there is no host proxy. The model drives the machine through 64 registered tools.

The repo is 96% C, with 207 stars off 17 commits by a single contributor. The bare metal claim is where r/ClaudeAI split.

“Calling Fable-OS a ‘real OS’ is fair. Calling the current demo a proven physical-hardware operating system is not.” Yash Thakker, explainx.ai

The details:

  • The real ceiling: tool schemas cost 56,309 bytes per request against a 57,344 byte cap. Headroom is 1,035 bytes.
  • The 86 byte outage: one four-verb tool family pushed the registry past that cap. The kernel booted, talked, and offered the model nothing to act with.
  • The test evidence: 39 host suites and 9,598,786 assertions pass, and explainx.ai reran them on August 2.
  • Never on real silicon: AGENTS.md says the project has never booted on physical hardware. Everything is QEMU.
  • The gaps: no LICENSE file despite the open source label, and certificate checks are off by default.

Why builders care: The ceiling on this class of product is context economics, not model capability. Sending tool schemas once per conversation instead of once per round buys more product from the same model.

The README also deleted one of its own claims in public. An earlier version described a cleaner tone than any file in the repo could back up.

SHIP THE GENERATOR, NOT THE GEAR

⚙️ A gearbox repo out-starred its own author’s follower count

A gearbox repo out-starred its own author's follower count

The story: tom-ilan/cycloidal_gearbox is a 3D printed speed reducer, and the repo is listed as 100% Python. The part people came for is the generator. A Fusion 360 script takes pin count and pitch radius, then draws the whole rotor. Change N and R, and you get your own ratio.

The math is borrowed. The README credits a 2014 SOLIDWORKS post by Omar Younis, which credits an academic paper behind it. Twelve years later it is a printable part and a script anyone can fork.

“This gearbox was the first working version to run on a NEMA 17.” Tom Ilan, repo README

The details:

  • The measured win: 1.3 N.m out of the gearbox against the bare stepper’s 0.21 N.m, error bars included.
  • The failure in public: Version 2 was sized to a NEMA 17 footprint and did not work. Tight tolerances and print precision killed it, and the README says so.
  • The print spec: a 90 mm PLA housing with a +0.15 mm offset applied all round for print clearance.
  • Distribution beat audience: 66 stars against 10 followers and 3 public repos on the whole account.
  • The last file in: bom.csv landed on Aug 3, later than every other file in the repo.

Why builders care: The moat on a hobby build is forkability, not the part. That is the generator plus the failure you publish.

ACCESSIBILITY TREE SUPREMACY

🌳 A Windows desktop AI that reads the button names, not the pixels

A Windows desktop AI that reads the button names, not the pixels

The story: MudrikNow is an MIT licensed Windows tool built on nights and weekends. Hit Alt+Space over any window and it reads the active app’s UI Automation tree: buttons, fields, labels, values. Every rival in this category runs OCR on a screenshot instead. It is bring your own model, and the dev names Gemini Flash-Lite as the free pick.

The mode the dev is proudest of never touches your mouse. Auto-Guide hops a pointer to the exact control, then waits for you to click it. The launch post calls the release preview quality.

“It’s help, not a bot taking the wheel.” Famous_Can6494, in the r/SideProject launch post

The details:

  • The privacy gap: the indie rival ai-cowork screenshots every 5 seconds and holds 50 observations in memory. MudrikNow captures once per keypress.
  • The traction baseline: ai-cowork shipped a packaged 38 MB build and a landing page, and sits at 1 star.
  • The incumbent: screenpipe carries 20.7k stars and 2.1k forks, and shipped a commit the same day this launched.
  • The hardware floor: Windows Recall needs a 40 TOPs NPU and 16 GB of RAM before it turns on. An accessibility-tree reader needs neither.
  • The blast radius: the shell is read only, writes and deletes are blocked, and a violation kills the session.

Why builders care: The wedges left here are the read channel and the interaction mode, not the model. A pointer that waits for the user is a product decision, and it costs no NPU.

PRICED TO MOVE, BENCHED AT HOME

💰 Alibaba put a 2.4 trillion parameter model behind an Anthropic compatible endpoint

Alibaba put a 2.4 trillion parameter model behind an Anthropic compatible endpoint

The story: Qwen3.8-Max landed today at $2 per million input tokens and $6 out. Implicit caching runs $0.25 per million, and the context window runs to 1 million tokens. QwenCloud speaks the Anthropic API, so pointing an existing Claude Code install at it is four environment variables.

Qwen ran most of its own coding evals inside the Claude Code harness. Its own table then puts it at 67.7 on SWE-bench Pro against Fable 5 at 80.0. Open weights are due next week, a first for a Qwen-Max class model.

“Do not move production workloads on the strength of a teaser.” Asif Razzaq of Marktechpost, on July’s preview

The details:

  • What is actually live: 95 billion parameters fire per token, roughly 4% of the model on any given token.
  • Where it leads: PaperBench at 93.0, ahead of Fable 5 at 88.8.
  • Whose scoreboard: every figure here is Qwen’s own, and the agent contest it won ran on Alibaba’s Tianchi platform.
  • The self hosting math: at 4-bit the Max weights run roughly 1.2TB, against 141GB on a single H200.
  • The hostable sibling: Qwen3.8-27B goes open weights too, and Marktechpost calls it the one most builders can run.

Why builders care: The pitch here is cost and context, not a capability lead. The Max weights land in a datacenter, so the 27B is the one that changes a solo builder’s stack.

THE PELICAN IS DEAD, LONG LIVE THE PELICAN

🐦 Karpathy spent $10 to replace the pelican test, and left out the prompt

Karpathy spent $10 to replace the pelican test, and left out the prompt

The story: The run fed Opus 5 the first paragraph of The Lord of the Rings. The budget was 1M tokens. It took about 2 hours and produced 5500 lines of three.js, which @karpathy called janky but fun. The framing was explicit: this is the successor to Simon Willison’s pelican on a bicycle.

Hacker News gave it 493 points and 357 comments, and the loudest objection was not the jank. Nobody could find the prompt, so nobody can rerun it against their own shortlist.

“The difference between this and Simon’s pelican is that with Simon, I get the prompt.” consumer451, on Hacker News

The details:

  • The pelican still fails: dllu listed head tube alignment, fork offset, and chain to sprocket as live errors.
  • The harness confound: CapsAdmin argued these demos benchmark the model and the harness at once. That is not a read on raw model gain.
  • The contamination problem: attheballot noted Tolkien sits on a huge training corpus. That is the exact property Willison picked the pelican to avoid.
  • The saturation case: maxutility called the pelican saturated and uninteresting, since a good one no longer marks an unusual model.
  • Nobody is gaming it: Castillo ran 48 prompts across 7 models in July. The result was no evidence labs train for it.

Why builders care: The pelican survives as the cheap smoke test, because bike geometry still breaks on current models. Anything agentic scores the model and the harness together, so production picks belong in your own traces.

The genre is not slowing down. Somebody spun up a Habsburg jawed frog benchmark the same week, and it is below in Trending.

STACK OF THE DAY

✅ A language that makes you prove the code is right

F* is a proof-oriented programming language: you state what a function must guarantee, and the compiler checks the proof. It took 168 points and 76 comments on Hacker News. Niche, and worth an afternoon if you have ever shipped a parser you did not fully trust.

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

BOOKMARKED TODAY

See you tomorrow. Hit reply and tell me what you shipped this week.

Curated by AI, built by a human.