/Jobs
Core Concepts

Jobs

How jobs work — the scheduled tasks that Claude Code executes.

What Is a Job?

A job is a scheduled, executable task. When a job fires, OpenHelm runs Claude Code with the job's prompt in the project directory. Jobs are the atomic unit of work in OpenHelm.

Each job has:

  • Name — human-readable label
  • Prompt — instructions sent to Claude Code when the job runs
  • Schedule — when and how often to run (see Schedule Types)
  • Model settings — which Claude model to use and effort level
  • Permission mode — how much autonomy Claude Code has during execution

Creating Jobs

Jobs can be created two ways:

  1. Via the AI planner — describe a goal; the AI generates a job plan for you to review and approve
  2. Manually — click New Job and fill in the prompt, schedule, and settings yourself

Job Settings

Model

The Claude model used for this job's execution. Defaults to Claude Sonnet 4.6.

Effort (low | medium | high)

Controls how much planning effort Claude Code uses before starting work. Higher effort means more thorough planning but more tokens consumed.

Permission Mode

Controls what Claude Code can do without prompting for confirmation:

  • default — standard Claude Code permissions
  • acceptEdits — auto-accepts file edits without prompting
  • dontAsk — does not prompt for confirmation on most actions
  • bypassPermissions — maximum automation; use with care

Working Directory Override

By default, jobs run in the project's root directory. Override this to run in a specific subdirectory or a different path entirely.

Correction Note

Optional text appended to the prompt of any corrective retry run. Use this to guide Claude Code when recovering from failures — for example, specifying which commands to run first or which files to check.

Enabling and Disabling Jobs

Toggle the switch on any job to pause or resume automatic scheduling. Disabled jobs can still be triggered manually.