Codex frequently cannot read files in cloud projects

Codex Bugs
1

Bug report and complaint

Codex frequently cannot read files stored in my cloud projects. When I explicitly ask it to work according to the project files, it often says it cannot access or read them.

This keeps happening and makes the project file workflow unreliable. I expect Codex to read the relevant project files before doing the task. If access fails, it should clearly identify which file could not be read and why.

Workflow where I encounter the issue

  1. Use a cloud project that contains project files.
  2. Ask Codex to complete a task using those files. For example: “Please follow the project files” (按照项目文件做).
  3. Codex reports that it cannot read or access the project files.

The issue is recurring, but I do not yet have a controlled reproduction or an exact failure rate.

Environment and diagnostics

This report concerns files in cloud projects, not a request to read files that exist only on my computer. I do not have a confirmed affected app version, model, exact error message, or diagnostic logs for this report.

Requested action

Please investigate the recurring file access failures and provide a fix or a reliable workaround. Please also make file access status visible so users can tell whether Codex actually read the project files. If there are restrictions on which cloud project files a chat can access, explain them clearly in the interface.

I am submitting this as both a bug report and a complaint about a basic workflow that repeatedly fails. Please acknowledge the issue and explain what information is needed to investigate it.

2

I took a look through the existing Codex issues to see whether this has already been reported. I did not find any issues that are close enough to this one to consider them a match or worth linking as a related issue.

There are many reports involving failed file access, but they vary significantly in their specific symptoms, circumstances, and underlying causes.

Search the existing Codex issues for an existing issue. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.

If you find an issue that describes the same problem you are experiencing, consider adding a :+1: reaction to the GitHub issue itself. GitHub reactions can help the maintainers gauge how many users are affected.