Ling 3.1 Flash: InclusionAI releases 560B open-weight model under MIT license

InclusionAI, Ant Group's AI lab, has released Ling 3.1 Flash as an open-weight model, according to its Model Card. It has 560 billion parameters, with only 25 billion active per token. The model is MIT-licensed and aims to excel at coding and long agentic tasks. Until now, it was only available through Ant's own service.

Model releases Try it yourself Oct 23, 2026 5 min read Source: Google News (TW)
Illustrative image, AI-generated

What's going on

InclusionAI, the AI lab of Ant Group (best known for Alipay), has released Ling 3.1 Flash, a large language model, as an open-weight model. "Open weight" means you can download the trained weights – roughly, the settings the model learned during training – and run the model yourself. According to the Model Card, which Techapple's report draws on, the weights were released on October 16, 2026 under the permissive MIT license, in fp8 format (8-bit floating-point numbers that use less memory than 16-bit). Ready-made launch recipes are also available for the inference frameworks SGLang and vLLM, the programs used to run models like this on servers.

Some context: the model wasn't new. Ant announced it on September 30, 2026 and initially offered it only in its own product and through its own API. An OrcaRouter report written in mid-October explicitly noted that there were no weights, no Model Card and no license. So the current release follows the plan Ant itself had laid out.

Architecture: big, but frugal

