Workflows
Save a routine you want repeated - steps in plain words plus the tool calls that did them - and have an agent follow it on the next project.
A workflow is a recipe the user wants repeated on other projects: "my podcast clean-up", "the weekly reel", "client delivery". It is a name, what it is for, and its steps in order. Each step says in plain words what to do, and may carry the tool call that did it last time. Workflows are shared by every project, one JSON file each in library/workflows/<id>.json:
{ "id": "podcast-clean-up", "name": "Podcast clean-up",
"description": "Voice level, no dead air, captions, a Shorts cut.", "tags": ["podcast"],
"steps": [
{ "text": "Reduce the room noise on the voice clips.",
"call": { "tool": "fablecut_denoise", "args": { "clipIds": ["c_vo"], "amount": "medium" } } },
{ "text": "Normalize the voice to -16 LUFS.",
"call": { "tool": "fablecut_normalize_audio", "args": { "clipIds": ["c_vo"], "target": -16 } } },
{ "text": "Cut the pauses longer than half a second, keeping the music bed running." },
{ "text": "Export for YouTube Shorts.", "call": { "tool": "fablecut_export", "args": { "preset": "youtube-shorts" } } } ],
"created": "…", "updated": "…" }| key | does |
|---|---|
name · id | up to 80 characters; the id is made from the name, and saving the same name again updates that workflow (it keeps its created) |
description · tags | what it is for (up to 600 characters) · up to 12 labels |
steps | 1–50, each {text, call?} (a plain string is a step with only text); text up to 1000 characters |
call | {tool, args}: a FableCut tool (not fablecut_workflows) and the arguments it was given, up to 20 000 characters |
Following one is a job for judgement, not a replay. The new project has other clips, ids and times, so a step's call is a worked example: read what the step says, look at the project (fablecut_get_project {compact:true}, fablecut_frame), and make the call that does that here. A step with no call is one only the agent's judgement can do ("pick the three strongest shots").
Agents use fablecut_workflows (or the REST endpoints below):
{}lists them (id, name, steps, tags, description);{action:"show", id}gives the steps to follow (id or name).{action:"save", workflow:{name, description?, tags?, steps}}keeps one. Save when the user asks to keep or repeat what was just done: write each step the way you would explain it to another editor, and attach the calls that worked. A call to a tool that doesn't exist refuses the save.{action:"delete", id}removes one: only when the user asks.
Recipes: "do what you did last week" - {}, then show the one that matches and do its steps; a house style for every episode - after the first episode is right, save its loudness, captions, grade and export steps as one workflow; hand a routine to another agent - the file in library/workflows/ is plain JSON any agent can read.