[Feature Request] Add transparent session limit tracking and advance warnings before hitting limits

Bug Description
Claude Code’s session limits appear to have been reduced without any clear communication, and the impact is immediately noticeable. Tasks that previously fit comfortably within a session are now hitting limits unexpectedly fast under normal usage. Last week, reaching the limit required deliberate heavy use; now it happens during routine workflows.

This creates friction in several ways:
• Unpredictability: There is no clear indication of what changed or how limits are calculated, making it difficult to plan work.
• Interrupted workflows: Hitting limits mid-task disrupts momentum and reduces productivity.
• Perceived instability: Silent changes to core constraints undermine confidence in the platform’s reliability.

If limits have been adjusted, they should be:

1. Explicitly communicated (with changelog or notification).
2. Quantified clearly (e.g., tokens, requests, or time-based caps).
3. Observable in real time (usage meters or warnings before cutoff).

At minimum, advance warning and transparency would allow users to adapt. As it stands, the experience feels degraded compared to just a week ago, despite no change in usage patterns.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.81
• Feedback ID: 3b5a2d2b-0e23-44d6-9838-b1fbe4813bce