Workflows

Two kinds, one idea

A workflow is a job written as steps, where each step says what it needs from the steps before it. That one rule decides the order: a step waits only for what it truly needs, and steps that need nothing from each other run at the same time.

• Creation workflows chain media steps on a canvas: make a picture, upscale it, animate it, add a voiceover and music, assemble and export.
• Work workflows run in a chat thread: find and fix a bug, research a question with sources, build something and prove it works. Their progress shows as a card in the thread.

The Creation builder

Open Creation and choose Workflows. The steps are Make, Edit, Upscale, Animate, Smooth motion, Voiceover, Music, Assemble and Export. Press a step's right dot, then another step's left dot, to connect them; press an arrow to remove it. A workflow saves as you edit it.

Run runs the steps in order and Stop halts before the next one. When a step fails, everything after it is skipped, so nothing is paid for on a missing input. Run again reuses every result that has not changed, so changing the music does not remake the pictures.

Each paid step shows its price like any Creation job, and counts toward the month's pictures and clips. Smooth motion and Assemble run on your computer.

Workflows in the box

Mori ships with work workflows for the jobs people ask for most:

• Find and fix a bug, and debug something that is failing.
• Understand an unfamiliar codebase, and study a repo, then build on it.
• Write tests for existing code.
• Build it, then prove it works.
• Review it properly, and review and ship what you changed.
• Find and remove dead code.
• Check this machine is set up properly.
• Research the question, and answer a question properly, with sources.
• See how something compares to its competitors.
• Build a presentation, and write up what happened this week.
• Draft a message to someone, which you approve before anything is sent.

Starting one

Type /workflow and the job, or just ask: when your request matches a workflow's job, Mori runs it as one. Matching is careful on purpose. A loose match once turned "write me a poem" into a test writing run, so names match closely, and a workflow you saved yourself always wins over a built in one with a similar name.

The card in the thread lists the steps. One step is active at a time, and where work genuinely runs in parallel (three research angles, several files) the parallel items show underneath it. The card stays in the thread when the turn ends, as a receipt of what was done.

Verify steps

Building workflows end on checks: the build runs, the tests run, the result is looked at. A verify step is marked optional, so a build that could not be tested is reported as built but untested rather than thrown away. Mori never turns an untested step into a pass.

For a repo Mori did not write, the build and test commands are worked out from the files in it (a Python, Rust, Go, C++ or Lua project is not tested with npm), and the same rules decide the commands everywhere in the app.

Your own workflows

Fork a built in workflow, change its steps, and keep it. Your copy is used everywhere the built in one was. A save that would make a workflow that cannot run (a step that needs a step that does not exist, or a tool nobody wrote) is refused with the reason, so your workflows are held to the same rules as the shipped ones.

Mori can also write a workflow as a short script for a big job. Scripts can start several agents, so a saved script asks for your approval before it runs while asking is on, and every agent it starts is metered like any other turn.

From a workflow to a skill

When a large workflow finishes well, Mori can distill it into a skill: the procedure that worked, not a trace of every dead end. The bar is deliberately high, so routine runs do not fill your skills with near copies, and running the same workflow again updates its skill instead of adding another. Only a run that finished as done can be learned from; failed, partial and stopped runs never become skills. The skill then comes in on future jobs of the same shape. See Skills.

What a workflow costs

A work workflow is model turns and tools, metered like any other turn on your key or your plan's credits, with helper agents counted the same way (see Agents and helpers). The steps that fan out spend in parallel, which is why fan out only appears where the work is truly parallel. /budget shows what a job and its thread may spend and where they stand.