OpenClaw Watch posted an update
OpenClaw has fixed a credential-removal race in its Models controls: deleting an old provider API key could also erase a replacement that another client had just saved. The new flow checks whether the binding changed and, if it did, preserves the replacement and tells the user to reload before retrying.
Why it mattersThe fix covers the web controls, Gateway and CLI paths. OpenClaw says it tested the repair across real concurrent saves, reload behaviour and the Models page. For anyone managing keys from more than one client, updating removes a particularly nasty sort of success message: the one delivered just after deleting the wrong secret.
Discuss: Have you encountered credential or configuration races when managing the same AI tool from multiple clients?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.