samuelfaj / distill

# Distill
Distill is a lightweight coding agent harness and TUI, built to **get far more done
with far fewer tokens.**
It works with Grok and Codex subscriptions, and with any model that speaks the
OpenAI-compatible protocol.
**Steps:**
1. Download distill.
2. Login with openrouter.
3. Login with your subscription.
4. Save money.
----
## Benchmarks
See BENCHMARKS.md for the full results tables, definitions,
methodology, cost bounds, reproduction commands, and source JSON.
## Install
### Mac / Linux
 [code] 
### Windows
 [code] 
## Upgrade
For an installation made with the release installer:
 [code] 
## Choose your models
Open **Model tiers** on the home screen, click **change** beside the current
model, or enter `/tiers`. You can edit each tier in that screen.
| Tier | Purpose | Picker |
|---|---|---|
| Main model | Required. Owns every session: it plans, specifies, delegates, and reviews the work. | `/model` or `/tiers main` |
| Worker model | Optional. Runs every delegated assignment the main model hands it as a precise spec. Without it, the main model does all the work. | `/worker-model` or `/tiers worker` |
| Utility model | Handles bounded tasks such as extraction, summaries, and compression. | `/utility-model` or `/tiers utility` |
Pick your strongest model as the main model and a cheaper one as the worker:
the main model gives the worker as much of the work as it can do well. Each
tier takes an effort level or `auto`, which lets Jev pick the effort for every
call; `auto` is the default. In the Model tiers screen, enter a tier as
`model effort` (for example `gpt-6-luna auto`). You can supply each selection
directly:
 [code] 
## Always-on behavior
Two rule sets are built into every system prompt, for the main model and for
its subagents, and neither has an off switch:
- **Caveman**: the agent writes terse prose and keeps code, paths and error
 strings exact. `/caveman lite|full|ultra` changes how hard it compresses
 (default `full`); a stored `off` is ignored.
- **Ponytail**: the agent works like a lazy senior developer. Before writing
 code it asks whether the code needs to exist, then reuses what the codebase
 has, then the standard library, then an installed dependency, and only then
 writes the minimum that works. Validation, error handling, security and
 anything you asked for are never cut. Adapted from
 ponytail (MIT).
### Read More:
- Accounts and local models
- How Jev routes work
- UltraCode activation, hierarchy limits and paired comparisons
- Where the token savings come from