Skip to main content
A Workflow saves instructions you want to reuse with /slug. It’s a playbook, not an AI employee. Say you’re always asking for the same inbox triage: archive newsletters, treat investors as VIPs, and keep drafts under three sentences. A Workflow captures that procedure once. Type /inbox-triage and Runner loads those instructions in that session.
Writes follow your tool permissions. Ask stages an Action Card for review. Allow acts without asking. Off blocks the tool unless a user-created Runner has its own override.
Coming from Runner Desktop? Workflows are what Skills became. Your synced Skills are already in your Workflow Library. Migration details →

Create a Workflow

Two ways, same as Runners: fill out the form, or have Runner build it with you.
1

Open the Workflow Library

Find Workflows in your sidebar. Click New workflow, or choose Create a workflow to have Runner interview you and write it.
2

Write the instructions

Name it (the name becomes the slug: “Listing Email” becomes /listing-email) and write the step-by-step guidance Runner should follow. Be as opinionated as you are in real life. That’s the point.
3

Invoke it anywhere

Type /listing-email in any session, on any device. Add context right in the message: “/listing-email for the house on Maple, emphasize the backyard.”
Just did something in a session you’ll want again? Say “turn this into a workflow.” Runner extracts the procedure from the conversation and saves it.

Workflows and Runners work together

A Runner owns the job. A Workflow says how, the schedule says when, and the Project supplies background. A Runner assigned the Friday review can invoke /weekly-review at 4pm, using those instructions and the background from its Project.

Workflow ideas


What’s next?

Starter workflows

Start with useful procedures, then make them yours.

Runners

Put a recurring job and the right Workflow on a schedule.