Codex Desktop should not automatically create date-based folders in Documents without user control

ChatGPT Feature requests
, , , ,
1

I would like to report a workflow and local-data-management issue introduced by recent Codex Desktop updates.

I previously maintained a dedicated local folder for Codex-generated work:

/Users/<user>/Codex

This was intentional. I organize my work by project, not by conversation date. Each AI or tool I use has its own dedicated folder, which keeps generated files separate from my personal documents, makes backups predictable, and lets me decide what should be retained.

After the recent update, projectless Codex chats began automatically creating folders under:

/Users/<user>/Documents/Codex/<YYYY-MM-DD>/<conversation-name>/

For example:

/Users/<user>/Documents/Codex/2026-07-23/new-chat

I could not find a setting to:

  • choose the default workspace/output directory;
  • prevent Codex from using Documents;
  • disable automatic folder creation for projectless chats;
  • choose a different folder structure;
  • change the date format;
  • organize generated work by project instead of date;
  • reuse an existing workspace as the default location.

The date-based hierarchy is itself a significant issue. Codex is automatically creating a structure in YYYY-MM-DD format, followed by the conversation title. I was not asked whether I wanted date-based organization, whether I preferred year/month/day hierarchy, or whether I wanted files grouped by project, client, repository, or another structure.

Date-based folders may work for some workflows, but they are not a neutral default. In my case, they fragment related work across multiple days and conversations. A project can span weeks or months, so its drafts, reports, assets, and generated code can end up distributed across many folders that have no meaningful relationship to the project itself.

This is especially problematic because Documents is a personal, user-managed location. Automatically writing AI-generated files there can:

  • add unnecessary, temporary, or duplicate files to personal backups;
  • mix AI-generated work with personal and professional documents;
  • create storage growth that the user did not plan for;
  • make cleanup and retention harder;
  • fragment project material across date-based folders;
  • conflict with an established “one workspace per AI/tool” organization;
  • reduce user control over locally generated data.

The behavior also creates a migration problem. Users who already had a well-organized Codex workspace may suddenly have work split between an existing project-based directory and a new date-based directory under Documents.

I believe Codex Desktop should provide the following controls:

  1. A configurable default workspace/output directory.
  2. An option to disable automatic persistent folder creation for projectless chats.
  3. A choice between date-based, project-based, conversation-based, or custom folder organization.
  4. Configurable date formatting, if date-based organization is enabled.
  5. An “open existing workspace” flow that can become the default destination for future work.
  6. A clear prompt before the first persistent file is written, showing the exact target path.
  7. A distinction between temporary session files and persistent user deliverables.
  8. A migration tool or guided workflow for users whose files were automatically created in the new location.
  9. Clear release-note communication when local storage behavior or default paths change.

I understand the value of automatic organization, but it should be opt-in or configurable. Users who have established local file-management and backup practices need control over where Codex writes files, how folders are named, and whether work is organized by project or by date.

1 Like