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

Laguna S 2.1 vs ThinkingCap (Qwen3.8 27B)

Laguna S 2.1 and ThinkingCap (Qwen3.8 27B) score within a point of each other on agent readiness, 61 (C) and 61 (C). ThinkingCap (Qwen3.8 27B) leads on 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

  • Risk, 55 against 45
  • Agent interface, 85 against 70

Watch for

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

ThinkingCap (Qwen3.8 27B) C

Best for Small teams and individuals running Qwen3.8-27B for agent or reasoning work who want shorter thinking traces on one 24 GB GPU or Mac.

Ahead on

  • Documentation and upkeep, 53 against 41

Watch for

PolyForm Small Business licence, free commercially only below 100 people and 1,000,000 USD (2019) revenue

Score by category

CategoryWeight this runLaguna S 2.1ThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257575even
Risk20%205545Laguna S 2.1 +10
Agent interface10%108570Laguna S 2.1 +15
Documentation and upkeep10%104153ThinkingCap (Qwen3.8 27B) +12
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactLaguna S 2.1ThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorPoolsideBottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceOpenMDW-1.1PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-192026-10-06
Terms last updatedno document linked
Privacy policy last updated
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)2.5/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.

ThinkingCap (Qwen3.8 27B)

A Qwen3.8-27B with shorter reasoning, for agent work where thinking tokens cost time, and BottleCap's 4-bit GGUF runs in about 19 GB. The main limits are the licence, which needs a paid licence above 100 people or 1,000,000 USD revenue, a gated main repository, and no safety results or training-data description.

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

ThinkingCap (Qwen3.8 27B)

  1. Check the licence first, an organisation with 100 or more people or 1,000,000 USD (2019) revenue needs a commercial licence from BottleCap
  2. For files without the gate use llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 17.4 GB
  3. On vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_xml, and on SGLang --tool-call-parser qwen3_coder
  4. Set reasoning_effort (xhigh, medium or low) in chat_template_kwargs, any other value makes the template raise an error
  5. Keep the base's sampling (temperature 1.0, top_p 0.95, top_k 20), the GGUF card says greedy decoding can loop
  6. The GGUFs carry an MTP head, and llama.cpp builds without MTP support for this architecture may refuse to load them with a missing blk.64 tensor

Questions

Which is better for AI agents, Laguna S 2.1 or ThinkingCap (Qwen3.8 27B)?

Laguna S 2.1 and ThinkingCap (Qwen3.8 27B) score within a point of each other on agent readiness, 61 (C) and 61 (C). ThinkingCap (Qwen3.8 27B) leads on documentation and upkeep.

Other comparisons with Laguna S 2.1 or ThinkingCap (Qwen3.8 27B)

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.