Repository navigation
Conversation
github-actions
Bot
added
the
needs:compliance
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found several related PRs that might be worth reviewing for context or overlap: Potentially Related PRs:
These PRs touch on similar token speed/throughput display features. You should review PR #46108 and #42112 particularly closely to ensure your implementation in the status bar doesn't duplicate or conflict with footer-based approaches, and to confirm the calculation methodology aligns. |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
github-actions
Bot
removed
the
needs:compliance
1 participant
Closes #47914
Shows real-time token generation speed in the TUI prompt status bar, Hermes-style (
15.2 t/s).chars / 4per token) over elapsed turn time, refreshed every 500ms next to theesc interrupthint. Exact counts only materialize at step-finish, so live values are estimates by design.tokens.output / (completed - created), appended to the existing usage line (12.3K (42%) ·$0.12· 48.0 t/s).packages/tui/src/util/tps.tswith unit tests (estimateOutputTokens,calcTps,formatTps).Verification:
bun typecheckinpackages/tui: clean.bun testinpackages/tui: 197 pass, 1 pre-existing Windows-only failure intest/runtime.test.tsx(path separator, fails on clean tree too).Follow-ups (not in scope): subagent footer parity,
--minirun footer, session-wide average,display.show_output_speedtoggle if maintainers want it opt-in.