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

Ling-3.0-tiny vs ThinkingCap (Qwen3.8 27B)

ThinkingCap (Qwen3.8 27B) scores 61 (C) on agent readiness against Ling-3.0-tiny's 55 (C), and leads in 1 of 4 scored categories. Ling-3.0-tiny leads on reach and risk. 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

Ling-3.0-tiny C

Best for Agents on a laptop or small GPU that want a fast local model for tool calls and short reasoning, under MIT

Ahead on

  • Reach, 90 against 75
  • Risk, 50 against 45

Watch for

No hosted provider today, and Ollama support is only an unmerged pull request

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

  • Agent interface, 70 against 60

Watch for

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

Score by category

CategoryWeight this runLing-3.0-tinyThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259075Ling-3.0-tiny +15
Risk20%205045Ling-3.0-tiny +5
Agent interface10%106070ThinkingCap (Qwen3.8 27B) +10
Documentation and upkeep10%105653Ling-3.0-tiny +3
Negative events≤1500
TotalC 55/100C 61/100

Facts side by side

FactLing-3.0-tinyThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)BottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITPolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-312026-10-06
Terms last updatedno document linkedno 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.8/5 (4)2.5/5 (4)

Verdicts

Ling-3.0-tiny

A small, quick hybrid reasoning cousin for local agent work, tool calls and coding, under MIT. It runs in about 6 GB from inclusionAI's 4-bit GGUF in released Transformers, vLLM, SGLang and llama.cpp, with no host. The main risks are a card that doesn't match the files in places, the vLLM route running repository code, and no model safety results.

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

Ling-3.0-tiny

  1. Start it with llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q4_K_M --jinja -c 32768, which needs llama.cpp b11772 or a recent release with bailingmoe3
  2. With vLLM 0.32.0, vllm serve inclusionAI/Ling-3.0-tiny --trust-remote-code --enable-prefix-caching --mamba-cache-mode align --enable-auto-tool-choice --tool-call-parser ling3 --reasoning-parser ling3, which runs the repository's config code
  3. With SGLang 0.5.22, its cookbook uses --reasoning-parser deepseek-r1 --tool-call-parser glm45 for this model, and drop the card's NEXTN flags since tiny has no MTP layer
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks
  5. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 20
  6. The template keeps earlier reasoning in the prompt, which grows long agent sessions
  7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
  8. For a guardrail, inclusionAI's Ling-3.0-tiny-singprobe scores intent, unsafe output and hallucination per token, but only through SGLang and vLLM integration branches

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, Ling-3.0-tiny or ThinkingCap (Qwen3.8 27B)?

ThinkingCap (Qwen3.8 27B) scores 61 (C) on agent readiness against Ling-3.0-tiny's 55 (C), and leads in 1 of 4 scored categories. Ling-3.0-tiny leads on reach and risk.

Other comparisons with Ling-3.0-tiny 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.