Recursive Flint: A Free 40B Coding Model for Laptops, With 74.2% on SWE-bench Verified by Its Own Count

Most local coding models are a compromise: small enough to run on a laptop, too weak to trust with a real bug. Recursive says Flint closes that gap. Coverage so far has focused on the claim that AI helped build it. For a developer deciding whether to install it, the scores, the memory it needs and the fine print matter more.

The model in numbers

What "runs on a laptop" really means

• Recursive tested on an M4 Pro MacBook Pro and a 64GB RTX Spark, and Wired's reviewer used a Mac with 48GB of memory. Neither the announcement nor the model card states a minimum memory figure.
• The 4-bit NVFP4 build is what makes laptop use possible. Recursive says the gap between it and full precision is within 0.7 points across its benchmarks.
• It works with llama.cpp, Ollama, Unsloth, LM Studio, vLLM and SGLang, and Recursive also released a small inference engine called rec.
• Running locally means it works offline, keeps code on your machine and has no usage fees.

How it was built

Recursive says a small team built Flint from scratch in under four months, with its automated research system, the Eureka Machine, contributing to nearly every step from pretraining to inference. Socher told TechCrunch its contributions included the sparser model shape, low-bit training that shrank the model by 71% with almost no quality loss, and custom kernels. The company emerged from stealth in May with $650 million at a $4.65 billion valuation, backed by GV, Nvidia and AMD Ventures.

What hasn't been checked

• Every benchmark and speed figure comes from Recursive. No independent leaderboard had published results at the time of writing.
• The context window is stated two ways: 262,144 tokens on the model card and up to 512k in the announcement.
• TechCrunch dates the release 21 October; the announcement page is dated 23 October.
• Recursive says Flint needs more guidance than large paid assistants and recommends breaking big tasks into smaller steps.

What this means if you pick coding tools

• If you can't send code to a cloud model, Flint is worth testing first: Apache 2.0 and local inference remove the two usual blockers.
• Test it on your own repository before relying on its SWE-bench score. Vendor-run agent benchmarks vary a lot with the harness.
• Use it alongside a cloud assistant, not instead of one, for long multi-file changes, as Recursive's own guidance suggests.
• Check your machine's memory first. A 48GB or 64GB machine is the tested setup, not a typical laptop.