{"slug": "a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex", "title": "A way to exclude sensitive files issue still open for OpenAI Codex", "summary": "A GitHub issue requesting a feature to exclude sensitive files from OpenAI Codex remains open as of August 2025. The feature would allow users to specify files and paths that the AI agent must not read or send to the model, addressing security and performance concerns. The issue was previously closed in favor of a Rust implementation, but the comparable feature has not yet been implemented.", "body_md": "-\n[Notifications](/login?return_to=%2Fopenai%2Fcodex)You must be signed in to change notification settings -\n[Fork 14k](/login?return_to=%2Fopenai%2Fcodex)\n\n# A way to exclude sensitive files #2847\n\nCopy link\n\nCopy link\n\nOpen\n\nLabels\n\n[enhancementNew feature or request](https://github.com/openai/codex/issues?q=state%3Aopen%20label%3A%22enhancement%22)New feature or request\n\n[sandboxIssues related to permissions or sandboxing](https://github.com/openai/codex/issues?q=state%3Aopen%20label%3A%22sandbox%22)Issues related to permissions or sandboxing\n\n## Description\n\n### What feature would you like to see?\n\n- A mechanism to explicitly mark files/paths that the agent must not read or send to the model, at both repository and global levels (e.g., a repo-local .codexignore plus a global ignore file).\n- Example: keep node_modules/ searchable for implementation checks, but never read or send .env, .env.*,\n*.pem, id_*, .aws/**, .ssh/**. - The configuration should be deterministic and shareable across the team/repo, and also support user defaults, rather than relying on project documentation or conventions.\n\n### Are you interested in implementing this feature?\n\n- Yes — I can contribute and tests.\n\n### Additional information\n\nRelated: [#205](https://github.com/openai/codex/issues/205). That issue surfaced two primary use cases: preventing sensitive data from being sent to the model and excluding large/irrelevant files. The issue was closed in favor of a Rust (codex-rs) implementation, but as of 2025-08-28 a comparable feature does not appear to exist in codex-rs. I’d like to restart the discussion and converge on a design.\n\nReactions are currently unavailable\n\n## Metadata\n\n## Metadata\n\n### Assignees\n\n### Labels\n\n[enhancementNew feature or request](https://github.com/openai/codex/issues?q=state%3Aopen%20label%3A%22enhancement%22)New feature or request\n\n[sandboxIssues related to permissions or sandboxing](https://github.com/openai/codex/issues?q=state%3Aopen%20label%3A%22sandbox%22)Issues related to permissions or sandboxing\n\n### Type\n\n### Fields\n\n[Give feedback](https://github.com/orgs/community/discussions/189141)\n\nNo fields configured for issues without a type.", "url": "https://wpnews.pro/news/a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex", "canonical_source": "https://github.com/openai/codex/issues/2847", "published_at": "2026-06-28 12:27:33+00:00", "updated_at": "2026-06-28 12:34:57.120420+00:00", "lang": "en", "topics": ["ai-safety", "ai-tools", "ai-products"], "entities": ["OpenAI", "Codex", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex", "markdown": "https://wpnews.pro/news/a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex.md", "text": "https://wpnews.pro/news/a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex.txt", "jsonld": "https://wpnews.pro/news/a-way-to-exclude-sensitive-files-issue-still-open-for-openai-codex.jsonld"}}