[BUG] 5h session limit after using commands like /context and /usage

Bug Description
Hi, I need to speak with Product Support — I'm experiencing what I believe is a serious bug.

I opened a brand new session with the sole intention of checking my token usage, as recommended. I ran:

• /context (once)
• /usage (twice)

That's the entirety of my session activity. After just these three commands, I hit the 5-hour session limit. I hadn't done any actual work yet.

This is completely unacceptable. These are basic diagnostic commands built into the product — they are literally what's recommended for understanding token consumption. If running them burns through an entire session limit, something is fundamentally broken.

Please do not reply with links to documentation. I literally cannot open them — I don't have enough tokens left. That's the whole point of my complaint.

I want this escalated to someone who can actually investigate the session limit calculation and explain what happened. This needs to be fixed.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.119
• Feedback ID: df295ad4-afa5-4ad0-901c-40fddd0f5b76

Errors

[{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"This request would exceed your account's rate limit. Please try again later.\"},\"request_id\":\"req_011CaQZucUyZQcSB5CXrhNci\"}\n    at generate (B:/~BUN/root/src/entrypoints/cli.js:11:55098)\n    at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T13:28:19.739Z"}]