TL;DR
OpenAI Codex is still working on a feature to allow users to exclude sensitive files from being read or sent to the model. The issue was reopened after being closed in favor of a Rust-based solution, but a comparable feature has not yet been implemented.
OpenAI Codex continues to lack a robust mechanism for users to explicitly exclude sensitive files from being read or transmitted to the model, despite ongoing discussions and feature proposals. This issue remains unresolved, raising concerns about data privacy and security for developers and organizations using the platform.
The issue, originally raised on Hacker News, calls for a feature that allows users to mark specific files or paths—such as .env, .pem, or .ssh—to prevent them from being accessed or sent to the model. The proposed solution includes a configuration system with a repository-local .codexignore file and a global ignore list, similar to mechanisms used in other development tools.
Although the feature was initially discussed extensively and was slated for development, the issue was closed in favor of a Rust-based implementation called codex-rs. As of late August 2025, no comparable feature appears to exist within codex-rs, and discussions about a standardized, shareable, and deterministic configuration system have been restarted. The community is eager for a solution that balances security with usability, but no official timeline has been provided.
Why Sensitive File Exclusion Remains a Critical Need
This ongoing challenge highlights the importance of data privacy and security in AI development tools. Without an effective way to exclude sensitive files, organizations risk unintentional data leaks, potentially exposing confidential information. The lack of a standardized exclusion mechanism also complicates compliance efforts and could hinder broader adoption of Codex in sensitive environments.
Cal-Van Tools 693 Ignition Point File
Made of super hard, high quality steel with Rockwell hardness of 65
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background of Exclusion Features in AI Code Tools
The feature request originated from user discussions on Hacker News, where developers expressed concern over the inability to reliably prevent sensitive files from being read or transmitted by Codex. The issue was formally tracked, with initial proposals advocating for a deterministic ignore configuration similar to .gitignore files. Despite the importance of this feature, OpenAI shifted focus to a Rust implementation, codex-rs, which as of August 2025, does not yet support this functionality. The debate reflects broader industry concerns about AI security and privacy controls.
“A mechanism to explicitly mark files/paths that the agent must not read or send to the model is still missing in Codex, and this remains a significant gap.”
— Hacker News user
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Challenges in Implementing File Exclusion
It is not yet clear when or if a standardized, shareable exclusion feature will be integrated into OpenAI Codex or codex-rs. The technical hurdles, community consensus, and OpenAI’s development priorities remain to be seen, leaving the timeline and scope uncertain.
Lomil Identity Protection Roller Stamps 2 Pack – Confidential Roller Stamp with 4 Refills – Wide Identity Theft Protection Stamp for ID Blockout, Privacy & Security(Black)
[Fully Protect Your Privacy] The identity theft protection roller stamp is the perfect choice to protect your private…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps in Developing Sensitive File Exclusion
Community discussions are ongoing, with developers proposing new design approaches and sharing code contributions. OpenAI has not announced an official timeline but is expected to revisit the issue in response to user demand and security considerations. Monitoring GitHub discussions and updates from OpenAI will be essential to track progress.
12Inch x 600Inch Honeycomb Paper Packing Sheets for Moving Sustainable Alternative to Bubble Cushioning Wrap for Shipping Box Protective Roll
Durability ：The design of small honeycomb is stronger then big honeycomb, which can enduring greater pressure.
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why is excluding sensitive files from Codex important?
Excluding sensitive files helps prevent unintentional data leaks, protecting confidential information and ensuring compliance with privacy standards.
What are the current workarounds for sensitive data in Codex?
Currently, users rely on manual practices, such as avoiding including sensitive files in repositories or using external filtering, but these are not foolproof or scalable.
Has OpenAI committed to developing this feature?
OpenAI has not made an official commitment, but community discussions and ongoing development efforts suggest it remains a priority for many users.
What is the role of codex-rs in this context?
codex-rs is a Rust implementation aimed at improving Codex’s functionality, but as of August 2025, it does not yet support the sensitive file exclusion feature.
When might a solution be available?
No official timeline exists; progress depends on community input, technical development, and OpenAI’s priorities.
Source: Hacker News
