#security
7 articles
-
Control Codex web search with the web_search setting: disabled, cached, indexed, and live
The four values of Codex CLI's web_search setting and their defaults, the --search flag for one-off use, why indexed reduces prompt injection risk, and how to restrict domains.
-
Keep API keys out of the commands Codex runs: the shell_environment_policy setting
Control which environment variables reach the commands Codex CLI runs with shell_environment_policy: inherit values, default handling of KEY/SECRET/TOKEN names, filters, and set.
-
Manage Codex's "trust this folder?" prompt in config.toml with the projects trust_level setting
How Codex records project trust under [projects."<absolute path>"] trust_level, what it ignores for untrusted projects (.codex/config.toml, hooks, rules), and its precedence.
-
Claude Code permissions in settings.json: allow, deny and ask rules with real examples
Control what Claude Code may do without asking: allow / deny / ask rules in settings.json, the pattern syntax, scope precedence, and recommended setups for solo and team work.
-
Codex CLI approval modes versus sandbox modes: safe combinations for autonomous runs
What Codex CLI's approval policy and sandbox mode each control, what --full-auto really does, how to pin them in config.toml, and which pair fits research, daily work and CI.
-
Stop AI coding tools from reading your API keys and secrets: settings for Claude Code, Codex and Gemini CLI
Settings that keep .env files and credentials away from Claude Code, Codex and Gemini CLI, what to do after a leak, and how to keep secrets out of the repository altogether.
-
Is your code used to train Anthropic's models? Claude Code data usage by plan
Whether Claude Code uses your code for model training depends on your plan and settings. How personal and commercial plans differ, and what to check before using it at work.