When using a database that's not called dbname the tools get too flaky #32
Description
One small snag I ran into. On my "production" database that i use for paulie.dev, I changed the database name from neondb. This seemed to cause Claude a few issues. I did a quick dump and restore to a new database and left the name alone, and Claude seemed much happier.
I heard tell of a similar issue with the create branch GitHub Action that had issues when database names had been changed from neondb. Perhaps this is something you're already aware of, just thought i'd mention it. 🙂
My suspicions are:
The issue is, we make a lot of parameters optional, like the DBname . So, the LLM sees that it's optional and sometimes it doesn't pass anything for that parameter because it's not sure what to pass, and our "default" for when nothing is passed in, is neondb. So it's not a super easy problem to tackle, because more often than not, it's a problem with the human, that's not passing enough context, although, I'm not sure if this was the case this time around!