← ClaudeAtlas

codex-deferred-completionlisted

Complete long-running executable work through an existing atomic JSON terminal receipt, avoiding repeated native-session or remote-status polling and wasted model turns.
Xopoko/plug-n-skills · ★ 11 · AI & Automation · score 77
Install: claude install-skill Xopoko/plug-n-skills
# Codex Deferred Completion Use this skill only for a non-interactive command with a producer-owned terminal receipt. The MCP server coordinates receipt creation and validation; it never launches, wraps, signals, or kills the command. Native Codex exec therefore remains the command's sandbox and approval boundary. This MCP requires POSIX safe-open support and is intended for current macOS and Linux hosts. On another host, use one bounded native wait or yield. ## Preconditions Inspect the producer's local `--help` and source-backed receipt contract first. Proceed only when all of these are true: - the command accepts an absolute result path through a native flag; - it atomically replaces a mode-`0600` JSON file at that path; - the receipt has the fixed envelope fields `schema`, `outcome`, `exitCode`, `startedAt`, `completedAt`, `elapsedSeconds`, and `transitionCount`; - a known JSON Pointer inside the receipt equals the reserved result path; - stable job identity can be checked with bounded JSON Pointer assertions; - the command is non-interactive and its live output is not needed for a decision. Do not invent a receipt adapter, shell wrapper, or nested subprocess merely to use this skill. If the producer lacks a native receipt, leave the command direct and use one long native wait. ## Reserve The Contract Call `reserve_completion_receipt` immediately before launch. Supply: - a compact `label` carrying the stable operation identity; - the exact producer `schema`;