Run Jobs¶
Goal¶
Create durable work that can be inspected, updated, completed, canceled, or repeated on a schedule.
Before you start¶
Use jobs when the work needs status and result tracking. Use schedules when you only need a future message, and use ask when you only need a peer to answer one question.
Steps¶
Create a job:
repowire jobs create "Daily brief" --path .repowire/agents/daily-brief --backend codex --cron "@daily" --prompt "Prepare the brief."
Unassigned path/backend jobs run with per-fire executors by default: Repowire
spawns or backend-resumes an executor for the run, delivers the job ask, and
releases the executor after a terminal job update. Later runs can resume with
the backend-native runtime session id when available. Use --continuity fresh
when a run should start without resume context.
List and inspect jobs:
Update status or record a result from CLI/MCP surfaces:
repowire jobs update job-... --state running --note "Started first pass"
repowire jobs update job-... --state succeeded --result-summary "Brief posted"
repowire jobs result job-...
Cancel work that should not continue:
Worker folders¶
repowire agents create <name> scaffolds a repo-local .repowire/agents/<name> folder for durable worker prompts and instructions. Target that folder from recurring jobs when the job should run as a reusable worker rather than an ad hoc prompt.