[Feature Request] Raise 5-hour usage limit or allow weekly pool carryover for business-hours use

Bug Description
Title: 5-hour limit is too small for business-hours work, so the weekly limit goes mostly unused Summary I work only in business hours, but I run out of the 5-hour limit within minutes of heavy use, and then wait about 4 hours for the reset. Because of that, I only use roughly 50% of my weekly limit. The weekly allowance is effectively unreachable under normal working patterns. Details - Typical day: 8 hrs - Time to hit the 5-hour limit: [30] minutes, in sessions of [Opus withmulti-file edits with subagents]. - Result: about 80 minutes of effective use per 20 hours of calendar time if I tried to chase the weekly cap. That isn't realistic, so I peak at about 50% of the weekly limit. - Using a bigger model (e.g. Opus) doesn't help. It drains the window faster and I'm blocked just as soon. - Session resets in settings are a one-time claim, not a sustainable fix. - I've already trimmed my own token use: Haiku subagents, context-mode, and fewer plugins. I haven't had the 5-hour window grow as a result. Expected behavior The 5-hour limit should be large enough that a business-hours user can reach most of the weekly allowance in two or three windows per day. Request (any one of these would fix it) 1. Raise the 5-hour limit by about 30–40%. 2. Let unused weekly capacity carry into the current window, or add a softer weekly-pool mode. 3. Show a clear breakdown of what consumed each window (main session, subagents, hooks, background plugins) so users can see why it drains. Environment Claude Code on Windows 11, Sonnet 5.5 as the main model, Haiku subagents,

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.296
• Feedback ID: 584a6507-e9c2-47d2-8080-6c610996da3a