A script task's working directory, variables, and timeout

A script task runs a program you name, on a schedule or by hand, with no AI tool involved. This page says where that program starts, which environment variables it sees, and when HarmFlow stops it. In the task editor, they are the task's Working directory, Environment variables, and Timeout (minutes), shared by all attempts fields.

Where the program starts

A script task can set the working directory its program starts in.

• A working directory set. The program starts in that folder. ~ in it stands for your home folder.
• None set. The program starts in your home folder.

The variables the program sees

A script task can set environment variables, one NAME=value per line. The program sees your own environment, as HarmFlow runs with it, plus the task's variables:

• A name only the task sets. The program sees it with the task's value.
• A name your environment already has. The task's variable replaces it. The program sees the name once, with the task's value.
• A name the task does not set. It reaches the program unchanged.

When the program is stopped

A script task can set a timeout, in minutes.

• A timeout set. HarmFlow stops the program once it has run that long.
• None set. HarmFlow stops the program after 60 minutes.