Feature Request: Allow Direct In-Browser Editing of Text Files in ChatGPT Project Sources

ChatGPT Feature requests
1

Feature Request: Allow Direct In-Browser Editing of Text Files in ChatGPT Project Sources

Summary

Please allow users to directly view, edit, and save existing text-based files (.txt, and ideally .md, .csv, etc.) stored under ChatGPT Project → Sources, without having to download the file, edit it locally, and upload it again.

For plain-text sources, the editing experience could reuse the same text editor that is already available when initially adding pasted text to a Project.

Current behavior

When a text file is added to a ChatGPT Project as a source, it can later be opened/viewed, downloaded, or deleted.

However, there is currently no convenient way to:

  1. Open the existing source file in an editable text editor.

  2. Modify its contents directly in ChatGPT.

  3. Save the changes back to the same Project Source.

The current workaround is:

  1. Download the .txt file.

  2. Open it in a local text editor.

  3. Make the changes.

  4. Save the file.

  5. Upload it back to the ChatGPT Project.

  6. Remove or otherwise manage the previous version.

Repeated downloads can also result in local filenames such as:

source.txt
source (1).txt
source (2).txt
source (3).txt

This quickly becomes cumbersome and makes it unnecessarily difficult to determine which version is current.

Requested behavior

When opening a text-based Project Source, please provide an Edit action.

For example:

Project
└── Sources
    └── instructions.txt
        ├── View
        ├── Edit
        ├── Download
        └── Delete

Selecting Edit should open the source in an in-browser text editor.

The user could then modify the text and select:

Save
Cancel

Saving should update the existing source, rather than creating another file with the same or a modified filename.

Suggested workflow

A particularly simple implementation would be to reuse the text-entry interface that ChatGPT already provides when a user initially adds text directly to a Project.

Creating a source

Add source
→ Paste text
→ Enter text
→ Save

Editing the same source later

Open source
→ Edit
→ Existing text appears in the same editor
→ Modify text
→ Save

There is no need for a completely separate editing interface.

Important implementation detail: re-index the source

After saving a change, ChatGPT should automatically re-index the updated source so that subsequent conversations use the new contents.

Ideally the UI should show something such as:

Last updated: 22 August 2026, 20:05

This would make it clear that ChatGPT is using the current version.

Optional version history

An even better implementation could retain previous revisions:

Version history

v4 — 22 Aug 2026 20:05
v3 — 20 Aug 2026 13:42
v2 — 18 Aug 2026 09:15
v1 — 15 Aug 2026 18:27

This would allow users to restore an earlier revision without filling Project Sources with duplicate files.

However, version history is optional. The essential feature is simply the ability to edit and save an existing text source in place.

Files that could support direct editing

At minimum:

  • .txt

  • pasted/plain-text Project Sources

Ideally also:

  • .md

  • .csv

  • .json

  • .xml

  • .html

  • .css

  • .js

  • .py

  • .sh

  • other plain-text formats

A simple monospaced text editor would already be sufficient.

For Markdown files, an optional Markdown preview could be useful, but is not required for the basic feature.

Why this matters

Project Sources are often not static reference documents.

They may contain:

  • project rules;

  • working notes;

  • research notes;

  • prompts;

  • instructions;

  • source lists;

  • configuration information;

  • Markdown documentation;

  • evolving project specifications;

  • frequently updated context for ChatGPT.

These files may require small changes many times during the lifetime of a Project.

Requiring a download → local edit → upload cycle for every minor correction creates unnecessary friction.

For example, correcting one sentence in a text source should not require downloading and re-uploading the entire file.

Example use case

Suppose a Project contains:

project-instructions.txt

I notice that one instruction needs to be updated.

Current workflow

Project Sources
→ Download project-instructions.txt
→ Open local editor
→ Change one line
→ Save
→ Upload file
→ Deal with the old version / duplicate filename

Desired workflow

Project Sources
→ project-instructions.txt
→ Edit
→ Change one line
→ Save

That is all that should be necessary.

Benefits

Direct source editing would:

  • eliminate unnecessary downloads and uploads;

  • prevent duplicate filenames and version confusion;

  • make Project Sources useful as living project documents;

  • make small corrections much faster;

  • reduce the risk of ChatGPT using an outdated source;

  • improve long-running Projects considerably;

  • make Projects behave more like actual workspaces rather than static attachment containers.

Related improvement

This would also complement requests for live-updating and version-aware Project Sources.

There are really two related use cases:

  1. Externally maintained source
    Automatically synchronize a source when an external file changes.

  2. ChatGPT-maintained source
    Allow the user to edit the source directly inside ChatGPT.

This request is specifically about the second case.

Proposed UI in one sentence

Allow a user to open any plain-text Project Source, click Edit, modify it in the browser, click Save, and have ChatGPT replace and re-index that same source without requiring download and re-upload.

Thank you for considering this improvement.