codex-process-jobs

Safely request termination of a tracked detached process group using PID identity validation and a SIGTERM-to-SIGKILL grace period. Use only when the user asks to stop a job; critical repair, migration, firmware, or destructive jobs require explicit risk-aware approval and --force.

Launch a finished Codex Process Jobs record again as a new detached job using its validated persisted argv, working directory, and execution mode. Use only when the user explicitly asks or approves rerunning a specific completed, failed, or cancelled build, test, benchmark, inference run, data job, or repair.

Retrieve bounded output for finished jobs and automatic CPJ completion hooks.

Launch an ordinary finite local workload as a durable detached process job, then release the assigning Codex turn instead of monitoring it. Use proactively for downloads, builds, test suites, evaluations, benchmarks, inference/model A/B runs, data jobs, and repairs whose underlying work may exceed 60 seconds or has uncertain duration. The user-visible parent must launch the job directly; never delegate local process execution or monitoring to a subagent.

Inspect active and recent detached process jobs in a later user-requested turn, retrieve a lightweight activity preview, or wait once when explicitly requested. Use for questions such as "how's the build going?", later user-requested checks of test, inference, data-processing, or repair progress, or diagnosis of a disappeared worker. Never use it to monitor a job from the same turn that launched it or merely because an automatic Goal continuation arrived.

Read the latest bounded stdout or stderr from a tracked detached process job. Use to inspect live build progress, benchmark output, test failures, repair diagnostics, or other command output without loading the entire persisted log.