Impossible to use prototyper since past week

I know, there are probably another 10+ topics on this recently, I just want to know if it’s something that I should do from my side or there is a fix coming from the studio team about this.
I tried a few solutions around like checking my threads folder, removing my edit agent messages from capra (the usual fix i had to do prior to last week updates) but nothing helps.
I already added an .aiexclude file however it doesn’t help either.

Is there a rate limit imposed for the users using prototyper? I am not sure if this has to do with my codebase or is a general issue (based on what i see from other devs around facing the same issue). I am unable to send any message in the prototyper since last thursday, I assume after the recent updates with the new preview. Maybe something changed and I am not aware, when i started the project a few weeks ago, i read that studio does not have any limitation or costs for using gemini while developing the project.

Thank you for your time for reading this!

Have you tried this?

You will also want to be familiar with this thread.

This is an issue unique to your project and the files Gemini is receiving.

If you can reduce your context to a point where you are below the limit, you can ask it “What files outside of my source directory are currently in your context that I can exclude with .aiexclude?”

Or, you can use this script I had Gemini help me create.

1 Like

Thank you for your time and suggestions, I actually ended up excluding my main project folder in order to ask gemini to properly set up the .aiexclude file for me and then to check the token count vs limit. As the project grows and the token context increases, I think i will need to disable from context certain parts of application in order to avoid hitting the limit and I think this is one of the issues with larger codebases or as codebases evolve from prototyping in time.

1 Like

According to the release notes, the latest version of Firebase Studio now trims the history of the context to keep it from growing indefinitely.

It should decrease how often you run into that issue.

Beyond what @dms shared, can you please also file a support ticket to help our team investigate and see what is going on: Get help with Firebase Studio