Member-only story
Firebase Studio, the coding agent from hell
If you are using Firebase Studio, quick. Get off that platform now before your project goes down the tubes.
In the worst case, you might not even be able to keep working on your project, encountering something like this:
Whoops… we are experiencing increased load and are spinning up a new VM for you. This may take several minutes. Check back soon.
I guess spending $10B in one quarter for new CPUs still doesn’t get you enough computing power.
Or maybe Google or Firebase will detect “suspicious activity” in your app development process — you were not writing one of those undressing apps now, were you? — and block your access to the app you just spent a month working on, with no recourse and no appeals process.
Right now, push your code to GitHub. If you choose to unwisely to keep using Firebase Studio, push your code to GitHub every fifteen minutes. If you know what’s good for you, you’ll shift completely over to another development environment and coding agent, like Copilot, or any other coding agent in the world.
If you should choose to make the unwise decision to keep using Firebase Studio, be ready for it to make a mistake so basic it defies description: it puts the changes in the wrong place. Instead of putting changes in a src directory, it puts them in home/studio/project/src, which has the effect of creating a new, useless directory in your project which has no effect on anything. It’s like writing…
