From c1367808fb7f2b73575feb20041e1b2dd55a2fd2 Mon Sep 17 00:00:00 2001 From: zhao-oai Date: Wed, 10 Dec 2025 16:11:46 -0800 Subject: [PATCH] fixing typo in execpolicy docs (#7847) --- docs/execpolicy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/execpolicy.md b/docs/execpolicy.md index a2dc6d9add..e60e1cec6c 100644 --- a/docs/execpolicy.md +++ b/docs/execpolicy.md @@ -1,6 +1,6 @@ # Execpolicy quickstart -Codex can enforce your own rules-based execution policy before it runs shell commands. Policies live in `.execpolicy` files under `~/.codex/policy`. +Codex can enforce your own rules-based execution policy before it runs shell commands. Policies live in `.codexpolicy` files under `~/.codex/policy`. ## How to create and edit rules @@ -12,12 +12,12 @@ Codex CLI will present the option to whitelist commands when a command causes a Whitelisted commands will no longer require your permission to run in current and subsequent sessions. -Under the hood, when you approve and whitelist a command, codex will edit `~/.codex/policy/default.execpolicy`. +Under the hood, when you approve and whitelist a command, codex will edit `~/.codex/policy/default.codexpolicy`. -### Editing `.execpolicy` files +### Editing `.codexpolicy` files 1. Create a policy directory: `mkdir -p ~/.codex/policy`. -2. Add one or more `.execpolicy` files in that folder. Codex automatically loads every `.execpolicy` file in there on startup. +2. Add one or more `.codexpolicy` files in that folder. Codex automatically loads every `.codexpolicy` file in there on startup. 3. Write `prefix_rule` entries to describe the commands you want to allow, prompt, or block: ```starlark