The status bar
The facts about this tab right now: which machine, which branch, how much context, whether you are connected, and what is waiting. On a phone they are one line above the composer. On a wide window they are two: the machine, the branch, the context and the ping on a row at the top of the composer, and what is waiting in the composer's key row. Every segment is a button.
Why you would use it
It is the fastest read of whether the thread is healthy, and the fastest route to the things it names — the sessions sheet, the changed files, the reason it is paused.
How to use it
- On a phone, look at the bar above the composer (
#statusbar). Every segment is on it. - On a wide window, look at the
top row of the composer (
#composer-facts): the machine, the branch, the context and the ping. What is waiting is in the key row (#composer-status), in the gap between the effort dial and the mic. Both report the pane they are in rather than the tab in front. - Tap any segment. Each one either says more, or opens the thing it is about. In a pane you are not typing into the segments are text, not buttons: the tap focuses the pane, and the box arrives with the bar you can tap.
What you see
Segments appear only when they have something to say, left to right. On a wide window the first four are the composer's top row and the rest its key row:
| Segment | Looks like | Tap does |
|---|---|---|
| Node | devbox |
Toasts the machine's name and URL |
| Git | ⑂ master*↑2 |
Opens the threads sheet |
| Context | ctx 162k |
Toasts the exact token count and the auto compact mark |
| Connection | ↑ 40ms (green) or ↯ offline (amber) |
Refreshes usage and workspace |
| Queued | ◷ 3 (amber) |
Toasts 3 queued |
| Needs you | ● needs you (red) |
— |
| Paused | ⏸ resumes 14:20 (amber) |
Toasts the full usage-limit line |
| Stopped | ⚠ stopped (red) |
Toasts why the agent stopped |
| Changes | a file icon, a count, +12 −3 |
Opens the changed-files popup |
The * on the branch means the working tree is dirty; ↑2 means two commits
ahead of upstream. ● needs you shows while an approval is pending. The node
segment and the VCODE_* variables behind it are in
machine-name.
Limits and known gaps
- There is no shell segment. Shell mode opens from the composer's mode chips, and a second door to the same room was removed.
- No cost segment. The dollar total is still accumulated server-side but is not shown: on a subscription plan it reads as a warning about nothing.
- The git figures come from
gitin the tab's folder and are best-effort: a folder that is not a repo, or a repo with no commits yet and no upstream, simply leaves the segment out rather than failing the request. ctxis this tab's context, not your plan usage. Plan usage is the meter row above the transcript.- Inside the composer the live line has the key row's spare track. A paused
thread that also has a queue and changes can still run past it: the last
segment is cut off at the mic, so
⏸ resumes 15:46reads as⏸ resumes. Drag the line to scroll to it. In a pane you are not typing into you cannot — the line is inside the stub's button there, and a drag focuses the pane. Focus it and read the line in the box.
Related
- auto-compact — what the
ctxnumber is measured against - usage-limit-pause-and-retry — the paused segment
- usage-meters — plan usage, which is a different number
- machine-name — the first segment, and the machines behind it
- floating-chrome — the band the bar sits in