VS Code reconnect resets Full Access permissions and desynchronizes the chat UI #36198

What version of the IDE extension are you using?

openai.chatgpt@26.721.41059

What subscription do you have?

ChatGPT Pro

Which IDE are you using?

VS Code 1.131.0, connecting from Windows to a remote Linux workspace

What platform is your computer?

Client: Windows x64

Remote workspace:

Linux 6.8.0-1061-aws x86_64 x86_64

What issue are you seeing?

When a Goal is started with the Full Access permission profile, the agent initially operates with the expected permissions. If VS Code disconnects from the remote workspace and then reconnects, the resumed Goal/chat appears to lose that permission state and begins requesting approval for operations again.

The same reconnect also leaves the chat UI in a broken or desynchronized state:

• Newly submitted messages do not appear immediately.
• The scroll position behaves incorrectly or jumps out of place.
• The conversation feels stale or out of sync after reconnecting.

These symptoms occur in the existing Goal/chat after the VS Code connection is restored. The combination suggests that the resumed chat/runtime and the visible chat state may not be fully rehydrated after reconnect.

What steps can reproduce the bug?

1. On Windows, open VS Code and connect to a remote Linux workspace.
2. Open the Codex IDE extension.
3. Start a Goal and select Full Access.
4. Continue the Goal long enough to confirm that the agent can perform operations without repeatedly requesting permission.
5. Disconnect VS Code from the remote workspace, either through a connection interruption or by closing/disconnecting the remote session.
6. Reconnect VS Code to the same remote workspace.
7. Resume the same Goal/chat.
8. Ask the agent to continue operations that were previously permitted.
9. Observe that it requests access/approval again as though the Full Access profile was lost.
10. Submit additional chat messages and scroll through the conversation.
11. Observe that new messages may not render immediately and that the scroll position or conversation layout behaves incorrectly.

What is the expected behavior?

After VS Code reconnects to the same remote workspace, the existing Goal/chat should resume with its selected Full Access permission profile intact.

The chat UI should also rehydrate consistently: submitted messages should appear immediately, the conversation should remain correctly ordered, and scrolling should remain stable.

If the permission profile cannot safely be restored, the extension should clearly show that the session state changed and request one explicit reauthorization instead of silently reverting to repeated permission prompts.

Additional information

This affects long-running Goals because a transient VS Code disconnect changes both agent behavior and the usability of the existing conversation.

Potentially related but not an exact duplicate:

• IDE: resumed compacted thread loses exec/code-mode tools on Responses WebSocket #35751 — resumed VS Code Remote threads can lose their usable tool surface even when danger-full-access is requested: IDE: resumed compacted thread loses exec/code-mode tools on Responses WebSocket #35751
• Codex IDE chat loses SSH/network access after idle/resume in same conversation #29866 — an IDE chat can lose network access after idle/resume: Codex IDE chat loses SSH/network access after idle/resume in same conversation #29866

The additional chat rendering and scrolling symptoms may help identify whether the reconnect is restoring stale or incomplete per-thread state.