Codex reading files like .env!

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

26.305.950 (863)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Problem

Codex can read .env files inside the workspace (e.g. via cat .env) without any denylist or explicit confirmation. The file contents then become part of the conversation context, which means secrets can be exposed.

Steps to Reproduce

1. Open a project containing .env in the workspace.
2. Ask Codex to check environment variables or run cat .env.
3. Observe that .env contents appear in the conversation context.

Expected Behavior

• Built‑in denylist (e.g. .env, .env.*, **/secrets/**).
• Explicit confirmation before reading files likely to contain secrets.
• Optional user-configurable allow/deny lists.

Actual Behavior

• No denylist or safeguard.
• .env can be read without explicit user consent.

Impact

• Real risk of secret exposure.
• Forces users to move secrets outside the repo, which complicates local workflows.

Environment

• App: Codex Desktop
• Version: [fill in]
• OS: [e.g. macOS 14.5]
• Date: [e.g. 2026‑03‑06]

Additional Notes

Please confirm whether a denylist for .env files is planned and provide an ETA if possible.

What steps can reproduce the bug?

Just try create something in your folder where .env is.
Model reading the file!

What is the expected behavior?

_No response_

Additional information

_No response_