Your first workflow
This guide creates a local command workflow. It does not contact an external service or require an AI account.
Create a job
Section titled “Create a job”- Open Runstead and choose the project in the sidebar.
- Choose Create a job and name it Morning check-in.
- Pick Command or script for its first task.
- Enter this command:
printf 'Runstead is ready.\n'The graph shows how tasks connect. Select a task to edit its fields in the right-hand inspector. Add more tasks with the graph’s + control.
Review and run
Section titled “Review and run”Choose Review & run, then Save and run…. Review the inputs and select Start run. Open Runs & logs to inspect the result and task output.
Saving and running are separate actions. Save checks and stores a workflow without starting it. Tools → Check workflow checks a draft against the installed engine.
Add a schedule
Section titled “Add a schedule”Return to the workflow, open Schedule, choose a daily time and timezone, and save. Confirm Enable saved schedules is enabled. Keep the computer awake and Runstead running for the scheduled time.
See Scheduling before relying on unattended runs.
Bring your own work
Section titled “Bring your own work”Replace the sample command with a script you already use. Use absolute paths for executables and working folders when needed: the app’s environment can differ from an interactive Terminal session. Add input fields for values that change between runs, and keep credentials in Secrets.
See Build a workflow to connect Docker images, AI agents, human decisions, and commands on server groups.