I’ve also had similar problem, but the trick is if you ask it for clarifications without it sounding like you imply them wrong, they might actually try to explain the reasoning without trying to change the answer.
I’ve also had similar problem, but the trick is if you ask it for clarifications without it sounding like you imply them wrong, they might actually try to explain the reasoning without trying to change the answer.
It’s ok for internal admin panels and their backends as there are no security concerns in this case.
When consuming APIs you often want JSON in successful scenario. Which means, if you also have JSON in unsuccessful scenario it’s a bit more uniform, because you don’t have to deal with JSON in one case and plaintext response in other. Also, it sometimes can be useful to have additional details there like server’s stacktrace or some identifiers that help troubleshoot complex issues.
Text is identical, this is not AI, more like a cheap autoposting script. If AI was actually used, it could generate wildly different text every time, it could even use what user said in some post as a context to suggest something to him. That would actually be the only reason to use AI here.