Recursive releases Flint for local agentic coding
Flint uses a mixture-of-experts architecture with 39.8 billion total parameters and roughly 2.5 billion active per token, targeting codebase investigation, bug fixing, feature implementation, and test writing.

AT A GLANCE
Key points
- 39.8B total parameters with about 2.5B active per token
- Apache 2.0 weights are available on Hugging Face
- Recursive says Eureka Machine contributed across the development pipeline
What is changing?
Recursive has released Flint, a model built for agentic coding on local hardware. According to the company’s model card, the decoder-only mixture-of-experts architecture has 39.8 billion total parameters, with roughly 2.5 billion active for each token. It is designed to investigate codebases, fix bugs, implement features, and write tests.
Flint’s BF16 weights are available on Hugging Face under the Apache 2.0 license. Recursive says separately quantized variants are being prepared for Apple Silicon and NVIDIA hardware, and that the model supports multi-turn tool use. The company reports context windows up to 512,000 tokens, while recommending users stay within 256,000 tokens for the best results.
Recursive says its automated research system, Eureka Machine, contributed across much of the development pipeline, including data, training recipes, architecture, infrastructure, and inference optimization. The approach could expand the role of automation in helping small teams build specialized local models. However, the published benchmarks rely on developer measurements, and the model card warns that faulty code and unsafe tool calls remain possible, recommending testing and strict permission boundaries.
Explore the original sources
Source date: 21 October 2026.
Published by AI Radar: 22 Oct 2026, 14:08 (Istanbul, UTC+3). Updated: 22 Oct 2026, 15:13.
FOLLOW THE TOPIC
Topics and tags
Share your discovery.
Send this story to a friend.
Reader comments
What do you think about this development? Share your experience or question. Comments are published after editorial approval.
Your name/nickname and comment become public if approved. Read: Privacy notice.






Loading comments…