Rerun Process Job
SkillAI & modelsLaunch 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.
Use Rerun Process Job in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Rerun Process Job and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Rerun Process Job skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/joelfarthing/codex-process-jobs/skills/rerun/SKILL.md and read by Ahel’s review.
Resolve <plugin-root> two directories above this file and run:
node "<plugin-root>/scripts/job.mjs" rerun <job-id> [options] --json
Never search memory for CPJ work; use validated CPJ state.
The user-visible parent owns every CPJ rerun and completion. Never delegate local process execution, launch, waiting, monitoring, or CPJ ownership to a spawned subagent. A subagent can analyze independent material only.
Require a specific source job. If identity is unclear, use $status once to
find it. Never reconstruct argv from displayed command text, logs, or model
memory. The controller reads the private validated record, refuses active jobs,
and creates a fresh job ID and logs with rerunOf lineage.
A rerun repeats the invocation, not the historical environment: files, dependencies, environment variables, credentials, devices, and external state may have changed. Mention a material change before launch; do not claim exact reproducibility.
Never rerun automatically from a completion notice. A direct user request
authorizes an ordinary non-critical rerun. For a CRITICAL job, explain that
the command may repeat repair, migration, firmware, or destructive effects and
obtain explicit risk-aware approval immediately before adding --force.
Add --goal-mode only for an explicitly active Goal. Optional flags are
--no-notify, --notify-user, and --no-notify-user. If the durable state
directory is not writable in the current sandbox, request the same narrow
controller escalation described by $start.
Treat a successful rerun as the same hard release boundary as $start: report
the new job ID and its source job ID in no more than two short sentences. Say
that a completion notification should appear when it finishes, then end the
turn without status, tail, result, wait, sleep, or process monitoring. Do not
narrate controller mechanics, persisted metadata, argv, cwd, or validation
unless the user explicitly asks.
If the controller refuses because the source remains active, its working
directory disappeared, or legacy shell semantics cannot be preserved, report
that refusal and do not improvise a replacement command.
Signals
- GitHub stars
- 1k
- Forks
- 316
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
rerun- Source
- github.com/hashgraph-online/awesome-codex-plugins
github.com/hashgraph-online/awesome-codex-plugins
More in AI & models
Skill · anthropics
More in AI & modelstriage
Skill · mattpocock
More in AI & modelswayfinder
Skill · mattpocock
More in AI & modelsalgorithmic-art
Skill · anthropics
More in AI & modelscode-review-and-quality
Skill · addyosmani
More in AI & modelsmarketing-psychology
Skill · coreyhaines31
More in AI & models