Workflows · Manwe docs

Turn a task you repeat into a saved workflow. Keep its instructions, inputs and world together, then run it on demand or on a schedule.

Create one

Open Workflows and press New workflow. A workflow belongs to a world, so create one first if you haven't. Then choose how to start:

Write it myselfFill in the editor yourself.

Browse examplesStart from a ready-made workflow for everyday life, learning, creative work, or work and community, and adjust it.

Build with an agentDescribe what you'd like to do repeatedly. Manwe asks what it needs to know and drafts the workflow for you to review.

The quickest way is often from a conversation. When an answer did something you'll want again, open its … menu and choose Save as workflow. Manwe opens a draft with your request as the instructions and the conversation's worlds and model already set.

What's in a workflow

InstructionsThe result you want, written the way you'd ask in a conversation.

Home WorldThe world whose context the workflow uses. Add more under Additional World context.

ModelThe workflow saves its exact model. Reasoning is captured when a run starts and reused for a valid restart. An unavailable model reports an error; changing another conversation's model does not select a substitute.

InputsAnything that changes between runs, like a date or a client's name. Mark an input Required, and give it a default for scheduled runs.

ScheduleOn demand, daily or weekly, at a time and time zone you choose.

Keep methods you use across many tasks in a skill instead; any workflow can use it.

Run and review

Run now starts the workflow. If it has inputs, you see them first and press Start run. While it runs, the button becomes Open run. Every run keeps the definition and inputs it started with. If an essential detail is missing, the run asks in its conversation and continues after your reply; the header's Activity shows it under Needs you.

The list shows each workflow's schedule and status, with a filter for what's running, waiting for input, scheduled or paused. Expand a workflow and press Open history to see past runs, their outputs and conversations, and exactly which definition and inputs each one used. Documents and other outputs are also kept in Settings › Vault › Saved work.

Repeat on a schedule

Scheduled runs prepare results without you there, so they only read: they look things up and save what they find. Anything that changes something outside Manwe, like sending a message or editing a page, needs a run you start yourself, with its normal approvals. Your private replies to a run's questions never become defaults for later runs.

By default, scheduled runs happen while your Mac is awake and Manwe is open, and a missed run catches up once. To keep them going after you quit, turn on Keep working after quit in Settings › General › Background work. A workflow that uses a model on your Mac still waits until Manwe is open, because the background helper doesn't load local models.

If a scheduled run can't start, Manwe tells you in a conversation and a notification. An unattended read-only run cut off by a restart can restart from its saved boundary when its definition, model, reasoning, Worlds and project context still match. Runs with saved responses, unanswered questions, approvals or uncertain effects need review; earlier actions and approvals are not replayed.

Pause schedule, in the workflow's … menu, stops future scheduled runs. Stop run stops the current one. They're separate on purpose.

Keep access explicit. A workflow uses its selected worlds and the task's permissions. Saving a workflow doesn't approve future changes, or turn its output into world memory.