Skip to content

Usage limit rows show your pace - #114

Open
ShriD5 wants to merge 3 commits into
mainfrom
t3-watch/2026-11-20-usage-pace
Open

ShriD5 wants to merge 3 commits into
mainfrom
t3-watch/2026-11-20-usage-pace

Conversation

@ShriD5

@ShriD5 ShriD5 commented Nov 20, 2026

Copy link
Copy Markdown
Owner

What T3 added

T3 Code's thread usage rows now show your pace for each limit window: "Ahead of pace", "On pace" or "Under pace", plus "N% of the window left", and a tick on the bar where the window's elapsed time sits (pingdotgg/t3code@669e2ea8e7). On-pace means usage is within 5 points of the elapsed share.

How Godspeed does it

  • crates/ui/src/usage_cockpit.rs: pure elapsed_share, pace (Pace::{Ahead, On, Under}, same ±5 point band) and pace_summary. Our probes don't report window length, so pace exists only for windows with a known length: 5-hour (5h) and weekly (7d). Other windows (Cursor month, Copilot) show no pace.
  • crates/ui/src/shell/session_info.rs: each limit row in the session card's Usage section draws a 1px mark at the elapsed share, sitting slightly above and below the 4px bar. Its hover adds a second line, e.g. Ahead of pace · 60% of the window left. The Context row has no mark.
  • T3's other change in the same commit (rows link to a usage page) is not ported: the usage page is out of scope per T3-WATCH.md.

Also updates the T3-WATCH ledger (reviewed through t3code@2c33cbdf02, 392 commits) and T3-GAPS (Done row, plus new rows for agent PR/CI MCP tools and side-chat @ references).

Screenshots

Not available (the watch agent doesn't launch the GUI).

Tests

  • New: usage_cockpit::tests::pace_compares_usage_with_the_elapsed_window, session_info::tests::limit_rows_mark_the_elapsed_window_and_name_the_pace
  • cargo build -p godspeed ✅, cargo check --workspace --tests ✅, cargo test -p zeron-ui --lib: 2189 passed

Check by eye

  • Session card → Usage: the elapsed mark on the 5-hour and Weekly bars. Is it visible against both the fill and the empty track in light and dark themes, and is it clipped at the card edge when the window is almost over (~100%)?
  • The hover tooltip shows two lines (reset, then pace).

Each 5-hour and weekly limit row in the session card gets a mark at the
share of the window already gone, and its hover says whether usage runs
ahead of, on, or under pace, with how much of the window is left.

Inspired by: pingdotgg/t3code@669e2ea8e7
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