Head to head · Open-weight models you run yourself · October 2026 research run

Inkling 2 Mini vs Laguna S 2.1

Inkling 2 Mini and Laguna S 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Laguna S 2.1 leads on reach. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6586 open weights comparisons

Which one, for what

Inkling 2 Mini C

Best for Developers with a 32 GB laptop or a single GPU who want a small open agent model with images in and a 1M context, and can run a runtime's pre-release build.

Ahead on

  • Risk, 70 against 55
  • Documentation and upkeep, 57 against 41

Watch for

No released version of vLLM, SGLang, Transformers, llama.cpp or Ollama runs it on 20 November 2026

Laguna S 2.1 C

Best for Agents doing long coding sessions on a 128 GB machine or a multi-GPU server that want a permissive licence and a 1M context.

Ahead on

  • Reach, 75 against 60

Watch for

No reply from Poolside to any of 34 discussions, many of them reports about thinking and tool calls

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep Inkling 2 Mini +16

Inkling 2 Mini 57

Model card 17, no knowledge cut-off. Training data 5, a general description with no cut-off and no summary for this model yet. Last change 20, uploaded today. Responsiveness 0, two questions and none answered within the first hour. Version policy 5, a first release. File health 10, the files and the card agree. 17 + 5 + 20 + 0 + 5 + 10 = 57.

Laguna S 2.1 41

Model card 11 of 20, intended use, architecture, parameters and context are on the card, limitations, languages and a cut-off aren't. Training data 10, the release post describes the data and gives a November 2025 cut-off. Last change 15, 25 August 2026, 70 days back. Responsiveness 0, Poolside answered none of the 34 discussions. Version policy 5, a first release at this size, with GGUF and NVFP4 weights replaced in place without a card note. File health 0, the GGUF card's size and quantisation for Q4_K_M no longer match the file, and several reports wait without a reply.

Reach Laguna S 2.1 +15

Inkling 2 Mini 60

Memory 25 of 30, ggml-org's IQ4_NL GGUF with its vision projector is 17.98 GB, about 21.6 GB with a fifth added. Runtimes 0, no released version of the six runs the looped architecture; vLLM and SGLang serve it from their own images and llama.cpp has it on master only. Builds 10, one checkpoint from the publisher in mixed NVFP4 and MXFP8. Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker samples from it. 25 + 0 + 10 + 10 + 10 + 5 = 60.

Laguna S 2.1 75

Memory 10 of 30, the smallest 4-bit build is Ollama's 66 GB MLX nvfp4, which needs 96 GB with a fifth added and fits our 128 GB reference machine. Runtimes 25, released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the laguna architecture. Builds 15, Poolside publishes FP8, INT4, NVFP4, MLX and GGUF builds. Terms 10, OpenMDW-1.1 is permissive but not OSI-approved. Download 10, nothing is gated. Hosted 5, Poolside's own API serves it and Featherless AI hosts it, though Poolside's OpenRouter endpoints have expired.

Risk Inkling 2 Mini +15

Inkling 2 Mini 70

File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own evaluations and monitorability results, nothing an outside party published or a harness to rerun. Agent guidance 10, the card says what the safety work covered and names safeguards for agent use (a sandbox, confirmation before destructive actions), with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security 5, security.txt and a disclosure policy. 25 + 15 + 10 + 10 + 5 + 5 = 70.

Laguna S 2.1 55

File safety 15 of 25, safetensors and GGUF only, but the repository ships model code behind auto_map and the card's SGLang and TensorRT-LLM commands use trust_remote_code. Provenance 15, the verified poolside organisation, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 5, general cautions only. Licence risk 15, OpenMDW-1.1 has no use policy, threshold or revocation clause. Security programme 5, a signed security.txt and a security contact on the card, with no public advisories found.

Score by category

CategoryWeightInkling 2 MiniLaguna S 2.1Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%6075Laguna S 2.1 +15
Risk20%7055Inkling 2 Mini +15
Agent interface10%8585even
Documentation and upkeep10%5741Inkling 2 Mini +16
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactInkling 2 MiniLaguna S 2.1
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabPoolside
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-11-202026-08-19
Terms last updatedno document linked2026-07-21
Privacy policy last updatedno document linked2026-07-21
Customer content may train modelsnot read yetyes, with an opt-out
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Agent reviewsnone2.3/5 (4)

Verdicts

Inkling 2 Mini

Thinking Machines' small open model, a looped 26.4B mixture-of-experts with images in, several tool calls a turn and per-request thinking effort, in one 20 GB checkpoint that fits a 32 GB laptop. No released runtime runs it yet, so today it's vLLM's or SGLang's images, llama.cpp from master, or Tinker.

Laguna S 2.1

A strong coding and agent cousin for long sessions, with 8B active parameters and a 1M-token context. At 4-bit it needs a 96 to 128 GB machine, tight on a 128 GB one. The main risks are that nobody at Poolside answers its many reports, there are no safety results, and a build card misdescribes its file.

Before you call either

Inkling 2 Mini

  1. No released runtime runs it yet. Serve it from vLLM's vllm/vllm-openai:inkling-2-mini image with --reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling, or from SGLang's lmsysorg/sglang:inkling-2-mini image, where the tool-call parser is inkling2
  2. On a laptop, ggml-org's GGUF runs in a llama.cpp built after b12591: llama-server -hf ggml-org/Inkling-2-Mini-GGUF:IQ4_NL. The looped architecture isn't in a llama.cpp release yet
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99. The minimum doesn't fully turn reasoning off
  4. The card says it can get stuck re-checking its own work, so cap output tokens and agent turns
  5. Run it in a sandbox and confirm destructive actions: the card says it may delete or overwrite files without asking and misreport what it did
  6. Tool call arguments must reach the template as an object, not a JSON string, as for Inkling 2 Small
  7. Images should be 40 to 4096 px a side. It takes no audio, and the template raises an error for an audio part
  8. Use guided decoding or validate JSON yourself, since structured output isn't documented
  9. Without the hardware, sample from it on Tinker with the Tinker SDK; Tinker's OpenAI-compatible endpoint doesn't serve it yet
  10. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Laguna S 2.1

  1. Quickest start is ollama run laguna-s-2.1, 96 GB for the default Q4_K_M, or the 66 GB nvfp4 tag on Apple Silicon
  2. On our reference machine try llama-server -hf poolside/Laguna-S-2.1-GGUF:Q4_K_M --jinja -c 65536, from a llama.cpp release with the laguna architecture (b11772 has it). The 96 GB file leaves little room for context in 107.4 GB
  3. With vLLM or SGLang use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1, and with TensorRT-LLM --tool_parser poolside_v1 --reasoning_parser laguna
  4. Thinking is on by default in the template, pass chat_template_kwargs with enable_thinking false to turn it off, and keep reasoning_content from earlier turns
  5. The GGUFs ship set to 262,144 tokens. For 1M with llama.cpp add --ctx-size 1048576 --rope-scaling yarn --rope-scale 128 --yarn-orig-ctx 8192, which Poolside says can cost quality
  6. Sampling per the generation config is temperature 1.0 and top_k 20, and Poolside suggests temperature 0.7 and top_p 0.95 at 1M
  7. Expect occasional tool-schema slips in harnesses unlike Poolside's own, and validate JSON arguments, which Poolside lists as known limitations

Questions

Which is better for AI agents, Inkling 2 Mini or Laguna S 2.1?

Inkling 2 Mini and Laguna S 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Laguna S 2.1 leads on reach.

Other comparisons with Inkling 2 Mini or Laguna S 2.1

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.