anaksor-ocr
Sokheng · Kit
Reads Khmer and English text from documents, receipts and photos of signs, using a detector for text lines and a recogniser for each line. Suits developers who…
A 39.8B mixture-of-experts language model for coding agents that investigates codebases, fixes bugs, adds features and writes tests. For developers who run their own agents on a GPU server.
Recursive Flint is a kit in the Developer category, listed by Mindket. It is free. This is version 1, last updated on . Download it on this page, a zip of its files. Nothing in it runs by itself.
pip install -U huggingface_hub openai hf download RecursiveSI/flint --local-dir flint && cd flint # about 80 GB docker build -t flint-sglang sglang
Recursive Flint is a language model from Recursive for coding agents. It has 39.8 billion parameters in total, but only about 2.5 billion are active for each token. It takes and returns text, reasons step by step and can call tools over several turns. The repository holds the BF16 checkpoint, the tokenizer, the chat template and an SGLang serving kit.
It suits engineering teams and tool builders who want to host a coding model themselves and wire it into their own agents.
| Industry | Who uses it | How they use it | Example |
|---|---|---|---|
| Software teams | Engineers | Run a coding agent on their own GPUs | Ask it to track down a failing test in a repository |
| Developer tools | Tool builders | Back an agent through an OpenAI-compatible API | Serve the model with SGLang and call it from the openai client |
| AI research | Researchers | Study a mixture-of-experts coding model | Run it on the agent benchmarks the project reports |
People without access to a B300 or H200 GPU can skip the BF16 checkpoint and look at the quantized variants, which the project prepares separately.
| Use case | Who | What they get back |
|---|---|---|
| Investigating a codebase | Developers | The model's findings about how a repository works |
| Fixing bugs | Engineering teams | Proposed code changes for a reported problem |
| Features and tests | Developers | New code for a feature, plus tests written for it |
You need these first:
pip install -U huggingface_hub openai hf download RecursiveSI/flint --local-dir flint && cd flint # about 80 GB docker build -t flint-sglang sglang docker run -d --name flint --gpus '"device=0"' --ipc=host -p 127.0.0.1:30000:30000 \ -v "$PWD:/model" -e MODEL=/model flint-sglang bash /model/sglang/serve_b300.sh # H200: serve_h200.sh until curl -sf localhost:30000/health_generate >/dev/null; do sleep 15; done # progress: docker logs -f flint
When the server is up, send chat requests to its OpenAI-compatible endpoint with the model name flint. Use the checkpoint's chat template and keep the returned reasoning_content in the conversation history. The prompt and the output share one context window.
| Tool | What it does |
|---|---|
| sglang/example_client.py | Example client that shows reasoning and a tool call |
| sglang/serve_b300.sh | Starts the server on a B300 GPU |
| sglang/serve_h200.sh | Starts the server on an H200 GPU |
| sglang/README.md | Documents what you need, the options of the serve scripts, running on several GPUs and the API |
You send the model a request such as "Find why my date parser test fails and fix it." It can reason about the code, call tools over several turns, and return a fix. For hard problems, allow at least 32768 output tokens, reasoning included.
Flint is a large coding model that you host yourself, not a chat website. A first small thing to try is the example client in the sglang folder once the server reports healthy.
Under the hood, each mixture-of-experts layer has 256 routed experts, picks 6 per token and adds one shared expert. Of its 49 layers, 2 are dense and 47 are mixture-of-experts layers. Sliding-window attention covers 513 tokens in 35 layers, and 14 layers use full attention. The documented context is 262,144 tokens, and the vocabulary has 150,144 tokens. Only about 2.5B parameters work per token, but all the weights still have to fit in memory.
These are the project's own release scores. Evaluation setups differ between sources, and the Terminal-Bench score counts solutions found through web retrieval as unsuccessful.
A 39.8B mixture-of-experts language model for coding agents that investigates codebases, fixes bugs, adds features and writes tests. For developers who run their own agents on a GPU server.
Made by RecursiveSI on Hugging Face. These notes are Mindket's, written from its model page and model card; the model's own files and license are on Hugging Face.
What it is: Recursive Flint is a language model from Recursive for coding agents. It has 39.8 billion parameters in total, but only about 2.5 billion are active for each token. It takes and returns text, reasons step by step and can call tools over several turns. The repository holds the BF16 checkpoint, the tokenizer, the chat template and an SGLang serving kit.
Who it suits: It suits engineering teams and tool builders who want to host a coding model themselves and wire it into their own agents.
Industry | Who uses it | How they use it | Example
Software teams | Engineers | Run a coding agent on their own GPUs | Ask it to track down a failing test in a repository
Developer tools | Tool builders | Back an agent through an OpenAI-compatible API | Serve the model with SGLang and call it from the openai client
AI research | Researchers | Study a mixture-of-experts coding model | Run it on the agent benchmarks the project reports
People without access to a B300 or H200 GPU can skip the BF16 checkpoint and look at the quantized variants, which the project prepares separately.
Where to use it:
Use case | Who | What they get back
Investigating a codebase | Developers | The model's findings about how a repository works
Fixing bugs | Engineering teams | Proposed code changes for a reported problem
Features and tests | Developers | New code for a feature, plus tests written for it
How to set it up: You need these first:
pip install -U huggingface_hub openai
hf download RecursiveSI/flint --local-dir flint && cd flint # about 80 GB
docker build -t flint-sglang sglang
docker run -d --name flint --gpus '"device=0"' --ipc=host -p 127.0.0.1:30000:30000 \
-v "$PWD:/model" -e MODEL=/model flint-sglang bash /model/sglang/serve_b300.sh # H200: serve_h200.sh
until curl -sf localhost:30000/health_generate >/dev/null; do sleep 15; done # progress: docker logs -f flint
How to use it: When the server is up, send chat requests to its OpenAI-compatible endpoint with the model name flint. Use the checkpoint's chat template and keep the returned reasoning_content in the conversation history. The prompt and the output share one context window.
Tool | What it does
sglang/example_client.py | Example client that shows reasoning and a tool call
sglang/serve_b300.sh | Starts the server on a B300 GPU
sglang/serve_h200.sh | Starts the server on an H200 GPU
sglang/README.md | Documents what you need, the options of the serve scripts, running on several GPUs and the API
Example: You send the model a request such as "Find why my date parser test fails and fix it." It can reason about the code, call tools over several turns, and return a fix. For hard problems, allow at least 32768 output tokens, reasoning included.
For newcomers and experts: Flint is a large coding model that you host yourself, not a chat website. A first small thing to try is the example client in the sglang folder once the server reports healthy.
Under the hood, each mixture-of-experts layer has 256 routed experts, picks 6 per token and adds one shared expert. Of its 49 layers, 2 are dense and 47 are mixture-of-experts layers. Sliding-window attention covers 513 tokens in 35 layers, and 14 layers use full attention. The documented context is 262,144 tokens, and the vocabulary has 150,144 tokens. Only about 2.5B parameters work per token, but all the weights still have to fit in memory.
Download the BF16 checkpoint
Build and start the SGLang container
Wait for the health check to pass
Send OpenAI-compatible chat requests
Good to know: These are the project's own release scores. Evaluation setups differ between sources, and the Terminal-Bench score counts solutions found through web retrieval as unsuccessful.
Title: Release evaluation scores
Terminal-Bench 2.1: 54.9%
SWE-bench Pro v2: 89.7%
SWE-bench Verified: 74.2%
Download its files with Hugging Face's command line:
pip install -U huggingface_hub
hf download RecursiveSI/flint
Then follow the usage in its model card. Nothing in this kit runs by itself.
README.md 6 KB
Listed Hugging Face models in the same category that share the most tags with this one.
| Product | Downloads, last 30 days | Likes | Parameters | License | Last change |
|---|---|---|---|---|---|
| Recursive Flint This page | 51,087 | 1,391 | 39.8B | apache-2.0 | |
| Flint INT4Shares flint · text-generation · conversational | 22,586 | 30 | — | apache-2.0 | |
| flint-mixed-3-4bitShares flint · text-generation · conversational | 5,091 | 12 | 39.8B | apache-2.0 | |
| flint-GGUFShares flint · text-generation · conversational | 325,104 | 376 | 39.8B | apache-2.0 | |
| Qwen3-0.6BShares text-generation · conversational · transformers | 19,718,599 | 1,894 | 752M | apache-2.0 | |
| Qwen3-14BShares text-generation · conversational · transformers | 12,965,376 | 540 | 14.8B | apache-2.0 |
Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search and on Trendshift. Mindket doesn’t write or check them. Open one to read it where it was posted.
Sokheng · Kit
Reads Khmer and English text from documents, receipts and photos of signs, using a detector for text lines and a recogniser for each line. Suits developers who…
Qwen · Kit
Qwen2.5-7B-Instruct as GGUF files in eight quantization sizes, to chat with locally through llama.cpp. For people who want a capable 7.6B model on their own co…
ACE-Step · Kit
Generates music from text with a 4B diffusion decoder, 50 steps and guidance control, aiming for higher audio quality than the base. For creators with a GPU of…
alirezarezvani · Skill
Adds 411 ready-made skills for Claude Code and other coding agents, grouped by role from engineering and product to marketing, finance and compliance. Installs…
block · Kit
Self-hostable workspace where people and AI agents share the same rooms, built on a Nostr relay that logs every action as a signed event. For teams that want t…
backnotprop · Kit
Opens your AI coding agent's plans, specs and code changes in a browser so you can annotate or comment on them and send the feedback straight back to the agent.