Verified, then logged.
Sun 22 Nov 2026 · 00:20 KST / 15:20 UTC한국어 | ENSearch /

02 / IT · Analysis

Codex command rules give blocking priority over permission

A DEV.to post explained which command rules take priority when they overlap and how to test them before use.

A headset and desk speakerphone are wired to an audio analyzer on a bench in a foam-lined acoustic booth, with empty call-center desks and an out-of-focus technician seen from behind through the open door. AI-generated image

A DEV.to post published on 14 Nov described how Codex command rules let developers allow execution, require prior approval or block commands according to their prefixes.

According to the post, the most restrictive decision takes priority when several rules match a command. An allow rule therefore cannot override a blocking rule that also applies.

The post paired that priority order with a recommendation to test rules before relying on them. For developers, the two steps connect the intended execution decision with a way to check the rule before use.

Blocking takes priority over permission

The DEV.to post described Codex rules as instructions written in .rules files. A command prefix means the opening part of a command.

The post gave the priority order as forbidden, then prompt, then allow. These decisions mean blocking execution, requiring prior approval and allowing execution, respectively.

Testing rules before use

The DEV.to post recommended using codex execpolicy check to test rules. Its guidance placed this check before developers begin relying on the rules to control command execution.

The post also recommended adding match and not_match examples: commands that should match the rule and commands that should not. Codex validates those examples when loading the rules, providing a check that the written rule matches its intended scope.