What the ChatGPT usage limit is
ChatGPT caps usage per model, and the caps vary by plan and by model. The limit that matters is the one on the strong model, and it lands mid-job: the analysis is half done, the draft is half written, the plan lives inside one conversation. The reset is a rolling window, shown inside the product, and it runs on the vendor's clock, not yours. Switching to a weaker model keeps a chat alive, but the step you actually need is usually the one the capped model was doing.
The job, though, is not the allowance. If the job has a record outside the chat, it can finish somewhere else, today, in an AI you already have.
The move: hand the job over, finish in another AI
- Wrap the job up. If your ChatGPT plan has MCP write (Business, Enterprise, or Edu), say wrap up in ChatGPT and take the continue link. The exact line is in the card below.
- Or start from the record that already exists. Any step that ran through Zambo tools already left a receipt outside the chat. The job's record does not depend on ChatGPT being awake.
- Open the AI that takes over. Claude is the natural landing spot: it takes custom connectors on every plan and the free plan includes one connector slot, so creating the next handover there is easy. Gemini takes the paste path; Grok takes a custom connector at grok.com/connectors, or the same paste path.
- Paste the pickup prompt and the link, and continue. The receiving AI starts at what is next, and its work chains onto the same job record.
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."
No setup at all? Copy the brief by hand this once: the goal, what is finished, what is next, and the decisions, dead ends included. Paste it into the other AI with the pickup prompt. Lossy, manual, and still faster than waiting, and it is the last time you should have to do it by hand if you take the setup section seriously.
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.
Per AI, honestly:
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.
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.
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.
Why the second subscription is the wrong fix
The usual response to a usage limit is paying for a second AI and then copy-pasting between the two, which buys you two allowances and the same broken bridge. The limit was never the real problem. The real problem is that the job lived in one chat. Give the job a record that any AI can continue, and the allowances you already have become one pool of working time, shared by every AI on your desk.
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 ChatGPT usage limit and still need to finish?
Move the job, not your deadline. If your plan has MCP write, say wrap up in ChatGPT: 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 Claude, Gemini, or Grok with the pickup prompt and finish there. If your plan cannot create the handover, start from the record the job already left through connected tools, or copy the goal, what is done, what is next, and the decisions over by hand this once.
How long does the ChatGPT usage limit last?
It depends on your plan and the model, and the window is rolling rather than a fixed clock time, so any page quoting you an exact hour is guessing with this week's numbers. The reset time that applies to you is the one shown in the product. The practical answer does not depend on it: the job can continue in another AI now, and when the window opens again, either AI can pick the job back up from the latest handover.
Can I continue the exact same conversation in Claude?
The chat thread itself does not transfer; Claude cannot open your ChatGPT history. What continues is the job, carried by its record: goal, done, next, decisions, receipts. Continued from a handover, Claude starts at what is next with the decisions in front of it, which is the part of the conversation that was actually load-bearing. The rest was transcript.
Which AI should I continue in?
The ones you already have. Claude is the easiest landing spot because it takes custom connectors on every plan and the free plan includes one connector slot, so the next handover can be created there. Gemini takes the paste path: continue link plus pickup prompt. Grok takes a custom connector at grok.com/connectors, or the same paste path. Your editor tools take it through MCP config. There is no wrong door, because the record is the same through all of them.
Does this work for long agent and research jobs too?
Yes, with the same shape. Any step that ran through connected tools left a receipt outside the chat, so a long job's record exists even if the chat is capped, and the receiving AI continues from the recorded state. A job that lived entirely as chat text moves by the wrap-up line if it was set up, or by a hand-copied brief if it was not. The longer the job, the more the recorded version wins.