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

Kronos vs Qwen3.5-4B

Qwen3.5-4B scores 61.2 (C) on agent readiness against Kronos's 55.2 (C), and leads in 3 of 4 scored categories. Kronos 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 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

  • Documentation and upkeep, 61 against 34

Watch for

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

Qwen3.5-4B C

Best for Agents that want a cheap local helper for tool calls, short reasoning and reading images on a laptop or small GPU

Ahead on

  • Reach, 85 against 55
  • Risk, 55 against 50
  • Agent interface, 70 against 60

Watch for

No quantised build from Alibaba for this size

Score by category

CategoryWeight this runKronosQwen3.5-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255585Qwen3.5-4B +30
Risk20%205055Qwen3.5-4B +5
Agent interface10%106070Qwen3.5-4B +10
Documentation and upkeep10%106134Kronos +27
Negative events≤1500
TotalC 55.2/100C 61.2/100

Facts side by side

FactKronosQwen3.5-4B
KindOpen-weight modelOpen-weight model
VendorYu Shi (shiyu-coder, NeoQuasar), Tsinghua UniversityAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-04-132026-03-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno 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 reviewsnone3/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.

Qwen3.5-4B

A small vision-language cousin for tool calls, light agent steps and image or video reading on almost any machine, with switchable thinking. Ollama's 3.3 GB build or the 9.3 GB BF16 files run in every major runtime under plain Apache 2.0. The main risks are no safety results, no structured-output guarantee and no answers from Alibaba since March.

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

Qwen3.5-4B

  1. Smallest start is ollama run qwen3.5:4b (Q4_K_M, about 4 GB with context)
  2. Full precision vllm serve Qwen/Qwen3.5-4B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 without thinking
  5. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  6. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, Kronos or Qwen3.5-4B?

Qwen3.5-4B scores 61.2 (C) on agent readiness against Kronos's 55.2 (C), and leads in 3 of 4 scored categories. Kronos leads on documentation and upkeep.

Other comparisons with Kronos or Qwen3.5-4B

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.