Ling 3.1 Flash is a Mixture-of-Experts (MoE) model. Think of it as a team of specialists: the model contains a great many areas of expertise ("experts"), but only a few are consulted for each word (token). That saves compute.

  • Parameters: about 560B in total, roughly 25B active per token – a ratio of about 1 to 22.
  • Experts: 512 routed experts plus 1 shared expert that always contributes. According to OrcaRouter (citing Ant's announcement), each token picks 8 of them.
  • Attention: a hybrid design of 63 KDA layers and 9 Gated-MLA layers. KDA stands for Kimi Delta Attention, a "linear" attention whose compute cost grows only proportionally with text length rather than quadratically. The Gated-MLA layers keep a global view of the entire text. That works out to 7 linear layers for every 1 global layer.
  • Context: the model is designed for 1 million tokens. That's roughly the volume of several thick books, all "in view" at once.

For comparison, the predecessor Ling-3.0-flash has 124B parameters, with 5.1B active. Ling 3.1 Flash is therefore about 4.5 times as large and activates roughly five times as many parameters per token.

Performance, according to the vendor

The official figures cover two coding benchmarks:

Benchmark Result (vendor-reported)
SWE-bench Pro 68.74
DeepSWE 59.7

Both tests check whether a model can solve real software engineering tasks. The sources contained no independent re-measurements. Ant's announcement also cites long-horizon results, such as a Lua-to-x86-64-ELF compiler built in about 17 hours without interruption that passed 178 of 182 tests (97.8%). In a Pyright optimization run of about 10 hours, the model reached 1.432x speed with all 2,279 tests passing. These are also vendor numbers on self-defined tasks, and the competitors' figures are expressly just "listed" there, not a head-to-head comparison under identical conditions.

The model is positioned for long, real-world tasks: office work from a vague request to a finished result, software development that runs for hours, and agents that call tools one after another and correct themselves. It handles text only; for images, Ant points to Ling-3.0-flash-VL.

Context: 1 million or 256K?

During the test phase, the service ran with 256K tokens. Ant's plan was to open the full 1M window once the free phase ended and to release the model as open source at the same time. Whether the newly released weights make the full 1M usable isn't clear from the sources. The memory costs of such a long context also remain an open question. If in doubt, plan for 256K.

What you need to try it

This isn't a model for your home PC. The fp8 weights alone are likely several hundred gigabytes (560B parameters ≈ 560 GB at 8 bits). Even with 4-bit quantization, you're looking at roughly 280 GB plus room for the context. A realistic setup is a multi-GPU server with several 80 GB cards or a cloud cluster, plus correspondingly large RAM and storage. It won't run in any sensible way on a Mac, a regular CPU or the free tier of Google Colab. Whether GGUF versions or an Ollama entry exist isn't stated in the sources. For smaller hardware, the predecessor Ling-3.0-flash or Ling-3.0-tiny makes more sense.

Our take

An MIT-licensed model of this size with strong coding scores is interesting for companies and research groups with their own GPU infrastructure, because they can run and adapt it without license hurdles. The release lands amid a wave of cheap, open, agent-capable models, which according to Techapple also includes DeepSeek V4.1-Flash-1017 and Tencent's Hy Memory 2.0. A few caveats: all benchmark figures come from the vendor, the charts in Ant's announcement contain no citable table of individual values, and the sourcing isn't entirely clear – an older report still said the release wasn't happening. We rely on the Model Card as reported by Techapple, so take a look at the repository yourself before deploying. Because of its size, the model has little practical use for home users.

Sources

#ling#inclusionai#ant-group#moe#open-weights#coding
Read the original source

Try it yourself: Ling 3.1 Flash

Explained step by step, no prior knowledge needed – on your own computer or free in your browser.

What can I do with it?

Ling 3.1 Flash is a text-only model built for coding, long agentic workflows and office tasks. Run locally, it can solve software problems, call tools in sequence and process long documents.

Who is it worth it for?

Interesting for companies, research groups and GPU cluster operators who want to self-host a large open coding model. Too big for home users with a regular PC.

Size572.1 B parameters (25 billion active)
Download343 GB (about 7.6 hr at 100 Mbit/s)
Licensemit
TypeLanguage model (text chat)

What your computer needs

Graphics card (NVIDIA), fully in VRAM at least 379 GB VRAMservers only, with multiple data-center GPUs (e.g. 8× H100) – fastest; with less VRAM, see the next line
Graphics card + system memory (MoE offloading) from approx. 12 GB VRAM + 512 GB RAMdie Experten liegen im Arbeitsspeicher, nur der Kern auf der Grafikkarte (llama.cpp/LM Studio). Langsamer als komplett im VRAM, aber auf normalen PCs machbar
Mac (Apple Silicon M1–M5) too big for any MacThe GPU and CPU share the memory – the model can use about 70% of it
CPU only (no graphics card) Very slow without a graphics cardan estimated 2 words per second on a current desktop PC (MoE: only 25 billion parameters active per word). This requires at least 512 GB of RAM.
Storage approx. 345 GB freeModel download plus programs
Google Colab too big for Colabeven the largest Colab GPUs aren't enough

Values estimated from the model size – the Model Card may have more precise figures.

Which variant is right for me?

Many models come in several sizes or "quantizations." These are compressed versions: smaller and faster, but slightly less accurate. Rule of thumb: pick the largest variant whose memory requirement fits in your VRAM (video memory). The scripts below choose this for you automatically.

VariantDownloadNeeds approx.Compatible graphics cards
4-bit (Q4) Default 343 GB379 GBservers only, with multiple data-center GPUs (e.g. 8× H100)
8-bit (Q8) 612 GB674 GBservers only, with multiple data-center GPUs (e.g. 8× H100)
16-bit (Original) 1144 GB1260 GBservers only, with multiple data-center GPUs (e.g. 8× H100)

fp8 weights are released (roughly 560 GB). According to the sources, there's no smaller variant for home hardware; Ling-3.0-flash or Ling-3.0-tiny are better suited for that. Quantized versions would first have to be created by the community.

  • The fp8 weights take up about 560 GB, plus memory for the context (KV cache).
  • A realistic setup is a multi-GPU server with several 80 GB cards.
  • According to the source, day-0 recipes for SGLang and vLLM are available.
  • The linear KDA attention is meant to make long context cheaper than classic attention.
  • The model won't run in any sensible way on a Mac, a CPU alone or free Colab.

Groß (572,1 B parameters, MoE): running entirely on the GPU takes a lot of VRAM (video memory). With MoE offloading, a regular graphics card plus plenty of RAM is enough (see table). Colab Free isn't enough.

How do I find out what my computer has?
  • Windows: Press Ctrl + Shift + Esc → Task Manager → Performance tab → click GPU on the left. At the bottom you'll see Dedicated GPU memory (that's your VRAM). You'll find system memory under Memory.
  • Mac: Apple menu at the top left → About This Mac. You'll see your chip (e.g. M2) and memory (e.g. 16 GB). On Apple chips, graphics and processor share this memory.
  • Linux: Type nvidia-smi in the terminal (shows your graphics card and its memory) and free -h for system memory.

Guide

Google Colab (in your browser, no installation)

Google Colab is a free service from Google. It gives you a computer with a graphics card in your browser for a few hours. All you need is a Google account. For this model: too big for Colab – even the largest Colab GPUs aren't enough.

  1. Download the notebook. Click the button and save the file.

    Download colab.ipynb

  2. Open Colab. Go to colab.research.google.com and sign in with your Google account.
  3. Upload the notebook. In the window that appears, click Upload on the left (or choose File → Upload notebook at the top) and select the file colab.ipynb.
  4. Turn on the GPU. In the top menu, go to Runtime → Change runtime type → under Hardware accelerator, select T4 GPU (with Colab Pro: L4 or A100) → Save.
  5. Start everything. Runtime → Run all (keyboard shortcut Ctrl + F9). If you see the warning “This notebook was not authored by Google,” click Run anyway.
  6. Wait. The cells run one after another. A green checkmark appears to the left of each cell when it's done. Installation and download take about 118 minutes here.
  7. Try it out. The result appears below the last cell. To test something else, change the text in the cell and run it again with Shift + Enter. The last cell starts a proper chat with an input field.
  8. Clean up. When you're done: Runtime → Disconnect and delete runtime. This saves your free quota.

