Story
A way to exclude sensitive files issue still open for OpenAI Codex
1 report
1 website
1 discussion
Latest report
Overview
A mechanism is proposed to mark sensitive files or paths that should not be read or sent to the model, applicable at both repository and global levels. This feature aims to enhance privacy and security in AI interactions with code.
Summary from github.com.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · github.com
Hacker News discussion ↗
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 5 sampled comments from this thread. Analyzed 2026-06-28.
- Praise: Running Codex in a container or using Unix permissions effectively prevents sensitive file access, emphasizing the importance of security measures in AI applications.
- Praise: The client-server architecture of Codex allows for effective remote agent harnessing, enhancing its usability in secure environments.
- Praise: Creating a dedicated workspace VM for Codex can isolate sensitive data, ensuring that coding agents operate within defined security boundaries.
- Concern: Implementing a blocklist for sensitive files in Codex is unlikely to be effective, as it may provide a false sense of security against the unpredictable nature of AI.
- Concern: The suggestion that Codex should enforce file access restrictions places security responsibilities incorrectly, as users should manage permissions themselves.
- Concern: Users express concerns that Codex's unpredictable behavior could lead to unintended access to sensitive files, highlighting the need for robust sandboxing solutions.