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

Laguna S 2.1 vs SmolLM3-3B

Laguna S 2.1 and SmolLM3-3B score within a point of each other on agent readiness, 61 (C) and 61 (C). SmolLM3-3B leads on reach, risk and documentation and upkeep. Both do open-weight models you run yourself.

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

Which one, for what

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

  • Agent interface, 85 against 80

Watch for

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

SmolLM3-3B C

Best for Agents that want a small, fully transparent tool-calling cousin on a laptop, CPU or edge device

Ahead on

  • Reach, 85 against 75
  • Risk, 65 against 55
  • Documentation and upkeep, 54 against 41

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.3 out of 5

Watch for

65,536 tokens trained; 131,072 needs a YaRN edit to config.json

Score by category

CategoryWeight this runLaguna S 2.1SmolLM3-3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257585SmolLM3-3B +10
Risk20%205565SmolLM3-3B +10
Agent interface10%108580Laguna S 2.1 +5
Documentation and upkeep10%104154SmolLM3-3B +13
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactLaguna S 2.1SmolLM3-3B
KindOpen-weight modelOpen-weight model
VendorPoolsideHugging Face
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceOpenMDW-1.1Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-192025-09-10
Terms last updatedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.3/5 (4)3.3/5 (4)

Verdicts

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.

SmolLM3-3B

A tiny, fully open cousin with documented tool calling and switchable thinking, for local subtasks and routing on laptops and CPUs. It needs about 8 GB in BF16, or under 3 GB in Hugging Face's 4-bit ONNX build for ONNX Runtime. The main risks are a 64K native context, no safety results and no repository changes since September 2025.

Before you call either

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

SmolLM3-3B

  1. Start it with vllm serve HuggingFaceTB/SmolLM3-3B --enable-auto-tool-choice --tool-call-parser=hermes, or tool calls come back as text
  2. Pass chat_template_kwargs with enable_thinking false for short tasks, since thinking is on by default; a /think or /no_think flag in the system prompt overrides the kwarg
  3. Put earlier tool calls in the assistant message content, since the template ignores a tool_calls field when it renders history
  4. Add the YaRN rope_scaling block (factor 2.0, original 65536) to config.json before sending more than 65,536 tokens
  5. Use temperature 0.6 and top_p 0.95, the card's recommended sampling
  6. Needs Transformers v4.53.0 or later; for llama.cpp use a GGUF from ggml-org or another converter, since Hugging Face publishes none
  7. Validate JSON output yourself or use the runtime's guided decoding

Questions

Which is better for AI agents, Laguna S 2.1 or SmolLM3-3B?

Laguna S 2.1 and SmolLM3-3B score within a point of each other on agent readiness, 61 (C) and 61 (C). SmolLM3-3B leads on reach, risk and documentation and upkeep.

Other comparisons with Laguna S 2.1 or SmolLM3-3B

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.