[rondar](/) [Product](/)[Pricing](/pricing)[Demo](/demo)[Docs](/docs)[Contact](/contact) [Sign in](/access#access-sign-in)[Request an invite](/access) [Product](/)[Pricing](/pricing)[Demo](/demo)[Docs](/docs)[Contact](/contact)[Sign in](/access#access-sign-in) Usage limit # 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. ## What Rondar reads Rondar reads the weekly window of a Claude connection through the Claude CLI of that connection. The CLI gives the percent used and the reset time. Rondar reads it only for a Claude connection that is signed in with the Claude CLI. 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](/settings/connections) ## Weekly limit banner When a weekly window of a connection that your selections use is at 100%, every signed-in page of Rondar shows the weekly limit banner. Your selections are the agent and model for new sessions, plan mode, infrastructure jobs and Sentinel monitoring, and the default agent of each project. The banner lists the models of your other connections. One press moves every selection that uses this connection to the model that you choose. You can ask Rondar to offer the earlier models again. When the limit resets, the banner asks you to go back or to keep the model in use now. Not now makes the banner a slim strip until the limit resets. When no other provider is connected, the banner offers to connect one. The banner shows the reset time in your own time zone. While a page is open, Rondar reads the usage again every 15 minutes. The banner changes your selections. It does not move a session that runs now. A session that stops at the limit uses the steps below. ## When a session stops The Claude CLI says, for example, that you hit your weekly limit or that the limit will reset. 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 Claude reaches its weekly limit?** A session that stops at the limit offers to continue on a model of another agent that you connected. With Continue automatically on, Rondar switches one time without a question. **Does the session keep its files when it moves to another agent?** Yes. The session keeps its branch and its workspace. The next agent gets your last request again and a note to continue from the current worktree and keep the edits. **What does the weekly limit banner change?** It changes the agent and model of your selections that use the Claude connection at its limit: new sessions, plan mode, infrastructure jobs, Sentinel monitoring and the default agent of each project. It does not move a session that runs now. **Does Rondar go back to Claude when the weekly limit resets?** Only when you ask for it. If you ask, the banner offers the earlier models again when the limit resets, and you choose to go back or to keep the model in use now. **When does my weekly window reset?** Rondar does not say this for other accounts. After you sign in, Settings, Connections shows the reset time that your own Claude connection reports. ## On this page [What Rondar reads](#limit-window)[Reset time](#limit-reset)[Weekly limit banner](#limit-banner)[When a session stops](#limit-session)[Same session, same workspace](#limit-workspace)[Questions](#limit-questions) ## Usage limit pages [Claude Code 5-hour limit](/limits/claude-code-5-hour)[Codex rate limit](/limits/codex)[OpenCode Go window](/limits/opencode-go)[Limit plan](/limits/plan) [rondar](/)© 2026 Rondar [Docs](/docs)[Pricing](/pricing)[Demo](/demo)[Rondar vs Amp](/compare/amp)[Rondar vs T3 Code](/compare/t3-code)[Rondar vs OpenHands](/compare/openhands)[Contact](/contact)[Security](/security)