[Feature Request] Expose session usage metrics in terminal status line

Resolved 💬 2 comments Opened Mar 18, 2026 by Code-Mandrill Closed Apr 15, 2026

Bug Description
Feature request: expose current session usage in the terminal status line

I'd love to have access to my current session plan usage (the "X% used / resets in N hours" shown in the UI sidebar) in the terminal status line, or
at minimum have it exposed in the status line JSON schema so I can build it into a custom statusline script.

Right now this data is only visible in the Claude Code UI — there's no way to surface it in the terminal itself. Being able to glance at the bottom
of my terminal and see how much of my session I've burned through (and when it resets) would be really valuable for managing my workflow without
having to context-switch to the UI.

Even just adding it as a field in the status line JSON would be enough — I'm happy to wire it up myself.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.77
  • Feedback ID: 7ceb854f-c309-4d3e-8e00-7ac76a053496

Errors

[{"error":"Error: Request was aborted.\n    at lXA (/$bunfs/root/src/entrypoints/cli.js:1189:68515)\n    at next (native:1:11)\n    at iD8 (/$bunfs/root/src/entrypoints/cli.js:6434:6962)\n    at next (native:1:11)\n    at oD8 (/$bunfs/root/src/entrypoints/cli.js:6439:9173)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-17T17:40:57.582Z"},{"error":"Error: Request was aborted.\n    at lXA (/$bunfs/root/src/entrypoints/cli.js:1189:68515)\n    at next (native:1:11)\n    at iD8 (/$bunfs/root/src/entrypoints/cli.js:6434:6962)\n    at next (native:1:11)\n    at oD8 (/$bunfs/root/src/entrypoints/cli.js:6439:9173)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-17T17:51:06.391Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:448:3940)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-17T22:34:55.575Z"}]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