Hi, I tried to reproduce this but couldn’t trigger it.
I tested multiple prompts, tabs, and sessions (including incognito), and everything worked normally. This suggests it’s not a general issue, but likely tied to specific account or chat state.
Given the symptoms (owner locked out, both new and existing chats affected, deployments still working), this looks like a backend mismatch between chat ownership, workspace, and session.
It might be worth checking chat ownership/workspace assignment and permission validation on message requests.
Hope this helps