ChatGPT Plus – File Creation Blocked by Read-Only Filesystem in Normal Chat (Errno 30)

ChatGPT Bugs
1

ChatGPT Plus – Read-Only Filesystem Preventing File Creation and Downloads

Issue started: 24 October 2026

I’m a paying ChatGPT Plus subscriber, and I’ve suddenly lost the ability to create and download files in regular ChatGPT conversations.

Until today, I could generate Word documents, PDFs, Excel spreadsheets, ZIP archives and other downloadable files without problems.

Now, whenever I ask ChatGPT to create a file, the operation fails because the execution environment appears to be configured as read-only.

This has seriously interrupted my work because I rely on ChatGPT’s file-generation capabilities.

1. Exact error messages

When attempting to create a simple text file, the system returned:

patch rejected: writing is blocked

by read-only sandbox;

rejected by user approval settings

Earlier Python file-writing attempts also produced:

OSError: [Errno 30] Read-only file system

The execution environment has reported:

sandbox_mode: read-only

ChatGPT can generate the requested text in its response, but it cannot write the file to disk or provide a genuine downloadable file.

2. Platforms and configurations tested

I have performed extensive troubleshooting using the same ChatGPT Plus account.

Platform| Result

Google Chrome on Windows| Failed

Microsoft Edge on Windows| Failed

ChatGPT Android application| Failed

Regular ChatGPT with different thinking settings| Failed

ChatGPT Work experience| File generation works

An important finding is that file creation works in the separate ChatGPT Work experience but fails in regular ChatGPT.

I primarily use normal ChatGPT because it better suits my everyday workflow. I previously had working file-generation capabilities there.

3. Troubleshooting already completed

I have tried:

- Starting completely new conversations.

- Signing out and signing back into ChatGPT.

- Clearing browser cache, cookies and history.

- Testing Chrome in Incognito mode.

- Disabling browser extensions.

- Switching from Chrome to Microsoft Edge.

- Testing different thinking settings.

- Testing the official Android application.

- Repeating file-creation tests.

I also deleted my previous ChatGPT conversations during troubleshooting.

None of these steps restored file-writing access in regular ChatGPT.

4. When the problem started

Everything was working normally before 24 October 2026.

The issue became apparent shortly after I submitted a TikTok video link for analysis. ChatGPT successfully analysed the video.

I do not know whether this event is connected to the filesystem restriction. I am including it only because it preceded the problem.

5. Expected behaviour

As a ChatGPT Plus subscriber, I expect regular ChatGPT to be able to:

- Create downloadable text files.

- Generate Word documents and PDFs.

- Create spreadsheets.

- Package files into ZIP archives.

- Provide working download links for successfully generated files.

These capabilities worked previously.

6. Actual behaviour

The execution environment is read-only.

File-writing attempts are rejected before the requested file can be created.

This is not simply a broken download link or an expired temporary file. The file itself cannot be written.

7. Impact on my work

I am paying for ChatGPT Plus, and this issue is preventing me from completing work that previously functioned normally.

I have spent considerable time testing browsers, devices and configurations without success.

The inability to generate downloadable documents and files has disrupted my workflow and delayed ongoing projects.

8. OpenAI Support

I have already contacted OpenAI Support and have an ongoing case being handled by Nerisa.

Support has acknowledged the read-only filesystem error and requested additional testing to identify the cause.

I have completed multiple tests and supplied screenshots showing the failures.

9. Questions for the community and OpenAI

I would particularly like to know:

1. Has anyone else experienced “[Errno 30] Read-only file system” in regular ChatGPT?

2. Has anyone suddenly lost file-generation capabilities that previously worked?

3. Has anyone experienced file creation working in ChatGPT Work but failing in normal Chat?

4. Is this a known execution-environment permissions issue?

5. Has anyone successfully restored write access, and if so, how?

6. Can OpenAI investigate whether an incorrect filesystem permission profile is being assigned to affected regular ChatGPT sessions?

Any confirmed solution, explanation or information from others experiencing the same problem would be greatly appreciated.

I would especially welcome guidance from OpenAI’s technical team, as the usual browser troubleshooting has not resolved the issue.

Thank you.

2

Exactly same issue for me and I have tried the same troubleshooting steps to no success. The error is that my “workspace is read only” but then frustratingly chat will tell me I need to set the workspace to write, but then say it’s not something I can set my side because it is server side.

This started for me about 3 days ago out of nowhere. Chat will keep trying to send me to Work (which does work with write access) but I want to be able to simply create simple basic documents in Chat without needing to involve Work mode.

The only thing I discovered, which idk if it’s the same for you - sometimes if I set the thinking mode in Chat to Instant, it suddenly works for wriee access. However, as soon as you set it to Medium or High, it has write access issues again. And Instant does not always work every time, so it’s annoying!

3

I’m experiencing the same issue in regular ChatGPT. As a simple test, I asked it to create a .txt file containing only “hola”. File creation failed before any download link could be generated:

patch rejected: writing is blocked by read-only sandbox; rejected by user approval settings

I repeated the test and got the same error. So, at least in my session, this is not an expired or broken download link—the file cannot be written in the first place.

I haven’t tested the Instant-mode workaround yet. Has OpenAI confirmed whether affected sessions are being assigned a read-only permission profile, and whether a fix is being investigated?