Skip to content

feat: add 2-line status layout with token breakdown and provider name#681

Merged
FL4TLiN3 merged 1 commit intomainfrom
feat/status-line-token-breakdown
Mar 4, 2026
Merged

feat: add 2-line status layout with token breakdown and provider name#681
FL4TLiN3 merged 1 commit intomainfrom
feat/status-line-token-breakdown

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Mar 4, 2026

Summary

  • Add providerName to initializeRuntime event and display it in the status line
  • Replace single total token count with per-type breakdown: R(easoning), I(nput), C(ached), O(utput) with cache hit rate
  • Status line now uses 2 lines: 1 running · 1 waiting · 5m 25s · anthropic + R 12.5k · I 180.2k · C 145.8k · O 25.3k (cache: 80.95%)

Test plan

  • bun run typecheck — 24/24 pass
  • bun run test — 20/20 pass
  • bun run build — 24/24 pass
  • bun run format-and-lint — no new issues
  • bun test --timeout 300000 e2e/ — 89/89 pass
  • bun run validate:changeset — passed

🤖 Generated with Claude Code

…ider name

Replace single-line token display with a 2-line layout:
- Line 1: running/waiting counts, elapsed time, provider name
- Line 2: R(easoning)/I(nput)/C(ached)/O(utput) token breakdown with cache hit rate

Add providerName to initializeRuntime event and track per-type token
accumulation (reasoning, input, cached input, output) across callTools,
completeRun, and retry events.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@FL4TLiN3 FL4TLiN3 merged commit 4990786 into main Mar 4, 2026
11 checks passed
@FL4TLiN3 FL4TLiN3 deleted the feat/status-line-token-breakdown branch March 4, 2026 12:46
@FL4TLiN3 FL4TLiN3 mentioned this pull request Mar 4, 2026
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