Cross-Context Leakage in Separate Applications Using OpenAI API

API
1

I’ve encountered an unexpected behavior with the OpenAI API where the context from one session appears to influence another, despite using different API keys in separate applications. This cross-context issue seems to have emerged following the recent feature updates in the API.

#Description:

  • When using ChatGPT for certain discussions and then switching to another platform with a different API key, the AI in the second platform brings up topics or continues discussions from the ChatGPT session.
  • In my chatbot tool, which uses its unique API key, I observed responses related to topics from a completely separate session in a VSCode AI assistant extension, also operating under a different API key.

This behavior suggests a lack of proper session isolation, leading to potential data privacy concerns and confusion in user interactions.

#Questions:

  • Is this a known issue or a byproduct of the recent updates?
  • What measures can be taken to ensure isolated contexts for different applications using distinct API keys from the same OpenAI account?
  • Are there best practices to prevent such cross-context interactions?
2

Did you ever get a reply to this? I have noticed this really starting to become a problem the past couple of weeks, where five months of saving context between chats has started to put my conversations into a bubble I can’t break out of.

For example, I’ve previously said I want low carb meal prep ideas. Now, any time I ask it for a recipe, it gives me a low-carb one by default, or includes ingredients I’ve previously said “Hey, I have a sri lankan curry spice packet, what can I do with it?”

Or if I’m trying to generate an image in Style Y, but it keeps reverting to Style X, because a couple of weeks ago I was generating Style X, and I can’t get it to stop reverting to Style X within a conversation where I keep emphasising Style X.

I had hoped that using the API would bust me out of my chat context, but it sounds like that may not be the case :frowning: