cd /news/ai-safety/a-way-to-exclude-sensitive-files-iss… · home topics ai-safety article
[ARTICLE · art-42511] src=github.com ↗ pub= topic=ai-safety verified=true sentiment=· neutral

A way to exclude sensitive files issue still open for OpenAI Codex

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.

read1 min views1 publishedJun 28, 2026
A way to exclude sensitive files issue still open for OpenAI Codex
Image: source
[Notifications](/login?return_to=%2Fopenai%2Fcodex)You must be signed in to change notification settings -
[Fork 14k](/login?return_to=%2Fopenai%2Fcodex)

Copy link

Copy link

Open

Labels

enhancementNew feature or requestNew feature or request

sandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing

Description #

What feature would you like to see?

  • 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).
  • Example: keep node_modules/ searchable for implementation checks, but never read or send .env, .env.*, .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.

Are you interested in implementing this feature?

  • Yes — I can contribute and tests.

Additional information

Related: #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. Reactions are currently unavailable

Metadata #

Metadata #

Assignees

Labels

enhancementNew feature or requestNew feature or request

sandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing

Type

Fields

Give feedback No fields configured for issues without a type.

── more in #ai-safety 4 stories · sorted by recency
── more on @openai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/a-way-to-exclude-sen…] indexed:0 read:1min 2026-06-28 ·