-
Notifications
You must be signed in to change notification settings - Fork 40
Workflows
Workflows let you chain multiple tool calls together into automated pipelines. Think of them as recipes — a series of steps that run in order, passing data from one step to the next.
Just describe what you want automated:
Example: Morning briefing Say: "Create a workflow called 'morning-briefing' that searches for today's top news, summarizes it, and reads it aloud with TTS"
Example: GPU health check Say: "Create a workflow that checks GPU status, lists loaded models, and reports the results"
Example: Model loader Say: "Create a workflow called 'load-qwen' that checks GPU memory, loads Qwen 7B on GPU 1 with 8192 context, and runs a test prompt"
Data flow between steps: Each step can use the output of previous steps. For example, step 2 can use the search results from step 1.
Conditional steps: Steps can be skipped based on conditions. For example: "Only load the model if GPU has more than 6GB free."
Loops: Steps can repeat over a list. For example: "For each loaded model, get its info and print a summary."
Error handling: Steps can be configured to continue, skip, or stop on error.
Parallel execution: Independent steps can run simultaneously for faster completion.
Scheduling: Workflows can be scheduled to run automatically on a timer (daily, hourly, etc.).
| Command | What It Does |
|---|---|
| "List my workflows" | Shows all saved workflows |
| "Show the [name] workflow" | Displays the workflow steps |
| "Run the [name] workflow" | Executes the workflow |
| "Schedule [name] to run at 8am daily" | Sets up automatic execution |
| "Delete the [name] workflow" | Removes the workflow |
Workflows are saved as JSON files in the workflows/ directory.