# Cancel > 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. - Skill: `thedixitjain/cancel` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds add thedixitjain/cancel` - Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/cancel/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: thedixitjain (https://skillmd.com/u/thedixitjain) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/thedixitjain/cancel --- # Cancel Process Job Resolve `` as two directories above this `SKILL.md` and run: ```text node "/scripts/job.mjs" cancel [--force] --json ``` If `${CODEX_HOME:-$HOME/.codex}/process-jobs` is not writable in the current sandbox, request narrow controller escalation on the first call; do not probe for a predictable `EPERM`. Never cancel because a Codex task, client, or terminal is closing. Require a specific job id; use `$status ` first only if identity/state is unclear. A direct request authorizes normal cancellation of a non-critical job. For a `CRITICAL` job, explain that interruption can worsen partial state and obtain explicit approval immediately before `--force`. This bypasses only the critical guard: the controller still validates PID identity, sends SIGTERM to the process group, waits up to five seconds, and uses SIGKILL only if needed. Never bypass an identity refusal with untracked `kill` without separate authorization after inspection. Filesystem/device repair can leave metadata partially rewritten. Prefer waiting unless continued execution presents a greater concrete risk. --- **Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/joelfarthing/codex-process-jobs/skills/cancel/SKILL.md`