Sage-A1.5: Open 35B agent model uses subagents and self-checking for research

Shanghai AI Laboratory has released Sage-A1.5, a Mixture-of-Experts model with roughly 35B parameters under Apache 2.0. It can split tasks across parallel subagents and check its own work mid-reasoning. According to the developers, it keeps pace with much larger models on agent benchmarks.

Model releases Try it yourself Oct 15, 2026 5 min read Source: Hugging Face Trending
Illustrative image, AI-generated

What this is about

Shanghai AI Laboratory (team InternScience) has released the model Sage-A1.5 on Hugging Face. It is an "agentic" language model: it's meant to do more than answer questions. It plans tasks across many steps, uses tools such as search or code execution, and adjusts its approach along the way. The weights are available for download under the Apache 2.0 license, also on ModelScope. There is also a technical report on arXiv, code on GitHub and a homepage.

Technically, Sage-A1.5 is a Mixture-of-Experts (MoE) model. It consists of many specialized sub-networks ("experts"), and only a small share of them is active for each token. That saves compute. It is based on Qwen3.6-35B-A3B and the team's own predecessor, Agents-A1. The model card says "35B"; Hugging Face counts 36B parameters (roughly speaking, the tunable values learned during training). The model is also tagged as a vision-language model (VLM), so it can process images too.

The three core capabilities

The developers name three focus areas:

  • Agentic orchestration: The model breaks a task into independent sub-questions and sends out subagents that work in parallel. Each subagent has its own context window (its own "working memory" for the conversation history) and its own tool access. That keeps the subtasks from interfering with each other. The main model then combines the results.
  • Verification: An optional mode in which the model pauses within its own chain of thought, checks what is established and what has failed, and changes direction in the same turn. There is no external checker.
  • Open scientific discovery: The model is meant to explore and research rather than just answer set questions, and to deliver traceable intermediate results.

Other listed features include native function calling, scientific and domain reasoning, and precise following of instructions with multiple constraints.

Benchmarks (developer-reported)

The comparison covers similarly sized models (Agents-A1, Qwen3.6-35B-A3B, Ornith-1.5) and larger models (Kimi-K3, GLM-5.3, GPT-5.6-sol). The figures come from the developers. For competitors, they took values from those models' technical reports and measured missing ones themselves.

Benchmark Sage-A1.5 Agents-A1 Qwen3.6-35B-A3B Kimi-K3 GLM-5.3 GPT-5.6-sol
GAIA 95.1 96.0 78.6 92.2 92.2 88.3
BrowseComp (with orchestration) 82.8 75.5 67.9 91.2 76.2 90.4
SWE-bench Pro 61.2 43.6 49.5 63.3 64.6 64.6
IFBench 81.6 80.6 64.4 72.1 53.4 72.7
FrontierScience-Research 48.3 40.0 2.9 21.7 16.7 26.7
HLE with tools 55.1 47.6 36.2 56.0 62.5 64.5

The developers say they achieve the best overall scores on XBench-DS-2510 (92.0), IFBench, PinchBench (90.0), FrontierScience-Olympiad (81.0), FrontierScience-Research, CMT (80.0) and OmniDocBench (91.5). On GAIA, the model scores higher than every larger comparison model, though its predecessor Agents-A1 reaches 96.0 there. Compared with Agents-A1, Sage-A1.5 improves sharply on engineering tasks: SWE-bench Pro +17.6, SWE-bench Multilingual +14.0, PinchBench +13.1, MLE-Lite +21.3.

On many tests, though, it clearly trails the big models. Examples are BrowseComp without orchestration (81.7 versus 91.2 for Kimi-K3), MLE-Lite (65.2 versus 77.3), ChemCOTBench (66.5 versus 82.5) and CritPt (20.0 versus 32.3). On MatTools (42.6) and HiPhO (45.3), even Agents-A1 comes out ahead. For the SWE-bench series, the developers used the mini-SWE-agent scaffold, temperature 1.0, 200K context and a fully offline environment.

How to use the two extra modes

Both modes are off by default.

Orchestration: You register a tool called spawn_subagent. The model calls it when a task can be split into independent investigations. Each subtask needs task, context and expected_output, because subagents can't see the main conversation. They return JSON with an answer, status, evidence and open issues. If they can't find anything, they reply "UNKNOWN" instead of guessing. By default, 5 tasks per call and 20 turns per subagent are allowed. Your own harness, not the model, runs the subagents.

Verification: You pass chat_template_kwargs: {"verification": true}. A non-empty system message is required, otherwise you get an HTTP 400 error. The value must be a JSON boolean. The self-check appears in the reasoning_content field.

