hey everyone.
wanted to give you a clear picture of what went on with the proxy settings over the past day.
what happened
we redesigned the proxy settings panel. the old system that managed proxy configs had been built up over a long time with a lot of messy legacy code underneath. when we rebuilt the UI on top of it, some of that old plumbing broke in a way that caused config data to get sent as empty values when you hit save. that is what wiped people’s proxy URLs, models and prompts.
the underlying issue was old technical debt that should have been cleaned up a long time ago. the panel redesign just exposed it. this also wasnt caught in testing because the bug only manifested in production builds.
were api keys leaked to other users?
no. we understand the concern and we looked into this thoroughly. every database query and API response is scoped to your user ID from your login session. there is no code path that returns another user’s data to you.
what people saw was their own old config data coming back from local browser storage after the server-side data got cleared by the bug. the new panel formats things differently so it looked unfamiliar.
what we fixed
- resolved the legacy data handling issue that was silently blanking configs on save
- saves now always go through to the server properly
- editing a config and clicking save now correctly captures everything you typed
- added a Recover button in proxy settings to restore previous configs from recent account history
- added backend protections so empty config data cannot overwrite existing configs
we are continuing to clean up the old proxy settings code and will keep you updated as we ship improvements.