lightsout status
Show what lightsout sees in this repo: config, harness, packs, any run still parked — and, for one run, what it is doing right now.
lightsout status
When to reach for it
Run it when you come back to a repo and need to know what lightsout thinks is going on. It names the config, the harness, the packs in play, and any run still parked. Name a run and it shows what is happening inside that run instead: its steps, their outcomes and durations, and what it is working on this moment. Name a branch with --shipping to follow it while it ships. Pass --queue while a queue drains to see every ticket on its board and what each active one is doing. Pass --now to see the run that is going right now, printed once.
How to run it
lightsout statuslightsout statusone run in detail; --watch repaints it every two minutes, and without --run it follows the one run that is goinglightsout statusthe run that is going, printed once; a phased plan shows its phase sequence and the phase moving nowlightsout statusone plan's planning steps, printed oncelightsout statusone branch's ship steps, read from the checkout that ships itlightsout statusthe queue's board, then one status block per active ticket, printed once| flag | meaning | left out |
|---|---|---|
| --run <id> | Show one run in detail — its steps, their outcomes and durations, what it is doing now. Takes the shortened eight-character id reports print. | Every run is listed, one line each. |
| --watch | Repaint the detail block every two minutes until the run stops, so a detached run can be followed. Without --run it follows the one run that is going, and its phase children with it; when several unrelated runs are going it names their ids and asks for --run <id> instead of guessing. | The block is printed once. |
| --now | Show the run that is going, printed once and never repainted — for a phased plan, its phase sequence followed by the phase moving now. It answers at once rather than waiting for a run to appear; with nothing going it falls back to the newest run of any status, and when several unrelated runs are going it names their ids and asks for --run <id> instead of guessing. Cannot be combined with --run, --watch, --planning, --shipping or --queue. | required |
| --planning <name> | Show the named plan folder's planning steps — verify-facts, draft, dedup, grade, publish — with their outcomes, attempts and durations, and what is running now. Cannot be combined with --run or --watch. | required |
| --shipping <branch> | Show the branch's ship steps — integrate, push, pull-request, checks, merge, sync — in the run block's layout, printed once, read from the record in the checkout --cwd names. Cannot be combined with --run, --watch or --planning. | required |
| --queue | Show the queue's seven-column board — Parked, Blocked, Build Queue, Building, Ship Queue, Shipping Now, Shipped — with one ticket ID in each cell and each ticket's title and reason listed under it, then one block per active ticket, each exactly what --run, --planning or --shipping prints for that ticket's worktree. Printed once. Cannot be combined with --watch, --planning, --shipping or --now. | required |
| --run <id> | The queue run to show — a past or crashed one included. Takes the shortened eight-character id reports print. | The live queue run this checkout's run lock names. |
| --wait | Wait up to a minute for a queue run to take the lock, for a status request made right after launching a queue — the queue has not taken the lock yet, and without this the answer would be that no queue is going. | A bare --queue answers at once. |
| --cwd <path> | Repository to report on. | The process working directory. |