Getting started

Watch it work

Every command llamay has and every flow worth seeing end to end, recorded as it ran. Nothing here is a mock-up: each one is a pseudo-terminal, a real binary and the output it actually produced, on a machine this page names.

How these were made, and what that is worth

A demo is a claim about what a program does, and a claim is only worth what produced it. These were produced by scripts/site/record_demos.py, which runs the command you are reading and records the bytes that came back, at the times they came back. Re-running it re-records all of them.

Three things in each recording are synthesised and everything else is real, which is the same disclosure the script carries at the top of its own file:

• The prompt. ~/llamay $ is not anybody's shell. A recording of a real one is a recording of its theme, its git branch and its aliases, none of which are llamay.
• The typing. Characters arrive at a human-ish rate because a command that appears all at once reads as a screenshot. The string being typed is the string that ran.
• The comment lines. They are captions wearing a #.

The output is not touched. It is not re-ordered, not trimmed to look faster, and not typed back in afterwards. Where a command failed it was recorded failing — a snapshot refusing the wrong weights, a request without a key and four errors in a row are demos here for the same reason the throughput page has a column llamay loses: the refusal path is the one people deploy without checking.

The player

These are recordings, not video. Each one is an asciicast — a few kilobytes of JSON — replayed by a terminal emulator in /assets/cast.js that llamay.com ships itself. That choice buys three things a <video> tag cannot:

• The text is text. Select it, copy it, search it with the browser's own find, let a screen reader walk it. A demo of a command-line tool whose output you cannot copy is a poster of a command-line tool.
• It is small. Thirty-five sessions come to about four hundred kilobytes in total, fetched only when you scroll to one. The equivalent in MP4 is a hundred times that.
• It diffs. A recording is a text file in the same repository as the code it records, so a command whose output changed shows up in a diff rather than in a screenshot somebody has to notice is stale.

Space plays and pauses, the arrow keys seek five seconds, 0 returns to the start, and copy puts the session's commands — without the prompts or the output — on your clipboard. Below each player is the whole session as plain text, which is what the page is when JavaScript does not run.

Getting started

Generating

Models

The state engine

Serving

Correctness

Building with it

Running these yourself

Every one of them is a command you can paste. The models are ordinary downloads — llamay pull qwen2.5:0.5b, llamay pull gemma2:2b, llamay pull all-minilm:latest — and the files under testdata/ ship with the source. The recording script itself is the last word on what each demo does:

# what there is
python3 scripts/site/record_demos.py --list

# re-record one of them
make demos DEMO=ctx-fork

# re-record all of them, which takes about a quarter of an hour
make demos

The casts are committed, so the site never depends on a recording machine being available at deploy time. make site-check proves the HTML on disk is what the generator emits from them; make demo-check proves every demo a page references has a recording and that none of them recorded a failure.