Usage limits
When your coding agent stops at a usage limit
Each page tells what Rondar reads and what Rondar does at one limit. In Rondar, a session that stops at a limit can continue on another agent in the same workspace.
The moments
- Claude Code hit its 5-hour limit
- What Rondar reads about the 5-hour window of your Claude connection, and how a session continues on another agent in the same workspace.
- Claude hit its weekly limit
- What Rondar reads about the weekly window of your Claude connection, and how a session continues on another agent in the same workspace.
- Codex hit its rate limit
- What Rondar reads about the rate limits of your Codex connection, and how a session continues on another agent in the same workspace.
- OpenCode Go used up a window
- What Rondar reads about the windows of your OpenCode Go subscription, and how a session continues on another agent in the same workspace.
- Limit plan
- Tick the subscriptions that you pay for, and get the order in which a session moves when one of them stops. No account. Nothing is saved.
What these pages do not say
These pages do not give the limits of a provider. A provider can change its limits at any time.
They do not compare products. They say what Rondar reads and what Rondar does.