AGENTS.md@plugins/autorun/src/autorun/codex_template · git:20260805.5d067a6 · 2026-08-05 · sha256 579b949490f54366
AGENTS.md@plugins/autorun/src/autorun/codex_template git:20260805.5d067a6A
Immutable. This exact content is served forever at /api/v1/blob/579b949490f54366.
<!-- autorun:codex-agents-md:start --> # autorun safety guidance (Codex) Codex CLI runs autorun's hooks from `~/.codex/hooks.json`, so the enforcement path (blocked commands, autofile policy, stop blocker) is real and binding. This file is informational — it tells the model what overrides exist so a stop or a block can always be resolved. ## Override commands (user types these) Codex-native forms avoid unknown slash-command interception in the TUI: - `ar:sos` — emergency stop, cancels the current autorun. - `ar:task ignore <id>` — mark a tracked task as ignored so a Stop block can clear. - `ar:ok <pattern> [N|5m|perm]` — allow a blocked command in this session; default is one use then auto-revoke. - `ar:globalok <pattern> [N|5m|perm]` — same allow, persisted globally. Slash forms such as `/ar:sos`, `/ar:task ignore`, and `/ar:ok` remain supported by autorun when a harness passes them to hooks, but current Codex CLI may handle unknown slash commands before `UserPromptSubmit` hooks see them. In Codex, prefer `ar:*` or `ar <command>` forms. ## Autorun skills Codex exposes skills through `/skills`, `$skill-name` mentions, and installed plugin selection such as `@autorun`. Autorun installs skills like `$mermaid-diagrams` and `$tmux-automation`, but Codex does not expose them as slash commands like `/mermaid`. The `$ar` skill carries the full `ar:<command>` control grammar (policy, guards, task tracking, cache gate, plan export); `ar:help` prints the live command list. ## Safety guardrails 1. Prefer `trash` over `rm` for any path you did not just create. 2. Never run `git reset --hard`, `git push --force`, or `git clean -f` without an explicit user instruction in the current turn. 3. Never modify uncommitted work that you did not produce in this run. 4. When in doubt about a destructive command, propose it as a question instead of executing it. ## Stop semantics If you have incomplete tracked tasks and the user asks you to stop, surface the override path: only the user can type `ar:sos` or `ar:task ignore <id>` to unblock the Stop. <!-- autorun:codex-agents-md:end -->