Recommended sampling parameters: temperature 1.0, top_p 0.95, top_k 20, min_p 0.0, presence_penalty 1.5.

What you need to try it

The source lists no minimum requirements. As a rule of thumb, a 36B model needs about 20–24 GB of memory at 4-bit quantization and considerably more (around 70 GB) at full precision. The examples run with vLLM on one GPU with 262K context. Long context costs extra memory (KV cache). A text-only mode (--language-model-only) saves memory because the image encoder is skipped. According to the source, there are no GGUF files, so running it with Ollama or on a Mac isn't directly supported right now. Without a big GPU, the model is unsuitable for Google Colab. Plan for about 70 GB of disk space for the weights.

Our take

Sage-A1.5 shows that open models in the 35B class are closing the gap on agent tasks against far larger systems, at least on the selected benchmarks. The subagent mode lifts BrowseComp from 81.7 to 82.8 and DeepResearch-Bench2 from 43.7 to 47.5, a concrete, measurable gain from orchestration. A note of caution: all figures come from the developers, partly with borrowed third-party values and inconsistent conditions. The benchmark selection is broad, but on several tests the big models are clearly ahead, and the predecessor sometimes does better. How well the model works day to day also depends heavily on your own harness, since you have to provide the orchestration yourself. For researchers and developers of agent systems, it's an interesting, freely usable starting point.

Sources

#sage-a1.5#agents#moe#open-weights#science
Read the original source

Try it yourself: Sage-A1.5

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

What can I do with it?

Sage-A1.5 is an agent model that can run locally as an API server. It researches with tools, writes code, answers scientific questions, and can split tasks across parallel subagents or check its own work.

Who is it worth it for?

Worth it for developers and researchers building their own agent systems with open models. Probably not for plain chat users without a big GPU or server experience.

Size36 B parameters (3 billion active)
Download22 GB (about 29 min at 100 Mbit/s)
Licenseapache-2.0
TypeImage + text (understands images)

What your computer needs

Graphics card (NVIDIA), fully in VRAM at least 25 GB VRAMe.g. RTX 5090 – fastest; with less VRAM, see the next line
Graphics card + system memory (MoE offloading) from approx. 6 GB VRAM + 32 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) from 36 GB unified memoryThe GPU and CPU share the memory – the model can use about 70% of it
CPU only (no graphics card) Runs smoothly without a graphics cardan estimated 12 words per second on a current desktop PC (MoE: only 3 billion parameters active per word). This requires at least 32 GB of RAM.
Storage approx. 24 GB freeModel download plus programs
Google Colab Colab Pro onlywith MoE offloading on a T4/L4 plus a High-RAM runtime (about 51 GB of RAM); free Colab doesn't have enough RAM

Only the Transformers weights (safetensors) are available. With about 24 GB of VRAM, only a quantized variant is realistic. Otherwise you need a card with around 80 GB or several GPUs. According to the source, there are no ready-made GGUF files.

  • The example commands use vLLM with one GPU and 262K context; long context costs extra memory (KV cache).
  • With --language-model-only, the image encoder is skipped and memory is saved.
  • 512K context requires YaRN with factor 2.0 and needs more memory.
  • Approximate memory needs: 4-bit about 20–24 GB, full precision around 70 GB (estimate).
  • No GGUF available, so CPU or Apple Silicon use isn't directly supported.
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: Colab Pro only – needs an A100 with 40 GB.

  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 11 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/InternScience/Sage-A1.5-Q4_K_M-GGUF:Q4_K_M
    The first time, Ollama downloads the model (22 GB (about 29 min 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.
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/InternScience/Sage-A1.5-Q4_K_M-GGUF:Q4_K_M
    The first time, the model is downloaded (22 GB (about 29 min 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/InternScience/Sage-A1.5-Q4_K_M-GGUF:Q4_K_M
    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

Research the populations of New York, Los Angeles and Chicago in parallel and cross-check the figures.
Explain step by step how I can find the bug in my Python date-parsing function, and suggest a fix.
Summarize the state of research on solid-state batteries in a structured report with open questions.

If something goes wrong

Use Python 3.12 and recent vLLM or SGLang versions (vLLM from the main branch), otherwise the architecture may not be recognized.

Set the parser options --reasoning-parser qwen3 and --tool-call-parser qwen3_coder, otherwise reasoning and tool calls won't work properly.

Verification mode needs a non-empty system message and a JSON boolean true, otherwise you get a 400 error.

Subagents only work if your harness actually executes spawn_subagent.

“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: apache-2.0.

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.