Turn repeat work into workflows

Why it helps

• The same good result each time. A request you’ve refined over a few tries keeps every improvement, instead of being retyped from memory.
• A clean start. Each run starts a new conversation with a fresh agent session, so leftovers from other work don’t get in the way.
• Less typing on the go. The iPhone app can run your workflows too.

When to make one

Make a workflow when you’ve sent a similar request two or three times. Good candidates are jobs with a clear result: checking the site for broken links, writing release notes from recent changes, or testing every page at phone size. OpenAI’s Codex guide suggests the same for its own reusable instructions, called skills: keep each one “scoped to one job.”

How to do it

1. Ask the agent to save it. In a conversation where the task went well, send: “Save what we did here as a workflow called ‘Weekly site check’. Make it work for any week.” Enjoy opens the new workflow’s page in Workflows. Saving never runs it.
2. Or write it yourself. Open Workflows, select New workflow, and write the instructions. Enjoy saves it as you type. You can also start from the Gallery, which has ready-made workflows to add.
3. Run it. In Workflows, point at the workflow and select Run, or type its name in the search field and press Enter. Or select Run at the top right of its page. A new conversation starts with the workflow attached. While it’s running, Run on its page becomes View run.
4. Or add it to a message. Type @ and choose it under Workflows to combine it with details: “@Write release notes, and keep them under 200 words.” The agent receives the workflow’s full instructions along with your text.
5. Schedule it once it’s reliable. Open the workflow, select Repeat under its title, and choose Every day, Every weekday, Every week, or Advanced…. Codex’s guide warns against “scheduling a recurring task before it’s reliable manually,” so run it by hand a few times first. If you ask an agent to save a workflow with a schedule, the schedule starts right away.

Scheduled runs happen only while Enjoy is running on your computer, as a workflow’s page notes under its schedule: While Enjoy is open. If your computer is asleep or the previous run is still going, that run is skipped rather than made up later.

What to put in a workflow

A scheduled run may start while you’re away, so the instructions have to stand on their own. Claude Code’s guide advises being “explicit about what success looks like and what to do with results.” Include:

• The goal and the result: “Produce a short list of problems, most serious first.”
• The scope: “Check every page linked from the homepage.”
• How to check the work: “Open each page in the browser at phone width.”
• What to do when unsure: “If something needs a decision, list it instead of guessing.”

Common pitfalls

• Vague instructions. Nobody is there to clarify, so the agent guesses.
• One workflow doing three jobs. Split it. Workflows can link to each other: type @ in a workflow’s instructions to run another one next.
• Expecting edits to change a run in progress. Each run uses the instructions as they were when it started.
• Forgetting that runs use your plan. Every scheduled run counts against your AI subscription’s usage. See Make your agent usage last.