How this command is triggered — by the user, by Claude, or both
Slash command
/mission:cancel <mission-id>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Cancel the mission and reconcile unfinished tasks (`pending`/`running`/`blocked`) to `canceled`.
Cancel the mission and reconcile unfinished tasks (pending/running/blocked) to canceled.
bun "${CLAUDE_PLUGIN_ROOT}/dist/mission-companion.js" cancel --stdin <<'__MISSION_CANCEL__'
$ARGUMENTS
__MISSION_CANCEL__
npx claudepluginhub loner1024/claude-mission-plugin --plugin mission/cancelCancels an active background Codex job in this repository using the provided job ID.
/cancelCancels stuck or orphaned executions in the session. Invoke also via /kill or /abort aliases.
/cancelCancels execution loop for spec by name/path or current, cleans up state files, removes spec directory, clears markers, and updates index.
/cancelCancels active execution loop for a specified or current feature, shows phase/progress/iterations before cleanup, deletes state file, keeps progress history.
/cancelCancels the active claudex loop in the project by marking state phase as cancelled, removing runner script and lockfile, and printing confirmation. Enables clean exit via Stop hook.