Design the last line of your terminal.
Drag tiles onto a drawing sheet, style them, and tell them how to behave when the window gets narrow. Export one config file and the same layout renders into Claude Code, into tmux, and into the browser preview — from one engine, so the preview can't drift from what you see at 2am.
68 tiles · 26 signals · 20 CLI commands · MIT licensed
Parts list on the left, drawing sheet in the middle, inspector on the right.
68 tiles across six groups, ten starter bundles to open from, and a layer schedule that keeps track of which breakpoint you are looking at. Nothing is nested more than one level deep.
Drag a tile out of the parts list and it is on the bar.
Drop position sets the order. Every tile carries its own defaults, so a bar is usable before you have styled anything — then you select one and start turning knobs.
Every tile has a priority. Narrow the window and the solver drops whole tiles.
It never wraps and never truncates mid-tile. Borders cost real columns and the solver counts them. Drag the handle below — this is the same ranking the CLI applies when it renders for real.
Same solver, driven by an actual window.
Pull the width handle in the builder and tiles leave in priority order, then come back in the order they left. Nothing is clipped in half on the way through.
Design it once. The preview is not a mockup of the output — it is the output.
The three targets do differ in what they can physically do, and the builder tells you which while you're designing rather than after you install.
Fifteen fill modes, seven border edges, five themes.
Colour is per tile or for the whole bar, with named palette entries defined once on the sheet so re-theming is a single edit. Every fill is quantised and emitted one escape per cell.
A tile can change colour, grow a border, or blink when something is wrong.
Up to twelve rules per tile, layered — later rules win, so a general rule takes a specific override. Blink is derived from the clock, not the terminal's blink attribute, so it looks identical everywhere.
ci.failingci.passingci.runningpr.approvedpr.changespr.pendingpr.openreview.waitinggit.conflictgit.dirtygit.cleangit.aheadgit.behindcontext.abovefivehour.abovesevenday.abovecost.abovecpu.abovemem.aboveswap.abovedisk.aboveload.abovegpu.abovevram.abovebattery.belowalwaysA tile can also stay hidden until it has something to say, and a firing rule can escalate past the hide rules.
Forty-eight seconds, one take, no cuts.
Two tiles dragged in, a border added, a flowing gradient turned on and cycled through five modes, then the width pulled down until the bar sheds three tiles and takes them back.
Three steps, and one of them is optional.
Build the layout in the browser, then hit Copy install. The config travels as a single base64 blob.
statusline export
Writes the config and patches ~/.claude/settings.json — it shows you a diff rather than overwriting blindly.
statusline import <blob>
Optional. Prints the .tmux.conf snippet with the mouse binding already included.
statusline tmux-conf
No. tmux is a first-class target on its own, and the web preview runs anywhere. Claude Code just gets the extra rows and the OSC 8 links.
The daemon. statusline daemon samples cpu, memory, swap, disk, load, network, gpu and vram off the render path, and statusline doctor tells you if it is not running.
No network calls on the render path — that is architectural, not incidental. Every tile declares a cost tier, the daemon does the sampling, and the renderer reads a cache.
Commands are argv arrays, never shell strings, and any command a config wants to run has to be approved against its exact arguments first. Editing the command revokes the approval.
Set the colour depth to ansi256 or ansi16 and the engine quantises to it. The 16 colour theme exists for exactly this.
Yes — as declarative JSON manifests with no code execution. statusline search and statusline add pull them from the registry, http-only, shown to you before install.