Codex Desktop: adding a Source folder does not update workspace permissions for existing tasks

No source files or tests are named. Trace the Codex Desktop Source folders flow and compare how workspace_roots and filesystem permissions are established for existing versus newly created tasks. Done means existing tasks receive the updated access, or the UI clearly tells users that a new task is required.

What version of the Codex App are you using?

Not captured. The issue was reproduced on July 27, 2026.

What subscription do you have?

Not included in this report.

What platform is your computer?

macOS (Apple Silicon).

What issue are you seeing?

When a folder is added to a Codex Desktop project's Source folders, an already-existing task does not receive the updated workspace root or filesystem permission. Creating a new task in the same project after adding the folder does receive the updated permissions and can read files from that folder.

This makes the Source folders UI appear to have applied the change, while the active existing task continues using stale workspace/permission state.

The behavior is consistent with workspace roots and filesystem permissions being snapshotted at task creation and not refreshed for existing tasks. That is only a hypothesis; the internal implementation was not inspected.

What steps can reproduce the bug?

1. Create or open a Codex Desktop project with an existing task.
2. Confirm that a folder outside the current workspace roots is not available to that task.
3. Add that folder to the project's Source folders.
4. Return to the already-existing task.
5. Observe that the task's effective workspace_roots and filesystem permissions do not include the newly added folder, and reading a file from it fails.
6. Create a new task in the same project without changing the Source folders again.
7. Observe that the new task's workspace_roots and filesystem permissions include the folder.
8. Read an image file from the folder in the new task; the read succeeds.

What is the expected behavior?

After a folder is added to a project's Source folders, existing tasks in that project should either:

• receive the updated workspace roots and filesystem permissions, or
• clearly inform the user that the change only applies to newly created tasks and that a new task is required.

The current behavior silently leaves existing tasks with stale permissions.

Additional information

Observed comparison:

• Existing task created before Source folder addition: folder absent from effective workspace roots/permissions; file read unavailable.
• New task created after Source folder addition: folder present in workspace_roots; folder present in filesystem permissions; actual PNG file read succeeded.

No credentials, environment files, or sensitive file contents were accessed or included in this report.