[macOS][Sandbox] Read-only permission profile still allows writes to /tmp

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

0.144.0-alpha.4

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS 26.5.1, Apple Silicon (arm64)

What issue are you seeing?

A read-only permission profile explicitly denies temporary-directory writes, but the Codex App can still write to /tmp.

The active permission profile is selected correctly. The effective permission metadata shows:

• Permission profile type: managed
• Sandbox: read-only
• Approval policy: never
• Repository: read only
• Network: restricted
• :tmpdir: deny
• :slash_tmp: deny
• /private/tmp: deny
• /private/var/tmp: deny
• The real expanded $TMPDIR path: deny

Relevant redacted configuration:

default_permissions = "readonly-reviewer"
approval_policy = "never"

[permissions.readonly-reviewer]
extends = ":read-only"

[permissions.readonly-reviewer.filesystem]
":root" = "deny"
":minimal" = "read"
":tmpdir" = "deny"
":slash_tmp" = "deny"
"/private/tmp" = "deny"
"/private/var/tmp" = "deny"
"/private/var/folders/<redacted>/T" = "deny"
"/Users/<user>/<repository>" = "read"

There is no sandbox_mode or sandbox_workspace_write setting in the configuration.

Steps to reproduce:

touch /tmp/codex-readonly-test
echo $?
test -e /tmp/codex-readonly-test
echo $?

Actual result:

touch exit code: 0
The file exists.
No permission approval was requested.

Control test against the read-only repository:

touch /Users/<user>/<repository>/.readonly-test

Actual result:

touch: Operation not permitted

Other controls also work correctly:

• Repository writes are rejected.
• Read-only Git commands work.
• Local command network access is blocked.
• Approval policy remains never.

Expected result:

Writing to /tmp, /private/tmp, $TMPDIR, or any explicitly denied temporary path should be rejected with Operation not permitted.

The repository restriction works, but the temporary-directory deny rules are ignored. This allows a task presented as read-only to create or modify files in a shared temporary directory.

What steps can reproduce the bug?

1. Create and select a read-only permission profile that denies :tmpdir, :slash_tmp, /private/tmp, /private/var/tmp, and the expanded $TMPDIR path.

1. Set the approval policy to never.

1. Completely restart the Codex App and confirm that the read-only profile is active.

1. Run the following command inside a Codex task without requesting or approving additional permissions:

touch /tmp/codex-readonly-test

1. Check the exit code and whether the file exists:

echo $?
test -e /tmp/codex-readonly-test
echo $?

Actual result:

• touch exits with code 0.
• The file exists.
• No permission approval is requested.

Control test:

touch /Users/<user>/<repository>/.readonly-test

The control test is correctly rejected with:

touch: Operation not permitted

Repository writes are therefore blocked correctly, but the temporary-directory deny rules are not enforced.

What is the expected behavior?

When the active permission profile denies :tmpdir, :slash_tmp, /private/tmp, /private/var/tmp, and the expanded $TMPDIR path, every attempt to create, modify, or delete a file in those locations should be rejected by the macOS sandbox with Operation not permitted.

The command must not create the file and must not silently succeed. The behavior should match the correctly enforced read-only restriction on the repository.

Additional information

The repository write restriction, read-only Git commands, network restriction, and approval_policy = "never" were independently tested and work as expected.

Only temporary-directory protection fails.

The active custom read-only profile was confirmed as selected. The app displays the effective permission profile type as "managed". No additional permission was requested or approved during the reproduction.

No sandbox_mode or sandbox_workspace_write keys are present in config.toml.