Good to know: The free GPU is limited (usually a few hours per day). After about 90 minutes of inactivity, Colab disconnects, and you'll have to start everything over.

Windows 10 / 11

The easiest way is Ollama, a free program that launches AI models with a single command.

  1. Update your graphics driver (NVIDIA cards only): Install the NVIDIA app or the latest driver. For AMD cards, use the latest Adrenalin driver.
  2. Install Ollama. Download the file OllamaSetup.exe from ollama.com/download/windows, double-click it, and choose Install. Afterward, a small llama icon appears in the taskbar at the bottom right.
  3. Open a terminal window. Press the Windows key, type PowerShell and press Enter. A blue or black window opens.
  4. Start the model. Copy this command ("Copy" button), paste it into the window with a right-click, and press Enter:
    ollama run hf.co/Baekpica/Ling-3.1-flash-VQ-GGUF
    The first time, Ollama downloads the model (343 GB (about 7.6 hr at 100 Mbit/s)). After that, it's instant.
  5. Start typing. Once >>> Send a message appears, type your question and press Enter. Type /bye to end the chat.

Not enough memory? Pick a smaller variant from the table above, e.g. ollama run hf.co/Baekpica/Ling-3.1-flash-VQ-GGUF.

Prefer automatic? A script that picks the right variant for you
  1. Download both files into the same folder: try_windows.ps1 demo.py
  2. Open the folder in File Explorer, right-click an empty spot and choose Open in Terminal.
  3. Paste this command and press Enter:
    powershell -ExecutionPolicy Bypass -File try_windows.ps1

If needed, the script installs Ollama via winget, measures your VRAM (video memory) and downloads the matching variant.

macOS

Macs with an Apple chip (M1 to M5) are ideal. Older Intel Macs are very slow.

  1. Install Ollama. Download it from ollama.com/download/mac, open the file, and drag Ollama into your Applications folder. Launch Ollama once – a llama appears in the menu bar at the top.
  2. Open Terminal. Press Cmd + Space, type Terminal, and press Enter.
  3. Start the model. Paste the command (Cmd + V) and press Enter:
    ollama run hf.co/Baekpica/Ling-3.1-flash-VQ-GGUF
    The first time, the model is downloaded (343 GB (about 7.6 hr at 100 Mbit/s)).
  4. Start typing. Type your question and press Enter. Quit with /bye.
Pick the right variant automatically

try_mac.sh

cd ~/Downloads
bash try_mac.sh

Linux

  1. Check your GPU. nvidia-smi should show your card. If it doesn't, install the driver on Ubuntu and restart:
    sudo ubuntu-drivers install
  2. Install Ollama:
    curl -fsSL https://ollama.com/install.sh | sh
  3. Start the model:
    ollama run hf.co/Baekpica/Ling-3.1-flash-VQ-GGUF
    Exit with /bye. Use ollama ps to check whether the model is running on the GPU.
  4. Or let it pick the right variant automatically:

    try_linux.sh

    bash try_linux.sh
    # mit Python/transformers statt Ollama:
    MODE=hf bash try_linux.sh

Try it

Analyze this Python project, find the reason the test is failing and suggest a patch.
Summarize the following 200 pages of contract documents and list all deadlines in a table.
Plan step by step how to build a small Rust library for reading PNG files, and write the first part of the code.

If something goes wrong

Double-check the exact repository address: the sources only mention the Model Card, with no link.

Use current versions of vLLM or SGLang and follow the recipes in the Model Card.

Don't assume 1M context: the hosted service initially offered only 256K.

The model doesn't understand images; Ling-3.0-flash-VL exists for that.

“out of memory,” a crash, or your computer freezes

The model is too big for your VRAM (video memory). Pick a smaller variant from the table above and close other programs, especially games and browsers with lots of tabs.

It runs, but extremely slowly

Your CPU is probably doing the work instead of your graphics card. In Ollama, the PROCESSOR column of ollama ps shows how much runs on the GPU. If it says "100% CPU", update your graphics driver or pick a smaller variant that fits entirely into VRAM (video memory).

“ollama” or “python” is not found

Close the terminal window and open it again so it recognizes the newly installed program. For Python on Windows: reinstall it and check Add python.exe to PATH.

Windows: "Running scripts is disabled on this system"

Run the script with exactly the command above: powershell -ExecutionPolicy Bypass -File try_windows.ps1. This allows execution for this one time only.

Error message when loading the model (version, "trust_remote_code", unknown architecture)

Brand-new models often need the latest software version. With Ollama: update Ollama. With Python: pip install -U transformers in the activated environment. The Model Card usually lists the exact version.

Tokenstrom generates the scripts and notebook automatically. Please take a quick look before running them – they're plain, readable text. Mind the model's license: mit.

Ask the AI assistant

Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.

Connecting …

The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.

Comments

What do you think? Already tried it? Write it here, no sign-up needed.

  1. Loading comments …

Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.