Feature request: auto-retry last message after usage quota window resets

Summary

Add an optional setting to automatically re-run the last user message once the usage quota window resets (e.g. after the 5-hour or 1-week limit), instead of requiring a manual retry.

Problem

When the quota is hit, the user must remember to come back after the window and manually resend or retry the same prompt. This interrupts flow, especially for long-running or unattended sessions.

Proposed behavior

• A toggle (e.g. in settings or surfaced when quota is shown): “Auto-run last message when quota resets” (or similar).
• When enabled, after the applicable window elapses, Claude Code would queue or automatically submit the last blocked message (or the last message that failed due to quota), subject to reasonable safeguards (e.g. confirm the workspace/repo is unchanged, or a short countdown before execution).

Notes

• Exact quota semantics (5h vs 1w) may vary by plan; the feature should align with whatever windows the product exposes today.
• Consider edge cases: user sent other messages in between, session ended, or repo changed—clear UX for what “last message” means.

Thank you for considering this.