Codex macOS app omits project source folder from new task workspace roots and writable permissions

Open
#37,731 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, rust
Domain
desktop, security

Research direction

Start by tracing how project source folders are carried into a newly created task's workspace_roots and permission_profile.file_system, including the configuration path across app relaunch. Reproduce with primary and secondary repositories, then verify that every configured folder receives workspace and writable permission entries without an approval prompt.

Written by the indexing model from the issue text.

Description

app bug sandbox
What version of the Codex App are you using (From “About Codex” dialog)?

26.803.41515

What subscription do you have?

PRO

What platform is your computer?

macOS 26, arm64

What issue are you seeing?

A secondary source folder configured on a Codex project which is not propagated to new tasks created for that project.

I added both repositories to the project:

/Users/nooblyf/github/pang
/Users/nooblyf/github/pang-server

I added the server folder before creating the task, fully quit and relaunched Codex Desktop, then created a new task. Despite this, the injected task context only includes the primary repository:

workspace_roots:
  - /Users/nooblyf/github/pang

The server repository is also absent from the writable entries in permission_profile.file_system. The agent can read it through broader read access, but writing to it requires an approval prompt.

This is not stale state from an existing task. The folder was configured before task creation and the app was relaunched first.

What steps can reproduce the bug?
  1. Create or open a Codex project.
  2. Add two local repositories as source folders.
  3. Ask Codex what permissions has in this project.
  4. Fully quit Codex Desktop.
  5. Relaunch the app.
  6. Create a new task under that project.
  7. Ask Codex which workspace roots and writable paths it received.
  8. Observe that only the primary folder appears.
  9. Ask Codex to modify a file in the secondary folder.
  10. Observe that the write requires out-of-sandbox approval.
What is the expected behavior?

Every source folder configured on the project before task creation should:

  • appear in the new task's workspace_roots;
  • receive the appropriate writable permission entry;
  • allow ordinary file changes without additional approval.

The project configuration should remain effective after relaunching the app.

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.