Codex hit its rate limit

What Rondar reads

Rondar reads the rate limits of a Codex connection through the Codex CLI, with its request account/rateLimits/read.

The CLI reports each limit with up to two windows. For each window, it gives the length, the percent used and the reset time. Rondar shows the windows that the CLI reports. It does not set their length.

Rondar runs the CLI in a temporary folder for each reading and deletes the folder after it. It keeps each reading for 5 minutes.

Reset time

This page shows no reset time, because each account has its own.

After you sign in, Settings, Connections shows each window of your own connection, the percent used and the time it resets, as your connection reports them.

Open Settings, Connections

Weekly limit banner

When the CLI reports a window of 7 days or longer at 100% for the shared Codex limit, the weekly limit banner opens. A limit of one model does not open it.

A shorter window does not open the banner. The banner works as the Claude weekly page tells.

When a session stops

The Codex CLI says, for example, that you hit your usage limit or that you can try again at a time. Rondar reads these words as a usage limit.

1. When the CLI of the agent says that the account reached its limit, the turn stops with a usage limit error.
2. The session then shows a card with one button: Continue with the next model. Rondar chooses a model of another agent that you connected first. When there is none, it offers another model of the same agent.
3. Press the button. Rondar saves the new agent and model on the session and sends your last request again.
4. In Settings, Agent defaults, you can turn on Continue automatically. Then Rondar switches without a question, and the session says which model it uses. It switches automatically one time in each session.
5. When no other model can run, the session tells you to wait until the limit resets or to choose another connection.

Same session, same workspace

The session stays the same session. It keeps its branch and its workspace, so the files stay as the last agent left them.

Rondar tells the next agent: "The previous model could not continue. Continue the same task from the current worktree and preserve edits." Then it gives your last request again.

A plan that you saved in Rondar is a record of the project. It does not change when the agent changes.

Questions

What does Rondar do when Codex hits its rate limit?

The session stops with a usage limit error. Rondar then offers to continue the session on a model of another agent that you connected. With Continue automatically on, Rondar switches one time without a question.

Which Codex windows does Rondar read?

The windows that the Codex CLI reports for your account, each with its length, the percent used and the reset time. Rondar does not set the length of a window.

Does the weekly limit banner act on Codex?

Yes, when the CLI reports a window of 7 days or longer and that window of the shared Codex limit is at 100%.

When does my Codex limit reset?

Rondar does not say this for other accounts. After you sign in, Settings, Connections shows the reset time that your own Codex connection reports.