Slices are specialist AIs.
The labs name models. We name the work. Five slices are named
for what you want from the model, six for the job, and you call any of them with one
word after toast: nothing to install, nothing in your bin,
a new slice is live the day it exists. Each reads stdin, takes a prompt, and prints —
so toast reviewer goes anywhere toast does.
Whatever is best right now. The name never goes stale; the model behind it changes when the leaderboard does. also: toast sota
cat draft.md | toast best "is this any good?"
Lowest latency available. For the terminal, the chat, anything you are waiting on.
git diff | toast fast "commit message"
The cheapest that will do. For the forty-times-a-day calls and the loops that run overnight.
20 while toast cheap notes.md "next source"
This machine, nothing leaves. The house computer's slice, and the honest answer to "where does my data go." also: toast private
rem | toast local "what's urgent?"
Reads the whole thing. A 300-line notes file, a book, a day of logs, without complaint.
toast long "what is in notes.md"
What is this? Errors, logs, code, a PDF. The most-typed word on this page.
cat error.log | toast explain
Given a file and a sentence, changes the fewest lines that do the job, and saves it with a reason.
toast coder deploy.sh "add a rollback on a failed health check"
What breaks in production, and what would embarrass you. Two reviewers that never saw the prompt. Paranoid and Security, both
cat deploy.sh | toast reviewer
Cuts. Says what is slack and where the reveal should go.
20 while toast editor ch4.tex "cut until nothing is left to cut"
Into any language the labs speak, which is most of them. The glossary lives in .crumbs so names stay put.
cat ch4.md | toast translator "into German"
Answers from the docs, forwards billing to a human. Friday's email bot.
email bot toast support "answer from docs.html"
Behind the names, all of them. A slice resolves to the weights of
whichever lab serves that job best this week, on the host that serves them best.
Want a particular lab? Each has a nickname — toast kimi, toast gpt —
and the nickname means that lab's best model today; it changes when theirs does:
Anthropic, OpenAI, Google, xAI, Moonshot, DeepSeek (two, six-fold apart in
price), Alibaba, Zhipu, Mistral, Meta — and Apple's on-device models when the answer is
local. Hosts include the labs themselves, Cerebras, and your own machine.
toast -l lists what each name resolves to this week, with the lab and the
price beside the id; -m and an id pins one model. A model name is only the
weights; who serves them decides the speed, the price, the retention and, quietly, the
quality. The receipt tells you which.
$ toast editor ch4.tex "what's slack in this chapter? one paragraph" The inn scene restates what the ledger already showed. Cut it, or move the reveal there. $ toast reviewer auth.py "what breaks in production?" The refresh check races. Two requests inside the 30 second window both mint a token; the second overwrites the first and the client retries with one that no longer validates. $ toast kimi "what is in notes.md" [toast] cat notes.md A structured list of figures with sources and dates from four sites, six flagged contradictions, and three Crunchbase URLs that were blocked.
The first word after toast picks a server-side configuration;
the rest is the prompt. A first word with a period in it, or that exists as a file, is a
file, and a quoted sentence is a prompt — toast keeps no list; the letters go to the server. Behind the name is whatever solves
that problem best right now — a model from any lab, one we trained, or a combination —
and it changes when something better appears. Your pipeline does not. Slices use your
.tools and .crumbs like toast does; only the voice comes from
our side. Plain toast uses your .persona instead, and only one
of them is ever read, so they cannot fight. Prefer one word? toast --add editor
makes a symlink, and editor alone means toast editor.
