Recursive Flint: an Apache 2.0, 40B coding model with 2.5B active parameters and a self-reported 89.7% on SWE-bench Pro v2

Recursive Flint is a 40B-parameter mixture-of-experts coding model with about 2.5B active parameters, released under Apache 2.0 on October 21, 2026. Its 89.7% on SWE-bench Pro v2 is Recursive's own number and wasn't on Scale AI's leaderboard as of October 22.

A large glass circle with a small lit circle at its centre at true area for active parameters, on a mint gradient, titled 40B-A2.5B

What’s new, in 20 seconds

  1. Recursive Superintelligence published Flint on Hugging Face on October 21, 2026: a mixture-of-experts coding model with 39.8B total and about 2.5B active parameters, a documented 262,144-token context and Apache 2.0 weights.
  2. Recursive's model card lists 89.7% on SWE-bench Pro v2, 74.2% on SWE-bench Verified and 54.9% on Terminal-Bench 2.1, all run by Recursive. Flint wasn't on Scale AI's SWE-Bench Pro V2 leaderboard as of October 22, and Scale says that benchmark's public set is probably affected by training-time exposure.
  3. Recursive's rec engine needs an M4 Pro, M5 Pro or M5 Max Mac with at least 48 GB of memory and about 30 GB of disk. Recursive says Flint runs at more than 125 tokens per second on an M4 Pro MacBook Pro.
Contents

Recursive Flint is the first model from Recursive Superintelligence, the startup founded by former Salesforce chief scientist Richard Socher. It went up on Hugging Face on October 21, 2026. Flint is a coding model for agents that run on your own machine: a mixture-of-experts (MoE) model with 39.8 billion parameters, of which about 2.5 billion work on each token, with Apache 2.0 weights. That puts it among the open models small enough to run on a high-end laptop. Its headline score, 89.7% on SWE-bench Pro v2, comes from Recursive itself. Our guide to coding-agent benchmarks explains what such scores do and don't measure.

This story is based on Recursive's Hugging Face model card, its launch post, its rec engine's GitHub README, and Scale AI's SWE-Bench Pro V2 leaderboard and methodology post. Recursive's pages were checked October 23, 2026, and Scale's October 22.

The short version

  • Size: 39.8B total parameters, about 2.5B active per token (Recursive rounds this to "40B-A2.5B").
  • License: Apache 2.0 for the weights.
  • Context: 262,144 tokens on the model card; Recursive's launch post says "up to 512k," with 256K recommended.
  • Runs on: an M4 Pro, M5 Pro or M5 Max Mac with at least 48 GB of memory via Recursive's rec engine, or one Nvidia B300 or H200 GPU with SGLang.
  • Scores (vendor-reported): 89.7% SWE-bench Pro v2, 74.2% SWE-bench Verified, 54.9% Terminal-Bench 2.1.
  • Built with AI: Recursive says its automated research system, the Eureka Machine, developed "nearly every part" of Flint's model-building stack. That's the company's claim.

What is Recursive Flint?

The model card calls Flint "Recursive's mixture-of-experts language model for coding agents." It has 49 layers, 256 routed experts per MoE layer (6 chosen per token) plus a shared expert, and mixes sliding-window and full attention. Recursive says it trained Flint from scratch, from pretraining through reinforcement learning, with a June 2026 knowledge cutoff.

ItemDetail
PublishedOctober 21, 2026 (Hugging Face)
DeveloperRecursive Superintelligence, Inc.
Parameters39.8B total; about 2.5B active (2.2B excluding the output head)
ArchitectureMoE, 49 layers, 256 routed experts (6 active) plus a shared expert
Context262,144 tokens (model card)
LicenseApache 2.0
DownloadAbout 80 GB (BF16); Recursive's final model is NVFP4 4-bit
Mac (rec engine)M4 Pro, M5 Pro or M5 Max; at least 48 GB memory; about 30 GB disk
GPU (SGLang)One B300 or H200 per replica
Hosted API priceNo paid price published; Recursive serves a free endpoint on OpenRouter

Table 1Flint's weights are free to use under Apache 2.0, but a laptop needs 48 GB of memory to run it with Recursive's engine. Source: Recursive model card, launch post and rec README; OpenRouter.

Last verified: October 23, 2026

Can I run Flint on a laptop?

Yes, if it's a recent high-memory Mac. Recursive's rec engine lists an M4 Pro, M5 Pro or M5 Max with at least 48 GB of unified memory and about 30 GB of free disk. Recursive says the final 4-bit NVFP4 model "scores within 0.7 points of the 16-bit model across our benchmarks." It claims more than 125 tokens per second on an M4 Pro MacBook Pro and more than 150 on a 64 GB Nvidia RTX Spark at short contexts. Those speeds are vendor-reported.

The launch post says Flint works with llama.cpp, Ollama, Unsloth, LM Studio, vLLM and SGLang. Hugging Face listed 34 quantized versions of Flint on October 23. Recursive also serves the model free through OpenRouter as recursive/flint-v1.0:free, with the same 262,144-token context. For the memory math, see how to choose a small model for your laptop, and for setup, our Ollama guide. Flint is in the same "tiny active, large total" class as Liquid AI's LFM2.5-24B-A2B, but its Apache 2.0 license has no revenue cap.

