Question / Description:
Since a couple of days the AI beta version dosn’t work? What is the reason?
Regards
Christian
Hey @Christian, thanks for writing in and welcome to the Community!! 
To help us understand what’s going on, could you clarify a few things for us? Thanks!
Are you on Retool Cloud or self hosted If self hosted, which version are you on?
When you say it doesn’t work, where are you using the AI beta? What do you see when it fails? Are there any error messages you can share? About when did it last work, and when did it first stop working?
Retool Cloud version 3.338.0
- Question: Which buttons are no longer needed?
Result: The limit for Assist's context window has been reached. Try again with a shorter prompt, or create a new thread.
No error messages
last work: 06.Feb.2026
Hey, thanks for the details! I can see you were asking Assist "Which buttons are no longer needed?" when you hit the limit.
I checked with our product and engineering teams. Here's potentially what's going on: Assist can only handle a certain amount of information at once. When you ask it to analyze your whole app, it might be trying to look at too much: all your buttons, queries, components, etc., which likely causes it to hit that limit.
Since you're on Cloud, the thread summarization should already be running automatically to help manage this. Try asking about a smaller part of your app instead. For example, "Which buttons in my user dashboard are no longer needed?" This way, Assist only looks at one section at a time. Let me know if that helps! 
Thanks for trying to help, but unfortunately this attempt was also unsuccessful.
Which buttons in my user dashboard are no longer needed?
Let me view the main page to see which buttons are at the top level
The limit for Assist's context window has been reached. Try again with a shorter prompt, orcreate a new thread.
@Christian Ah, sorry to hear that didn't work! How about trying to start a new thread? The auto-summarization should handle things correctly in a fresh thread. Keep me updated on how it goes!
Of course, I had always started new traets!
It appears that the number of tokens has been changed in the last few days.
Of course, I had always tried with new threats. It appears that the number of tokens has been changed in the last few days.
@Christian Did it work when you ask the question in a new thread?
It still isn't working. As already described, I always reloaded before starting a new thread.
Hello again @Christian We've pushed a fix that went live yesterday (February 17) at approximately 3pm EST around cached token counting, could you test this again on your end? Thanks! 
Sorry, no change. The AI isn't working.
Is it possible that this is due to hanging processes? Whenever I start a thread, the following message appears: “Page switching is disabled while Assist is building” and in the debugger: 
Circularity S3 checkboxes with correct data binding:
{B38: false, B39: false, B40: true, B41: true, B42: false…}
success
fixCircS3CheckboxMappings ran successfully (0.007s)
fixCircS3CheckboxMappings
success
queryVerificationStatus ran successfully (0.817s)
queryVerificationStatus
success
queryVerificationStatus ran successfully (1.504s)
queryVerificationStatus
success
queryVerificationStatus ran successfully (1.644s)
queryVerificationStatus
from queryVerificationStatus response(queryVerificationStatus)
in queryVerificationStatus.trigger()(queryVerificationStatus)
currentClientId.value: “000000-DE-12345-DEMOCLIENT”
environment: “production”
Translated with DeepL.com (free version)
I've been waiting for three weeks now for the AI error to be fixed. When can I expect a version in which the AI doesn't immediately crash after a system startup with “The limit for Assist's context window has been reached. Try again with a shorter prompt, or create a new thread.”?
Hey @Christian thank you so much for your patience, I'm sorry for the wait! I've been getting more information from our engineering team so I can best help you here.
Unfortunately, it looks like your app's size is hitting Assist's context window limit, which is why you're seeing this error right on startup. As a workaround, you can scope your prompts to a specific page using the @ tag, for example, typing @pageName will limit the context to just that page when writing a prompt, which should help you get back up and running.
I understand this isn't the permanent fix you've been waiting for, and I'm sorry for the frustration. Please let me know if the workaround helps or if you have any other questions!
These restrictions were not mentioned anywhere at the time of my purchase. I therefore request a reduction in my license price or appropriate compensation.
These restrictions were not mentioned anywhere at the time of my purchase. I therefore request a reduction in my license price or appropriate compensation.
How can I still complete my project?
Can I split the project across multiple pages without having to worry about further restrictions? Can I move content from page 1 to page 2, and how do I generally need to adjust cross-page scripts? What else would I need to consider to ensure that everything continues to run smoothly? How can I generate a PDF report that represents all container content?
Unfortunately, the proposed workaround “you can scope your prompts to a specific page using the @ tag, for example, typing @pageName will limit the context to just that page when writing a prompt” does not work either.
Thanks so much for your patience while we looked into this! @Christian
Unfortunately, Assist isn't able to support apps at this scale right now. The context window has limitations with very large apps.
The best path forward would be to split your app into smaller, separate apps. The good news is you can use the Query Library and Modules to share common code and components across apps, so you won't need to duplicate everything. Think of each app as a specific workflow or screen rather than one giant application.
Since Assist is still in beta, we're actively working on improvements, but large app support isn't something we'll have in the short term. In the meantime, you can absolutely continue building manually without Assist! Let me know if this makes sense, and how I can continue to support you through this!
By the way @Christian, don't miss our AI Office Hours session tomorrow (Thursday) at 9am PT! Got more AI questions? Bring them. We would love to see you there! 