The problem
Claude Code lets you point a status line at a shell script that receives session JSON on stdin and prints one line. People who want that line, and people on other tools asking for the same, write the script blind: guess the field names, pipe through jq, eyeball ANSI codes, restart, repeat. The Codex request for it has 220 reactions. The pain is not the idea, it is the feedback loop.
Why now
Terminal coding agents became a daily tool within a year, and each one is adding its own status hook. The JSON they emit is similar but not identical, so a visible, editable sample is more useful than another copy-paste gist. Developers are customising these lines right now, which is when they go looking for a tool like this one.
What it is
A two-pane composer. Tick the fields you want, order them, colour them, choose a separator, and the line renders at once against sample session JSON you can edit. The right pane holds the generated bash script and the settings.json block, with copy and download. Layouts save as presets in the browser. Nothing is sent anywhere and the script is not run in the page, so test it in your own terminal.
Who it's for
Developers comfortable with a shell who would rather click than learn jq paths. It is not for people who already keep a dotfiles status line they like, and not for anyone who wants a hosted, synced config: there is no account and no sync. Field names track one tool's documented JSON, so users of other tools must edit the sample and paths.
How it makes money
It does not, and that is right for now. A free utility earns its place by being the page people link in an issue thread. Charging for a snippet generator would lose to a gist. If it ever earns, the honest route is a sponsor line from a terminal or tooling vendor, not a paywall on a script.
Go to market
Answer the existing requests directly: post it in the Codex status-line issue and in Claude Code discussions where people paste half-working scripts, with a preset or two attached. Each reply reaches someone who had the problem that week. The first test is whether anyone returns to add a field, which tells us whether a field catalogue per tool is worth maintaining. The demo ships one tool's fields only.