How to switch back from GPT-3.5 to ChatGPT-4 when you reached the limit of 25 messages in 3 hours
TLDRThe video outlines a workaround for switching back to ChatGPT-4 after reaching the message limit of 25 messages in a 3-hour period, which defaults the user to GPT-3.5. The solution involves using Firefox to inspect the conversation's network activity, locating and altering the model version to 'gpt4', and then running the changes to regain access to ChatGPT-4. Credit is given to a Reddit user, kinky Cusco, for this method.
Takeaways
- 🚫 GPT-4 switches to GPT-3.5 after 25 messages in a 3-hour period.
- ⏳ To switch back manually, wait for at least two hours after reaching the limit.
- 💻 Use Firefox browser for the process of switching back to GPT-4.
- 🔍 Open the conversation where the switch occurred and inspect the elements.
- 📝 Write a test message to trigger the network activity.
- 🔗 Click on 'Network' and use the 'Fetch' option in the console.
- 🔑 Locate the 'model' in the text and change 'text DaVinci 2.0.2 render' to 'gpt/4'.
- 🔑 Keep the backslash '/' in 'gpt/4' for the change to work.
- 🏃 Click 'Run' to execute the change.
- ♻️ Refresh the page to confirm the switch back to GPT-4.
- 👤 Credit for this workaround goes to a Reddit user, kinky Cusco.
Q & A
What happens when you exceed the 25 message limit in a 3-hour period with GPT-4?
-When the 25 message limit is exceeded within a 3-hour period, GPT-4 will automatically switch to GPT-3.5 for the user.
How can you tell if the switch from GPT-4 to GPT-3.5 has occurred?
-The switch can be identified by the change in the model version displayed in the chat interface, where it shows the older version, such as 'text DaVinci 2.0.2'.
What is the suggested workaround if you want to switch back to GPT-4 after being switched to GPT-3.5?
-The suggested workaround is to wait for another two hours for the quota to become available again before starting a new conversation with GPT-4.
Why might someone want to switch back to GPT-4 after being switched to GPT-3.5?
-One might want to switch back to GPT-4 to continue a long conversation history and to maintain the trained communication patterns established with GPT-4.
What is the recommended method to switch back to GPT-4 as described in the script?
-The recommended method involves using the Firefox browser, logging into ChatGPT, opening the conversation where the issue occurred, and then using the inspect element feature to modify the model version in the network tab to 'gpt/4'.
How does the Reddit user kinky Cusco contribute to the solution?
-Kinky Cusco from Reddit provided the steps to switch back to GPT-4 by manipulating the model version in the browser's developer console.
What should you do after changing the model version in the browser's console?
-After changing the model version, you should click the 'Run' button in the console to apply the changes, then close the console and refresh the page.
What are the potential consequences of not being able to switch back to GPT-4 manually?
-If unable to switch back manually, users would have to start a new chat, which would result in losing the entire conversation history with GPT-4.
Why is it important to keep the backslash in the model version when changing it in the console?
-The backslash is important as it is part of the model version identifier. Deleting it would result in an incorrect model version, and the switch back to GPT-4 would not work.
How can you verify that you have successfully switched back to GPT-4?
-You can verify the successful switch by checking the icon and observing the response speed and pattern of GPT-4 in the chat.
What is the main takeaway from the video script for users who encounter the same issue?
-The main takeaway is the method to switch back to GPT-4 manually by using the browser's developer console to change the model version, as detailed by the Reddit user kinky Cusco.
Outlines
🤖 GPT Version Switching Issue and Solution
The paragraph discusses a problem encountered when using Chat GPT 4, where exceeding a limit of 25 messages within a two-hour period results in an automatic switch to GPT 3.5. The speaker describes a situation where a long conversation history with GPT is lost when switched back to GPT 3.5 due to the message limit. They then explain a method to manually switch back to GPT 4 using the Firefox browser, involving steps like logging into chatgpt, using the inspect feature, and modifying a model parameter in the network console. The solution is credited to a user named Kinky Cusco from Reddit.
🔄 Returning to GPT 4 After Forced Downgrade
This paragraph continues the discussion on the GPT version downgrade issue, focusing on a solution to revert back to GPT 4 after being switched to GPT 3.5. The speaker demonstrates a process involving the Firefox browser, inspecting the conversation element, and modifying the model parameter in the network console to change it from GPT 3.5 back to GPT 4. They emphasize the importance of keeping the backslash in the parameter and running the modified code to switch versions. After applying the fix, the speaker refreshes the page and confirms that they are back in GPT 4, encouraging viewers to follow along for more AI-related content.
Mindmap
Keywords
💡GPT-3.5
💡ChatGPT-4
💡message limit
💡conversation history
💡switch back
💡Firefox
💡inspect
💡network
💡model
💡coding
Highlights
Switching from GPT-3.5 back to ChatGPT-4 after reaching the message limit is possible with a workaround.
The default limit is 25 messages within a 3-hour period before switching to GPT-3.5.
Waiting for another two hours can reset the limit, but this may disrupt long conversations.
A manual switch back to GPT-4 is not straightforward once the conversation has started.
Starting a new chat would result in losing the entire conversation history.
The solution involves using the Firefox browser and its developer tools.
After waiting for the quota to reset, open the conversation and inspect the elements.
Utilize the 'Network' tab to identify the conversation's data packet.
Modify the model version in the data packet from GPT-3.5 to GPT-4.
Ensure the backslash is included when changing the model version in the code.
Run the modified code to switch back to GPT-4 within the same conversation thread.
The method was discovered by a user named Kinky Cusco from Reddit.
This workaround preserves the conversation history while upgrading back to GPT-4.
The process is user-friendly and does not require extensive coding knowledge.
The video provides a step-by-step guide on how to execute the workaround.
The success of the method is demonstrated by the return to GPT-4 and the continuation of the conversation.
This solution is particularly useful for those who have trained GPT-4 for specific communication needs.
The video encourages viewers to follow along for more AI-related content.