What a script task does not take

A script task runs a program you name, on a schedule or by hand, with no AI tool involved. So the settings that tell HarmFlow's other tasks how to work with an AI tool do not apply to it. This page lists them, says what HarmFlow does when a task file sets one for a script task, and why running a script task never uses an AI tool's quota.

The settings a script task leaves out

A script task has none of these:

• A prompt. The program is the task's work; there is nothing to ask an AI tool.
• An AI tool. No Claude Code or Codex runs for it.
• A model and an effort. With no AI tool, there is no model to pick.
• A fallback chain. There is no AI tool to fall back from.
• Agents and skills. They are instructions for an AI tool, and none runs.

A task file that sets one of them

HarmFlow checks a task file when you check it and when you save it.

• A script task that sets one of these settings. The file is rejected, and the rejection names the field that is not allowed. The model, the effort, and the fallback chain are part of a task's AI tool settings, so a script task that sets one of them is rejected at its AI tool settings.
• A script task that sets none of them. The file is accepted.

Usage limits

Running a script task never reads an AI tool's usage limit. It never shows a usage warning, and it never waits for a usage limit to reset, even when an AI tool's quota has run out.