Composer — telemetry placement

Reference (Claude Code web): model + effort + context usage shown in a single compact strip in the composer chrome ("Opus 4.7 · High" + small circular ring). Three takeaways shape these mockups: this metadata belongs near the input (it's config for the next response, not session identity); model + effort can collapse to one text trigger that opens a popover; context usage reads cleaner as a small ring than a horizontal bar.

0. Current — bulky pickers + stats line

Model and effort are full <select> dropdowns with uppercase eyebrow labels. Cost / duration / token count + horizontal usage bar live as a separate line above the composer. Three rows of chrome before you see the textarea controls.

$0.0014 · 1.2s · 14.2k/200k tokens 23%

1. Compact — send-inside, brighter model, ring with popover (recommended)

Refinements over the previous draft of this variant:

Closed state:

With ring popover open (hover or click on the ring):

Warn state at 76% — ring fills further and adopts the warn color (matching the existing usage-bar warn threshold):

My recommendation

Variant 1 as shown — ship this. The composer becomes a single textarea with the send icon in-place, plus one action row carrying the mode toggle on the left and the config trigger + ring on the right. Ring details land in a deliberate popover instead of a browser tooltip.

Implication for the header: it stays just title + project. Telemetry, model, and effort all leave the header entirely. The earlier header.html mockup is now obsolete.