What does Flint score on SWE-bench Pro v2?

Recursive reports these results on its model card. All were run by Recursive:

BenchmarkScoreHarness
SWE-bench Pro v289.7%mini-swe-agent, no internet
SWE-bench Verified74.2%mini-swe-agent, no internet
Terminal-Bench 2.154.9%Terminus 2; retrieved solutions count as failures

Table 2All three scores are vendor-reported, averaged pass@1 over at least five attempts with agent timeouts of up to 5 hours. Source: Recursive model card and launch post.

Last verified: October 23, 2026

The 89.7% does appear on the model card. SWE-Bench Pro V2 is real: Scale AI released it on September 22, 2026, with 642 tasks across 11 repositories after dropping 89 invalid tasks from the original 731. A score is the share of tasks where the model's patch passes hidden tests.

But Flint wasn't on Scale's public V2 leaderboard as of October 22, so no outside party has reproduced the number. Scale warns that the public set has "been on the open web since before these models were trained" and treats its private set as the clean measure. Recursive reports no private-set score. Its launch post claims Flint "leads MoE models with fewer than 50 billion total parameters on agentic coding benchmarks."

For context only: on October 22, Scale's leaderboard listed Kimi-K3 at 88.20% and Claude Sonnet 5.5 at 70.59%, both with mini-swe-agent. Scale's runs follow its own settings, including 50- or 250-turn limits, while Recursive allowed timeouts of up to five hours. A vendor's own run and a leaderboard run can't be ranked together. Our comparison of Claude Code, Codex and Cursor explains why such leaderboards score a model and harness together, not a product.

Did an AI really build Flint?

Recursive says its "Eureka Machine," an automated research system, helped develop "nearly every part of Flint's model-building stack," and that Flint was built "in under four months" by "a small team of people and agents." Its examples include searching expert configurations from a 35B/3B starting point, adding a distillation stage that "nearly halved the number of training steps," and writing a Metal megakernel for Apple's M4 and M5 chips. The post doesn't separate human and machine work in detail, and no outside review of the Eureka Machine has been published.

Recursive came out of stealth on May 13, 2026 with $650 million at a $4.65 billion valuation, according to SiliconANGLE, in a round led by Alphabet's GV and Greycroft.

What's confirmed, reported and uncertain

  • Confirmed (model card, Hugging Face): 39.8B parameters, about 2.5B active, Apache 2.0, 262,144-token documented context, October 21 publication, hardware for SGLang.
  • Vendor-reported: all benchmark scores, speeds, the 0.7-point quantization gap and the Eureka Machine's role.
  • Reported: funding and valuation (SiliconANGLE).
  • Uncertain: independent SWE-bench Pro v2 results; the context discrepancy (262K vs "up to 512k"); paid hosted API pricing.

Read next

Comments (0)

More on Open models

View all
Open source · NewsNemotron 3.5 Transcribe: Nvidia's open speech recognition model covers 40 languages under OpenMDW, with about 4B active parametersNemotron 3.5 Transcribe, released by Nvidia on Hugging Face on October 28, 2026, is an open-weight speech recognition model for 40 languages under the OpenMDW-1.1 license. It activates about 4B parameters per token, runs on a single Nvidia GPU and handles recorded audio, not live streams. Nvidia's word error rates are vendor-reported.·6 min read
Research · AnalysisQwenputer: a developer compiled a RISC-V CPU into Qwen3.5-4B's weights, with no training, and says it runs 18 million instructions without an errorQwenputer is Qwen3.5-4B with a 32-bit RISC-V CPU compiled directly into 11 extra layers, using the model's Gated DeltaNet memory as RAM. Developer Divyansh Agrawal says no weights were trained, the CPU passes the official RISC-V tests, and Qwen can call it as a tool for exact arithmetic. What was built, how, what 'deterministic' means and the limits.·7 min read
Open source · ExplainerWhat is an abliterated model? How refusal removal works, why abliterated DeepSeek is now sold by API, and the safety questionsWhat is an abliterated model? It's an open-weight model whose weights have been edited to strip out its learned refusals, based on 2024 research showing refusal sits along a single direction inside the model. In October 2026, an API router began selling an abliterated DeepSeek V4.1 Flash from five providers. What the technique is, what the licenses and terms allow, and what safety researchers say.·8 min read
Products · ExplainerOffline AI assistant: how Survival LLM pairs a local model with a 930,000-article emergency library, and how people run AI with no internetAn offline AI assistant runs the model and its reference library on your own computer, so it keeps working when the internet doesn't. Survival LLM, which drew wide attention on October 27, 2026, bundles one of four models with about 930,000 Wikipedia articles and medical and repair references. What it needs, how Kiwix, Ollama, llama.cpp and LM Studio work offline, and where offline AI falls short.·9 min read
The Week in AI · every Friday

Get the cluster, not just the headline.

The week’s biggest stories in AI and tech, what they mean, and what to read next.

Free. One email a week. Unsubscribe in one click.