The top-right chrome repeats the rail and shows a number nobody can use #2

New issue

Closed

opened 2026-09-13 07:43:06 -04:00 by cmoriarty · 1 comment

cmoriarty commented

2026-09-13 07:43:06 -04:00

Owner

Reported from the running system. The top bar reads ◆ inbox + new run ● live · seq 36486. Two of those controls already exist in the rail two inches to the left, and
one of them is an internal cursor.

`seq` is a coordinate, not a status

seq is how a deep link, a ?since= replay and a Playwright selector find their place
in the log. None of those readers is the operator, and there is no question a person has
that is answered by "36486". It is already on every row as data-seq, where all three
machine readers still find it.

If something in that corner should say the stream is keeping up, it should say that —
in a unit a person can act on — and not by printing a monotonic integer.

Acceptance

inbox and new run appear once, not twice.
seq is not in the chrome. Nothing that reads it programmatically breaks.
What remains in that corner earns its place: a person can say what each item is for.

Written from watching the running system. Source: docs/issues/02-the-top-right-chrome-is-redundant-and-opaque.md.

**Reported from the running system.** The top bar reads `◆ inbox + new run ● live · seq 36486`. Two of those controls already exist in the rail two inches to the left, and one of them is an internal cursor. ## `seq` is a coordinate, not a status `seq` is how a deep link, a `?since=` replay and a Playwright selector find their place in the log. None of those readers is the operator, and there is no question a person has that is answered by "36486". It is already on every row as `data-seq`, where all three machine readers still find it. If something in that corner should say the stream is keeping up, it should say *that* — in a unit a person can act on — and not by printing a monotonic integer. ## Acceptance - `inbox` and `new run` appear once, not twice. - `seq` is not in the chrome. Nothing that reads it programmatically breaks. - What remains in that corner earns its place: a person can say what each item is for. --- *Written from watching the running system. Source: `docs/issues/02-the-top-right-chrome-is-redundant-and-opaque.md`.*

cmoriarty referenced this issue from a commit

2026-09-13 11:58:46 -04:00

feat: say which run is which, drop the chrome nobody could use, name the backend

cmoriarty referenced this issue from a commit

2026-09-13 11:58:46 -04:00

fix(chrome): rail facts from the server, a status light from two clocks

cmoriarty commented

2026-09-13 12:34:48 -04:00

Author

Owner

Done and verified against the live system.

inbox and new run appear once. The header's copies show only below 1280px, where the rail is hidden; phones use the bottom bar.
seq is out of the chrome. Machine readers still find it as data-cursor on the status light and data-seq on rows; the Playwright suites that use it pass.
What remains earns its place: the top-right corner is now the status light alone (see #3).

Commits: 189908d, e398d36 (pushed), e570721 (local main, not yet pushed).

Done and verified against the live system. - **`inbox` and `new run` appear once.** The header's copies show only below 1280px, where the rail is hidden; phones use the bottom bar. - **`seq` is out of the chrome.** Machine readers still find it as `data-cursor` on the status light and `data-seq` on rows; the Playwright suites that use it pass. - **What remains earns its place:** the top-right corner is now the status light alone (see #3). Commits: 189908d, e398d36 (pushed), e570721 (local main, not yet pushed).

cmoriarty closed this issue

2026-09-13 12:34:48 -04:00

cmoriarty referenced this issue from a commit

2026-09-13 12:43:55 -04:00

fix: no agent session outlives its attempt

cmoriarty referenced this issue

2026-09-13 16:14:16 -04:00

A run cannot be abandoned #9