{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidu5mnsfpnrhy7emqogxgy7ebbuqwxqwur5kkwclwzpvr57uuj33i",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mldltithpzl2"
  },
  "path": "/t/feature-request-sentinel-mode-for-codex-chatgpt-enterprise-governed-ai-agent-operations-with-dry-runs-approvals-and-audit-logs/1380493#post_3",
  "publishedAt": "2026-05-08T10:49:38.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "topic",
    "due diligence",
    "Codex hooks",
    "Claude Code Docs",
    "Explore the .claude directory - Claude Code Docs",
    "daemon"
  ],
  "textContent": "I was reading this and then realized, I know this person from the other topic.\n\nMost, if not all, of what you are seeking could probably already be done. While I have not performed a full due diligence review, Codex hooks, combined with the fact that much of what Codex does is stored locally in `.codex` folders, would likely go a long way toward implementing this.\n\nI could not find an official OpenAI page documenting the `.codex` folder, but the related directory structure for Anthropic Claude Code is described here:\n\nClaude Code Docs\n\n### Explore the .claude directory - Claude Code Docs\n\nWhere Claude Code reads CLAUDE.md, settings.json, hooks, skills, commands, subagents, rules, and auto memory. Explore the .claude directory in your project and ~/.claude in your home directory.\n\nMany advanced users I know create a daemon to monitor and capture updates to these folders, since much of the data is eventually deleted to save space. For your sentinel idea, however, retaining that information could be invaluable.",
  "title": "Feature Request: Sentinel Mode for Codex / ChatGPT Enterprise — Governed AI Agent Operations with Dry-Runs, Approvals, and Audit Logs"
}