ChatGPT Fork Support
Quick answers for using forks, applying results, and reopening saved threads.
Monthly AI limits: November 3, 2026 (UTC)
The unlimited monthly beta has ended. Free includes 25 AI generations per UTC calendar month; Pro includes 100. Hosted AI stops when the allowance is used. There are no automatic overage charges; local tools and saved history stay available.
Allowances reset at 00:00 UTC on the first day of each month, independently of billing dates. Existing usage is retained; upgrading, signing out or reinstalling does not reset it. A Free account can upgrade to Pro for the higher monthly allowance.
Older Chrome Web Store wording about unenforced beta usage refers to the earlier beta period; its correction is awaiting review. Check the extension's usage display for your current allowance and remaining generations.
Using ChatGPT Fork
How do I start a fork?
Open ChatGPT, find the response content you want to explore, and use the Fork control beside it. A focused side thread opens with the selected source context.
Can I ask multiple follow-up questions?
Yes. Continue the conversation inside the fork without changing the original main chat.
How do I bring a result back?
When a fork reaches the result you want, use Apply to main chat to carry that result back into your main conversation.
Where are previous forks?
Open History in the Forked panel to reopen saved forks.
Troubleshooting
I don’t see the Fork control.
- Make sure ChatGPT Fork is enabled in Chrome.
- Refresh the ChatGPT tab after installing or updating the extension.
- Confirm you are using ChatGPT in a supported Chrome browser tab.
A fork isn’t responding.
Retry the request and confirm your internet connection is working. If the problem continues, refresh ChatGPT and reopen the fork from History.
I want to remove saved fork history.
Use the extension’s history/storage controls to delete individual forks or clear saved fork data.
Contact support
If you found a bug or need help, email support@northboundsoftwaregroup.com.
When reporting an issue, include your Chrome version, what you expected to happen, and what happened instead. Please avoid sending passwords or other sensitive information.