Skip to content

Move the suppressed-agents count off the tree's head into the footer - #4

Merged
simoncoombes merged 2 commits into
mainfrom
quiet-count-footer
Sep 12, 2026
Merged

simoncoombes merged 2 commits into
mainfrom
quiet-count-footer

Conversation

@simoncoombes

Copy link
Copy Markdown
Owner

Follow-up to #3, which merged before this landed on the branch.

+171 agents with no recorded activity sat between main and the first agent row, every frame — a census of things that did nothing, directly on top of the one thing that was doing something. §1.5 asks that they be stated, not that they be stated first.

The footer carries the count now, which is where the pane's other chrome lives:

AGENTS 1 · b38b · opus-5 · high  ▇▇▇▇▇· 19/20   28:08 · 5.9M tok
────────────────────────────────────────────────────────────────
◍ main  Tradefloor documentation                            1.3M
│ waiting on 1 agent                                         57s
╰─╮
  ╰● fix-python-docs…  opus-5 · high                      0.3k/s
     ✔ Dump mcp.py  +76 more
     ▸ Dump fingerprint.py                          ▪▫··  436k
────────────────────────────────────────────────────────────────
j/k move · ⏎ open · a returned · ? keys      171 quiet · s lists

s opens the census — the full list with each agent's id, type, spawn and last event, the same view ⏎ on the old line reached. s for suppressed, which is what the code and the docs call them; "quiet" is only what the footer has room for.

The count outranks the right column's mode hint, which is a reminder of a key ? also lists, where this is a fact about the session stated nowhere else on the screen. It never outranks an ask, a disconnect, or the scroll position.

That retires the inline expansion (quietLines, quietPreview): selecting the line used to grow six names under it, a worse copy of the census the same keypress opens. quietDetail stays — the idle screen still expands its own count, and the condensed screen still carries a line, because neither has a footer to put it in. Under 40 columns it still rides on the header as AGENTS 5 +40.

Second commit drops quietLineDrawn, dead since selectableIDs started reading the frame's hit-test metadata, and whose doc comment this change makes untrue.

Full suite passes; the three codexsrc failures are pre-existing on main.

"+171 agents with no recorded activity" sat between main and the first agent
row, every frame. A fan-out that trails a hundred and seventy-one announced
non-events put a census of things that did nothing directly on top of the one
thing that was doing something. §1.5 asks that they be stated, not that they
be stated first.

The footer carries the count now ("171 quiet · s lists", or just the count
under 56 columns), which is where the pane's other chrome lives, and `s`
opens the census — the full list with each agent's id, type, spawn and last
event, the same view ⏎ on the old line reached. `s` for suppressed, which is
what the code and the docs call them; "quiet" is only what the footer has
room for.

The count outranks the right column's mode hint, which is a reminder of a key
that is also in `?`, where this is a fact about the session stated nowhere
else on the screen. It never outranks an ask, a disconnect, or the scroll
position.

That retires the inline expansion (quietLines, quietPreview): selecting the
line used to grow six names under it, which was a worse copy of the census
the same keypress opens. quietDetail stays — the idle screen still expands
its own count, and the condensed screen still carries one, because neither
has a footer to put it in.
Dead since selectableIDs started reading the frame's own hit-test metadata
instead of re-deriving the pseudo-rows from geometry predicates, and its doc
comment ("every screen paints the notice as a selectable row") is now simply
untrue: no screen with a footer does.
@simoncoombes
simoncoombes merged commit 3b7d57a into main Sep 12, 2026
2 checks passed
@simoncoombes
simoncoombes deleted the quiet-count-footer branch September 13, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant