Feature Request: Optional “Reset My Limits” / Limit Warm-Up Trigger

[mahirozdin]

Hi,

I have been using Codex LB for a while with multiple Codex accounts and several proxied devices. Overall, it works very well for balancing usage across accounts, but I noticed a small missing feature that could improve practical limit utilization.

The feature could be called something like:

Reset My Limits
or
Limit Warm-Up Trigger
or
Auto Start Limit Window

The main idea is this:

From my observation, when a Codex usage limit is refreshed, the new limit window does not necessarily start immediately at the exact reset time. Instead, the effective usage window seems to start when the first request is made after the reset.

This can cause some wasted time between:

1. the moment the limit becomes available again, and
2. the moment the user actually sends the first coding request.

For example, if a weekly limit becomes available but the account stays idle for several hours before the first real request, that idle time is effectively lost from the usable cycle. The same logic also applies to shorter rolling windows, such as 5-hour limits.

A possible solution would be to add an optional feature in Codex LB that automatically sends a very small request using the cheapest available model as soon as a limit refresh is detected or expected.

For example:

• When a weekly limit resets, Codex LB could send a minimal prompt to start the new weekly window immediately.
• When a 5-hour limit resets, Codex LB could send a lightweight request so the next 5-hour window starts as early as possible.
• This way, when the user later starts real coding work, the current window may already be partially progressed, and the next reset may happen sooner.

A simple example:

Without this feature:

• Limit resets at 10:00
• User starts working at 14:00
• The new usage window effectively starts at 14:00

With this feature:

• Limit resets at 10:00
• Codex LB sends a tiny warm-up request at 10:00
• User starts working at 14:00
• The usage window is already 4 hours into its cycle

This could allow users to consume the remaining available limit more efficiently and reach the next reset sooner, instead of losing idle time after the limit becomes available.

Of course, this should be optional and configurable because not every user may want automatic traffic to be sent on their behalf.

Possible configuration options:

• Enable / disable limit warm-up
• Choose which model should be used for the warm-up request
• Set the minimal prompt content
• Apply only to specific accounts
• Apply only to weekly limits, 5-hour limits, or both
• Add a cooldown or safety threshold to avoid unnecessary requests
• Show the last warm-up request time in the account status panel

The request itself could be extremely simple, for example:

“ping”

or

“Say OK.”

The purpose is not to consume meaningful tokens, but only to trigger the next limit cycle as early as possible after a reset.

I think this would be useful especially for users who manage multiple Codex accounts through Codex LB and want more predictable, efficient rotation behavior across accounts.

Thanks for considering it.

[mahirozdin]

@Soju06 I forked and created a PR for this feature but because I forget to open contributions @Komzpa had to create a repair fix branch becase was not able to push my branch. But my feature #773 is merged and released ont he latest version but I'm not on the contributors list because It wasnt my branch because of this situation. Could you please add me as a contributor to repo. Thanks!