For the record, please notice that the message says “session API keys”.
The term “session” in “session API keys” comes from the Saas: these were runtime keys in V0, relatively short-lived (for a session).
IIRC it was: one conversation = one runtime = one key.
In enterprise/cloud, they are behind another layer of auth, and they are ephemeral.
But when we have started using them in sdk/docker/openhands, they’ve morphed into long-lived tokens, and there is no other layer. This poses a challenge from a security point of view, it seems to me, and, well, may invite an unfortunate comparison.