I found what looks like a stale conversation/runtime state bug involving Lockdown Mode and the GitHub connector.
Steps to reproduce
-
Enable Lockdown Mode.
-
Use an existing conversation that has access to the GitHub connector.
-
Attempt a GitHub action while Lockdown Mode is enabled.
-
Turn Lockdown Mode off.
-
Return to the same conversation.
-
Attempt another GitHub action.
Actual behavior
The existing conversation continues to behave as if GitHub is permanently disabled and returns:
“GitHub tool has been disabled. Do not send any more messages to GitHub.”
This persists even though Lockdown Mode is already disabled in the UI.
Expected behavior
After Lockdown Mode is turned off, the conversation should either:
-
refresh/reinitialize connector permissions automatically, or
-
clearly indicate that a new conversation/runtime is required.
Important confirmation
I tested the exact same GitHub connection in a fresh conversation after disabling Lockdown Mode, and it worked immediately:
-
GitHub authentication succeeded
-
authenticated account was detected correctly
-
repository listing worked
-
repository permissions were returned normally
So the GitHub connector/account itself is healthy. The issue appears isolated to the existing conversation runtime retaining the disabled connector state.
Environment
-
ChatGPT desktop app
-
Windows
-
ChatGPT Plus
-
GitHub connector
-
Observed: 22 Aug 2026, around 9 AM IST
This looks like a connector capability state that gets latched when Lockdown Mode blocks the tool and is not reinitialized when Lockdown Mode is turned off.