codex - 💡(How to fix) Fix Feature request: allow configuring local storage path for Codex VS Code sandbox, cache, sessions, and logs on Windows [2 comments, 3 participants]

What version of the IDE extension are you using?

vscode

What subscription do you have?

allow configuring local storage path for Codex VS Code sandbox, cache, sessions, and logs on Windows

Which IDE are you using?

vscode

What platform is your computer?

win10 x64

What issue are you seeing?

Summary

I would like to request better control over where the Codex VS Code extension stores local sandbox, cache, session, log, and runtime files on Windows.

Currently, Codex appears to create a large number of folders and files under the Windows user profile directory, such as:

• .sandbox
• .sandbox-bin
• .sandbox-secrets
• .tmp
• archived_sessions
• cache
• memories
• sessions
• skills
• tmp
• vendor_imports
• auth.json
• config.toml
• logs_*.sqlite
• state_*.sqlite
• related SQLite WAL/SHM files

I understand that some local files are required for sandboxing, session management, caching, authentication, and normal extension functionality. However, placing many Codex-related files directly under the Windows user profile directory can make the local development environment harder to manage.

Environment

• OS: Windows
• Editor: VS Code
• Extension: Codex VS Code extension
• Account type: ChatGPT Business

Current behavior

Codex creates multiple local folders and files under the Windows user profile directory. Over time, this can result in many Codex-related artifacts being mixed with other application and development tool configuration files.

Impact

This causes several usability and manageability concerns:

1. The Windows user profile directory becomes harder to inspect and maintain.
2. Codex-generated folders and files are mixed with other local development configuration files.
3. Users may not know which files are safe to delete.
4. C drive storage usage may grow unexpectedly.
5. Business and Enterprise users may have stricter local storage, security, and compliance requirements.
6. It is difficult to tell which files are required, temporary, archived, or safe to clean up.

Requested improvements

I would like to suggest the following improvements:

1. Add an option to configure the local storage path for Codex sandbox, cache, sessions, logs, and runtime files.
2. Store all Codex-generated files inside one clearly named dedicated directory, such as .codex or Codex, instead of creating many folders and files directly under the user profile directory.
3. Add VS Code extension settings for:
   • Viewing the current Codex local storage path;
   • Changing the local storage path;
   • Clearing cache, old sessions, and archived sandboxes;
   • Setting a maximum local disk usage limit.
4. Provide documentation explaining:
   • What local files Codex creates;
   • What each file/folder category is used for;
   • Which files are safe to delete;
   • How to reset or clean up local Codex state.
5. Consider additional controls for Business and Enterprise environments.

Expected behavior

Codex should either:

• store its local files in a single clearly scoped directory by default, or
• allow users to choose a custom storage location, especially on Windows.

For example, users could configure Codex to store local files under:

D:\Codex

### What steps can reproduce the bug?

common using

### What is the expected behavior?

_No response_

### Additional information

_No response_