-
-
Notifications
You must be signed in to change notification settings - Fork 11.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Forking Breaks If Over 150k Tokens #5692
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Hey @ColbySerpa! I'm here to help you with any bugs, questions, or contributions. Let's tackle this issue together! The issue you're experiencing with token counting in forked chats might be related to how tokens are calculated and managed in the framework. The token counting logic is implemented in the Additionally, the The error you're encountering might be due to a discrepancy in how tokens are counted in forked chats compared to the original chat. It could be beneficial to review the token counting logic in these files to identify any potential issues or inaccuracies specific to forked chats. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
it seems a bug, I will figure it out |
@arvinxx Thank you so much! It will make my life 1000x easier. 🙏 |
You can reproduce this bug easily with Claude if your original chat is over 150k tokens and then you fork it. In the fork, as you approach 170k and 180k tokens, every message you send will fail because it says that the 200k token limit has been reached. For some reason, the token counting is inaccurate in the fork.
To get around it, I have to delete the fail message and press retry — then it will work. Every single time I have to send a message in the fork I have to delete the error reply message and then retry which is incredibly annoying and slows me down. It would be great if the forking feature was fixed.
If you have any questions please let me know.
The text was updated successfully, but these errors were encountered: