Segments

The eleven pieces the bar is built from, and when each one sits out.

The bar is rows of segments, and the rows are yours. lines in your config is an ordered list of rows; each row is an ordered list of segment ids. The shipped layout is two rows:

{
  "lines": [
    ["model", "context", "rl5h", "rl7d", "spend", "cost"],
    ["project", "worktree", "branch"]
  ]
}

Mix and match freely. A row that ends up with no visible segments is dropped rather than drawn empty, which is why the second row disappears entirely outside a git repository.

The catalogue

Eleven segments. {sym.x} below is the glyph configured under symbols, and every · is one literal space — the renderer adds one more on each side of the whole text.

Three of those have a detail worth knowing:

• The rate-limit segments show the reset half only when the reset time is known; the percentage alone renders otherwise.
• context always renders, even with no data at all — as {sym.context}·▱▱▱▱▱▱▱▱▱▱·?/?·(0%).
• branch carries the branch glyph, then the name. Three things around it are conditional: the worktree glyph appears before the branch glyph only when you are inside a worktree, and the ↑ (ahead of upstream) and ± (dirty) markers follow it. Each is preceded by exactly one space. Dirty is + for additions only, - for deletions only, ± for both. So an ordinary checkout renders {sym.branch}·main, and the same branch inside a worktree renders {sym.worktree}·{sym.branch}·main.

Where project comes from

Never from the session payload. The name is the first of these that exists:

1. projectName in the repository’s own <repo-root>/.config/claude-status.json.
2. projectName in your user config — which is not inert, and names every repository that has not named itself.
3. The git root’s directory name.

So the segment draws by default, and naming a repository is only how you call it something other than its directory. Outside a git repository there is no root, and the segment sits out. See Per-repo.

Why spend is missing

Four gates hide it, checked in this order:

1. spend is not in your lines.
2. There is no usable cached figure yet.
3. The budget is unusable — either disabled, or a limit of zero. (A missing budget block is gate 2, not this one.)
4. The seat is one that show: "auto" hides. auto shows the segment only for team and enterprise seats, so every other plan — and any cache with no plan recorded at all — is hidden here. Much the most common answer.

--debug reports all four and tells you which one applied. More on the segment in Configure.

Getting an id wrong

Typo a segment id and you get a note on stderr and a bar without it. The render does not fail, the exit code stays 0, and stdout is only ever the bar:

statusline: unknown segment "brnach"

Styling one

Every segment takes bg, fg and bold, resolved inline override → segments.<id> → the built-in fallback:

{
  "segments": {
    "branch": { "bg": "aqua" },
    "cost": { "bg": "green", "fg": "white", "bold": true }
  }
}

Or, for one position only, put an object in the row instead of a bare id:

{
  "lines": [
    ["model", { "name": "cost", "bg": "red" }]
  ]
}

Colours are covered in Configure.