What the weekly limit actually is
Claude plans carry a weekly usage cap on top of the shorter session windows. The session window costs you hours. The weekly cap costs you days, and it lands mid-job as often as at a clean stopping point: the research is half gathered, the draft is half written, the plan exists mostly inside one conversation. The reset arrives on the account's own schedule, shown in your usage settings, and no new chat, refresh, or prompt moves it.
Two things stay true when it lands. Your chats and files are intact, waiting for the reset. And every other AI you already have, paid or free, is completely unaffected. The job is only stranded if its record lives in exactly one place: the capped chat. Move the record, and the job moves with it.
The move: wrap up, hand over, finish somewhere else
- Say wrap up in Claude. With Zambo connected, Claude hands the job over as a record: the goal, what is done, what is next, every decision, with the receipts attached, and hands you a continue link. The exact line is in the card below.
- Open the AI that takes over. ChatGPT, Gemini, Grok, or your editor. Paste the pickup prompt and the continue link. The receiving AI reads the record, not a summary you typed under pressure.
- Continue from what is next. The second AI works from the recorded state. Its steps chain onto the same job record, so the finished job reads as one job, not two half jobs in two apps.
- Come back if you want. When the weekly reset lands, Claude can pick the job up from the latest handover. The chain runs in both directions, as many hops as the job needs.
The one line to save
"When I say WRAP UP, hand this job over with Zambo: the goal, what is done, what is next, every decision, with the receipts attached, and give me the continue link."
Say it before the cap, and the AI hands the job over as a record: goal, done, next, decisions, receipts, and a continue link. Paste this pickup prompt into the AI that takes over:
"Continue this job from its record: [paste the continue link]. The goal, what is done, what is next, and every decision are in the handover, with the receipts attached. Start from what is next, and keep the record going as you work."
Already capped, and never set anything up? The job is not lost, the handoff is just manual this once. Open the chat, and copy four things into the pickup prompt yourself: the goal in one or two sentences, what is finished, what is next, and the decisions already made, especially the dead ends, so the next AI does not retry them. It is slower and lossier than the recorded version, and finishing this one job by hand is exactly what makes the two-minute setup below feel worth it.
Nothing set up where the job lives? Skip the connector for today: the paste box at zambo.dev/continue takes the wrap-up from any AI and hands back the same continue link, no account and no install.
Set it up once, before the next cap
The whole setup, the wrap-up line with copy buttons for each AI, and the paste box live on one page: Continue in another AI.
The whole system is one saved line plus, where the AI supports it, one connector. Per AI, honestly:
Claude: one connector slot, on every plan
Claude takes custom connectors on every plan, and the free plan includes one connector slot. Add Zambo as a custom connector (Settings, then Connectors, then add a custom connector pointing at https://zambo.dev/mcp), then paste the wrap-up line into your custom instructions so it is loaded in every chat. From then on, the one-word flow works inside Claude itself, and Claude becomes the easiest place to create a handover.
ChatGPT: pickup for everyone, creating on team plans
Continuing a job inside ChatGPT works for everyone, through the pickup prompt: paste the prompt, add the continue link, and ChatGPT continues from the record. Creating the handover from inside ChatGPT needs MCP write access, which lives on the Business, Enterprise, and Edu plans. On a consumer plan, create the handover in an AI that has Zambo connected, Claude is the easy one, and bring the link to ChatGPT.
Gemini: the paste path, with Saved info
Gemini takes the paste path. Save the wrap-up line in Saved info so the habit is written down where you will find it, and when a job matters, wrap it up in the AI that holds the job, then paste the continue link into Gemini with the pickup prompt. Gemini continues from the recorded job instead of from your retelling of it.
Grok: a custom connector, or the paste path
Grok takes custom MCP connectors: add a custom connector at grok.com/connectors with https://zambo.dev/mcp, and the job can be wrapped up and continued inside Grok itself. Keep the wrap-up line in your custom instructions either way. With no connector set up, the paste path still works: paste the continue link plus the pickup prompt into Grok, and it picks the job up from what is next.
Cursor, Claude Code, Codex, VS Code: config once
In the coding tools, add the Zambo MCP to the MCP config once. Every project after that can wrap up and continue, and the handover runs between the editor and the chat AIs in both directions, which is the route to take when a chat AI planned the work and the editor has to build it, or the other way around.
A real job that already made this move
Claude started it, ChatGPT finished it, one chain
On October 18, 2026, a job ran in Claude, then continued in ChatGPT from the handover instead of from a summary, and was accepted on the record the same day. Open both hops yourself: the first handover, and the continuation. The second AI started at what is next, and nothing had to be re-explained, re-decided, or re-done.
What waiting and restarting actually cost
Waiting costs the days until the reset, and the job's momentum with them. Restarting in another AI costs the context: the new AI re-asks settled questions, retries dead ends you already paid for, and quietly contradicts decisions it never saw. The handover costs one sentence before the cap, and the job keeps its goal, its progress, its decisions, and its receipts. That is the whole trade.
What it costs to stop waiting
Don't buy a second AI for the three bad days a month. Finish in the ones you already have.
Continuing a job is free on a normal day: the handover, the continue link, and the receipt checks cost nothing, and the public handover page is free to send and to open. On a heavy day, when the job is big and the record has to hold up, a $0.99 Day Pass covers 24 hours of the full machine, and the Zambo Pass at $29 a month is there for people who hand work over every week. Start where the job is stuck: hand it over on zambo.dev.
Questions, answered
What do I do when I hit the Claude weekly limit?
Do not wait, and do not restart. Hand the job over and finish it in another AI you already have. If Zambo is connected in Claude, say wrap up: When I say WRAP UP, hand this job over with Zambo: the goal, what is done, what is next, every decision, with the receipts attached, and give me the continue link. Then paste the continue link into ChatGPT, Gemini, Grok, or your editor with the pickup prompt, and the job continues from what is next. If you never set it up, copy the goal, what is finished, what is next, and the decisions into the pickup prompt by hand this once, and set up the connector before the next cap.
Can I get around the Claude weekly limit itself?
No, and any page that promises a trick is selling you a banned account. The cap sits on the account, and new chats do not move it. What you can move is the job. Your work is not the same thing as your Claude allowance: hand the job over with its record attached, finish it in an AI you already have, and the limit stops being the thing that decides when your work gets done.
Will I lose my work when the weekly limit hits?
Your chats and files stay where they were, and they are there when the reset lands. What does not survive on its own is the working state: the decisions made mid-job, the dead ends already explored, the exact place the job stopped. That state is what a handover records. If the job ran through connected tools, its receipts already live outside the chat, and the next AI can pick up from the record even before you say anything.
Does continuing my job in another AI cost money?
Don't buy a second AI for the three bad days a month. Finish in the ones you already have. Continuing is free on a normal day: the handover, the continue link, and the receipt checks cost nothing. On a heavy day, when the job is big and the record has to hold up, a $0.99 Day Pass covers 24 hours of the full machine. The Zambo Pass at $29 a month is for people who hand work over every week.
How do I make sure the weekly limit never strands a job again?
Set it up once, on a calm day. Add Zambo as a custom connector in Claude, the free plan includes one connector slot, and paste the wrap-up line into your custom instructions so it loads in every chat. From then on, wrap up is a habit, not a rescue: say it whenever a job matters, capped or not, and every important job already has a record that any other AI can continue.