codex-pair-ack git:20260609.145a061A

Immutable. This exact content is served forever at /api/v1/blob/64d1633010bd2402.

---
name: codex-pair-ack
description: Use when the user wants to defer a codex-pair HIGH finding so the Stop-gate stops blocking turn-end. Records an acknowledgement in .codex-pair/state/acks.json keyed by the 16-char hash printed in the gate's block message. Usage /codex-pair-ack <hash> "<reason>".
user_invocable: true
---

# Acknowledge a codex-pair HIGH finding

Records an ack for the given finding hash so the codex-pair Stop-gate skips it on future turn-ends. The gate prints a full 16-char hash in its block message, e.g. `[fc69d46835dfd2ab] src/auth.ts` — pass that hash verbatim.

## Instructions

1. **Parse args.** The first whitespace-delimited token is `<hash>` (16-char hex). The remaining text (strip enclosing quotes if present) is `<reason>`. If either is missing, print usage and stop:
   ```
   Usage: /codex-pair-ack <hash> "<reason>"
   Example: /codex-pair-ack fc69d46835dfd2ab "false positive — test-only code path"
   ```

2. **Locate the `.codex-pair/` directory.** Walk up from the current working directory looking for `.codex-pair/context.md`. The directory that contains `.codex-pair/` is `<markerDir>`. If no marker is found after reaching the filesystem root, tell the user:
   ```
   codex-pair is not enabled in this project (no .codex-pair/context.md found). Nothing to acknowledge.
   ```

3. **Record the ack** by running the following Bash one-liner (substitute real values for `<markerDir>`, `<hash>`, and `<reason>`):
   ```bash
   node --input-type=module -e '
   import { addAck } from "${CLAUDE_PLUGIN_ROOT}/scripts/lib/state.mjs";
   addAck(process.argv[1], process.argv[2], { reason: process.argv[3] });
   ' "<markerDir>" "<hash>" "<reason>"
   ```
   `addAck` writes to `<markerDir>/.codex-pair/state/acks.json` (creating the directory if needed). The hash is passed verbatim — no resolution is performed.

4. **Confirm** to the user:
   ```
   Acknowledged `<hash>` — <reason>. The Stop-gate will skip this finding.
   ```
   If the node one-liner exits non-zero, surface the error output so the user can diagnose it.