Recording
Three ways to capture a session, depending on how much ceremony you want.
Interactive sessions
The default. rekord start wraps your shell and records everything until you press the stop hotkey (Ctrl-] by default).
$ rekord start --name api-debug ● recording session "api-debug" · press Ctrl-] to stop
Change the stop key per run with --stop-key ctrl-x, or set a persistent default in config (recording.stopKey).
Single commands
Skip the session entirely and capture exactly one command with rekord run. Everything after -- is the command to record.
$ rekord run --name k8s -- kubectl get pods -A ✓ recorded one-shot · 1 command · 0.4s
Timer mode
Hand-free demos: record for a fixed window, then auto-stop.
$ rekord start --name walkthrough --timer 5m ● recording · auto-stop in 05:00
Rekord records the command, output, exit code and timing as structured events — never a flat screen-scrape. That's what makes every export format possible from a single capture.
Interactive TUIs (vim, htop, full-screen menus) are captured as raw terminal output. They replay faithfully but don't decompose into clean command/output pairs.