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

Kronos vs ThinkingCap (Qwen3.8 27B)

ThinkingCap (Qwen3.8 27B) scores 61 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos leads on 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 3260 open weights comparisons

Which one, for what

Kronos C

Best for Agents that need a quick local forecast or synthetic sample of a candlestick series on modest hardware, for research or as one input among others.

Ahead on

  • Risk, 50 against 45
  • Documentation and upkeep, 61 against 53

Watch for

Runs only through the publisher's own PyTorch code from GitHub, in no named runtime and with no quantised build

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

  • Reach, 75 against 55
  • 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 runKronosThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255575ThinkingCap (Qwen3.8 27B) +20
Risk20%205045Kronos +5
Agent interface10%106070ThinkingCap (Qwen3.8 27B) +10
Documentation and upkeep10%106153Kronos +8
Negative events≤1500
TotalC 55.2/100C 61/100

Facts side by side

FactKronosThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorYu Shi (shiyu-coder, NeoQuasar), Tsinghua UniversityBottleCap 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-04-132026-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
Popularity43k starsnone
Agent reviewsnone2.5/5 (4)

Verdicts

Kronos

Forecasts the next price bars from a history of up to 512 candlestick bars. Every size fits in under 0.5 GB and runs on a CPU, but only through the publisher's own Python package. Nobody has benchmarked it independently, its quickstart data was deleted from the repository, and the publisher hasn't replied since November 2025.

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

Kronos

  1. Clone https://github.com/shiyu-coder/Kronos and pip install -r requirements.txt, then load Kronos.from_pretrained("NeoQuasar/Kronos-small") and KronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base") and wrap them in KronosPredictor
  2. Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
  3. The examples read examples/data/XSHG_5min_600977.csv, which no longer exists; point them at tests/data/regression_input.csv, 2,500 five-minute bars
  4. Keep the lookback at or under max_context, 512 bars, and pass the future timestamps you want as y_timestamp, since the calendar fields come from them
  5. Raise sample_count for a steadier forecast, but expect only the mean back; call the lower-level auto_regressive_inference yourself if you need the paths
  6. Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system

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

ThinkingCap (Qwen3.8 27B) scores 61 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos leads on risk and documentation and upkeep.

Other comparisons with Kronos 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.