Security concern: Codex VS Code extension stores chat history and auth data on shared Remote-SSH Linux account

Resolved 💬 2 comments Opened May 8, 2026 by Kiddin75 Closed May 8, 2026

What variant of Codex are you using?

IDE Extension

What feature would you like to see?

In our lab’s server environment, master’s students are required to share a single Linux account, while only PhD students are given individual Linux accounts.

In this setup, using the VS Code Codex extension introduces a serious security concern. Since Codex chat history and authentication/session data appear to be stored under the shared Linux user directory on the remote server, other users who share the same Linux account may be able to view my Codex chat history. More importantly, they may also be able to use my OpenAI account and consume my Codex quota directly.

This makes the Codex extension unsafe to use in Remote-SSH development environments where multiple people share the same Linux account.

It would be very helpful if the Codex VS Code extension could support storing chat history, session state, and authentication data on the local client instead of the remote server, or at least provide a configurable option for local storage or per-user session isolation.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