[Feature Request] Fixed schedule option for usage limit reset window instead of rolling 5-hour window

Bug Description
Subject: Rolling 5-hour usage window is unworkable for live-trading use cases — request fixed reset schedule (or a way to reset/reschedule it manually)

The problem: Claude Code's usage limit resets on a rolling 5-hour window measured from first activity, not a fixed clock schedule. For someone running Claude Code alongside a live trading bot, this means:

• There's no way to predict when the window will reset, so there's no way to plan trading-day availability around it.
• Heavy usage late one day (e.g. multiple parallel background agent tasks running into the evening) can push the next reset into the middle of the following trading day, with zero visibility into when that will happen until it already has.
• /usage-credits doesn't reliably surface the actual reset time (returned "Login interrupted" when I tried to check it today), so even after the fact there's no way to confirm what happened or plan around the next one.

A concrete example of why this fails for trading: most days my window lands somewhere reasonable — roughly 7am–12pm, then 11am–4pm — which works fine. Today it drifted to something like 9:30am–2:30pm CST instead, and I genuinely don't know what caused the shift. That means my current window runs out 30 minutes before the US market close. If something with my bot fails mid-day and I've already used up that window, I'm locked out of help until the next window opens — which lands right around 2:30, giving me only about 30 minutes of runway before the close to actually fix anything with a live position on the line. That's about as bad a placement as this could land on.

Why this matters more than typical usage-limit friction: this isn't just an inconvenience — it's a live financial-risk exposure. If I lose access to Claude Code mid-trading-day with a live options position open and something needs attention, there is no way to know in advance that access is about to disappear, and no way to know when it will come back.

Request: either (a) offer a fixed-schedule usage window option (e.g. user-selectable 5-hour blocks like 7am–12pm / 12pm–5pm / 5pm–9pm in the user's local timezone) as an alternative to the rolling window, or (b) give users a way to manually reset/reschedule their current window when it's drifted somewhere unworkable — at least for Pro/Max plans. At minimum, make the actual reset time reliably visible in /usage-credits or the CLI status so users can plan around it instead of discovering it by getting cut off. There has to be a better method than this — right now it's mayhem to plan around.

Environment Info

• Platform: darwin
• Terminal: WezTerm
• Version: 2.1.235
• Feedback ID: 75be2f14-5d4c-4279-9e0b-b6de8af02efa

Errors

[]