Guided first run
Checks your machine, picks a model size that fits it, helps you get text, and walks you to a working model. Every step can be skipped.
Haiku Studio
BY ROOTCOMPUTER
GitHub
Haiku Studio runs the whole pipeline locally: build a tokenizer from your text, pretrain a model, fine-tune it to hold a conversation, align it on the replies you liked, and chat with the result. Nothing is sent anywhere. There is no API key.
0001 LOG [cache] 1,341,882,304 tokens (3.87 bytes/token)
0002 LOG [eval] step 18000 val 2.44 ppl 11.5 ** new best
0003 WARN [plan] 2.1 passes over corpus at this budget
Most of the work in training a small model is knowing whether a run is worth starting. Haiku Studio answers that before you commit hours to it, not after.
Checks your machine, picks a model size that fits it, helps you get text, and walks you to a working model. Every step can be skipped.
Before a run starts you see the model size, the tokens it needs, the passes over your corpus that implies, and whether it can work at all.
Catches the classic trap where pip install torch silently gives you the CPU-only build, before you lose a week to it.
Learn a byte-level BPE vocabulary from your own corpus, with proper control tokens so replies begin and end cleanly.
Pretraining, supervised fine-tuning and DPO alignment, with resumable checkpoints. Stop any run and it picks up exactly where it left off.
Streaming replies from your model, with a stop button that actually stops. Rate replies with thumbs and they become alignment data.
Download prepared corpora straight into your project. Checksum-verified, and resumable if your connection drops mid-transfer.
Pick CPU, a specific GPU, or Apple Silicon. Asking for a device that is not there raises an error instead of quietly using the CPU.
Everything the app does is available as python -m haiku.cli. The desktop app is a front end, not a wall.
Five presets, from something that trains on a laptop CPU in minutes to a model that will take a good GPU several days. The app recommends one based on your hardware.
“Text it wants” is the compute-optimal ratio of roughly 20 tokens per parameter. You can train well past it, and for small models you probably should — the budget dial goes to 200×, which is where small models start to feel capable. Higher ratios need proportionally more text and time, and the app computes both before you commit.
Corpus, tokenizer, config, checkpoints, cache and logs. Switching projects switches all of them together.
Text present, tokenizer built, budget checked. Training will not start until the prerequisites are actually met.
Stop whenever you like. Resume restores the optimizer, the random state and the exact sample it left off at.
Every tab maps to a real stage of the engine, and every number on screen comes from the run itself rather than an estimate.
0001LOG[cache] train 1,331,204,096 · val 200,000 tokens
0002LOG[eval] step 18000 val 2.44 ppl 11.5 ** new best
0003WARN[plan] only 2.1 passes over corpus at this budget
0004ERR[device] cuda requested but PyTorch sees no GPU
Replies stream token by token from a model held in memory, so the first word arrives in milliseconds rather than seconds.
Download the release, or clone the repository and run the Python engine directly. Both give you the same thing — the desktop app is a front end over the command line, not a separate product.
No Windows installer yet. 2.0 ships as source; a packaged installer is coming. You will need
Python 3.10+ and Node.js LTS. Install PyTorch first from
pytorch.org —
a plain pip install torch gives you the CPU-only build on Windows, even with an NVIDIA card.
The built-in environment check will tell you which one you actually have.