/oss:scaffold writes .oss/statusline.py as an owned file, and Claude Code renders its output
in the corner of the terminal. Every field is separated by |; a field this repository could not
measure renders ? rather than a guess, per this repository's own rule that a check which did not
run must never look like one that ran clean.
Left to right:
| field | example | means |
|---|---|---|
| model · context | Opus · 42% |
Claude Code's own session facts, passed straight through. |
| repo | claude-oss✓ main v0.15.0 |
repo name, glued to a glyph for whether the default branch's own head commit is currently green (✓/✗/⋯/?; #856), then the current branch (only when it is not the declared default) and the tracked version. |
| board | 4pr 2ok 1x 1... 0? · 23is / 2eis |
open pull requests, then a CI breakdown (green/red/running/unknown, every group shown even at zero), then open issues and how many of those arrived from outside repository membership. |
| unlabelled | 0np 1nl |
open issues carrying none of the declared priority labels (np), then open issues carrying none of the declared lane labels (nl) — reported separately, never summed. ? for an axis this repository declares no spellings for, or for a reading the forge could not take, same as every other cached count on this line. |
| release | rel 4/17 |
commits banked since the last release, over what a release here usually costs. Either half is ? on its own when only one could be measured. |
| trap | trap 3 |
.md fragments in trap.d/ waiting for /oss:curate (same filter as trap_curate.waiting, so .gitkeep and any other dotfile do not count). Read straight off the filesystem at render time, no forge call. A missing trap.d/ is a real 0; ? is only for a directory that exists and could not be listed. |
| inb | inb 2is 1pr |
how much of what arrived from outside is still waiting (#1406): open issues authored by someone outside repository membership, then open pull requests from the same population — both cached on the board's own clock, ? per count for a read that could not be taken, never 0. A third count (comments still needing an answer) is not shown here yet; see scripts/statusline.py's own inbound_reading docstring for why. |
| last | last 12:34 |
a wall-clock stamp of when this line was last rendered — frozen like the rest of the line between renders, but a frozen clock time stays readable against your own watch. |
| plugins | plug 3✓ oss↥0.15.0 1? |
how many of this repo's declared plugin dependencies are current, then each one that is not, named. ↥/> shows the latest published version behind a plugin marked behind; ↑/+ shows the version installed for one marked ahead — two markers that print two different fields, not two colours of the same one (#549/#550). ? counts a plugin whose version could not be compared at all. |
| ch | ch✓ / ch✗ / ch◐ / ch! / ch? |
whether supertool's watch channel is delivering — green when the consumer's counters are moving, red when nothing is listening, yellow (◐) when the consumer is bound but nobody is subscribed, ch! on a contradiction, ch? when nothing could be established. Set "watch_channel": false in .oss.json to turn it off — the field then disappears entirely rather than showing ch?, because an operator's deliberate off switch is not the same absence as a question this line asked and could not answer. |
| dr | dr✓ / dr◐ / dr✗ / dr? |
/oss:doctor's own last verdict (#1314), cached and detached on an hour-long clock — too expensive to run at render time, since one of its checks alone is documented past 20 seconds in its worst case. ✓ is a clean run, ◐ is usable with gaps (an actionable WARN survives), ✗ is not usable (a FAIL survives), ? is an absent or stale reading — never a guessed state. No off switch: unlike ch, this field always renders. A single false-positive WARN that nothing can clear pins this marker at ◐ permanently — that is a defect in the check that raised it, not in the repo it is raised against, and the marker only makes that standing alert visible on every render instead of only on a run nobody happened to make. |
Colour, where the terminal supports it, adds a second signal on top of the marker shape rather than replacing it — every state above is told apart by its glyph alone, in monochrome.
The repo field's marker maps gh-branch's own four states down to _symbols' four glyphs:
✓ for GREEN, ✗ only when a leg on the head commit has actually failed, and ⋯ for both
"still running" and NO RUN — nothing has concluded yet, including the moment right after a
merge, when the branch has a fresh commit and no run against it at all. ? covers UNKNOWN and
a reading older than its own refresh interval, folded the same way plug's own behind/ahead
comparison folds a stale one (#550) — a stale ✓ about a commit that may no longer be green is
worse than an honest ?. The marker is absent entirely, not ?, when .oss.json declares no
default_branch to compare against — a deliberate absence of the question, the same convention
ch's own off switch above uses.