Exporting and importing a task

A task can leave your Mac as a file and come back as a task, on the same machine or another one. Export a task to move it to another machine, to share it, or to keep a copy. This page says what the exported file holds, what it leaves out, and what you see when you import it.

Exporting a task

In the Tasks screen, each task's row has an Export button. HarmFlow asks where to save the file, with a name taken from the task's identifier, such as weekly-report.yaml, and shows Task exported. once it is saved.

What the file holds

The exported file is the task's own file, as you or HarmFlow wrote it: its comments and the order of its keys are kept. It holds what the task is — its type, its work, its schedule, its AI tools, and its permissions — and nothing else.

What the file leaves out

The file carries no record of any run, even for a task that has already run many times. Nothing a run left behind is in it:

Your own agents and skills stay on your machine, too: the file names the ones the task cites, but does not carry them.

Secrets

If a password or a token was typed into a task's prompt, its description, or a comment of its file, the export masks it: the secret does not reach the exported file.

That is a safety net, not a place to keep secrets: do not type secrets into a task, and read an exported file before you share it.

Importing a task

In the Tasks screen, choose Import. In the Import a task window, choose a .yaml file with Choose file… or paste its content, then choose Import.

After an import

HarmFlow shows Task imported., the task appears in the task list, and it opens in the task editor. From there it is a task like any other: edit it, save it, and run it.