Long tasks and helpers

When a task is long

Ask for a long task by name, or for something that spans days or weeks, and Mori plans it as one. At Balanced and above, a build that is clearly hours of work does the same: a real console emulator, a compiler, an operating system, a game engine, a browser, a database. The work is split into milestones, and each milestone is a standing goal.

The card

A long task opens on a card that says how it will work and what to expect: a time range with its basis, the cost estimate (with a warning when it may go past what the budget has left), how much of the budget is spent, when it reports, its pace, quiet hours, and where it runs. Nothing runs until you press Start; then Pause, Resume and Stop.

Budgets

A long task has a budget: $10 unless you name another, from $0.50 to $500, for up to 30 days. When the budget is spent, the task stops and waits for you. /long shows where the thread's long task stands and changes it: start, pause, resume, stop, or a new budget.

Reports

Mori reports at each milestone and once a day (at 9:00 unless you pick another time), in the app, or in Telegram and Discord when you ask, or when the task was asked for from a bot, where the reports go back to that chat.

On this computer or a cloud machine

On your computer, closing Mori or the lid pauses a long task, and it picks up when Mori opens again. On a cloud machine it keeps going while your computer sleeps, and the card shows the machine's cost and the hours left.

Cloud machines come with every paid plan: a Standard machine has 2 vCPU, 4 GiB of memory and 10 GiB of disk, and a Large has 4 vCPU and counts two hours for each hour. Plus has 40 cloud hours a month, Pro 120, Studio 300 and Max 600. Run on Cloud, Continue on Cloud and Return to This Mac move a thread, once cloud threads are set up in Settings > Connections.

Boxes that say what she is on

Each piece of work, a workflow, a crew, a research run, or the helpers of a turn, is a box with a title from the actual work, one line about it, its phases, one row per agent with what it is doing, its model, its tokens and its time, and a Stop.

When helpers start

Mori decides when a helper helps. A box appears only when a helper really starts:

• Never when you said no helpers, and never for small asks.
• At Instant and Quick, only for serious research or heavy jobs.
• At Balanced and above, for serious research or a heavy build.
• Always when you ask for them.

Crews

/crew <task> drafts a crew: a Captain and the members the job needs, a Builder, a Reviewer, a Tester, a Researcher or a Designer, each with its own model. Change any brief, model or order, then press Go; nothing runs before that. Members can work in their own git worktrees, one after another, merged back once at the end, and nothing is merged while your checkout has uncommitted changes.

/captain <task> runs a read-only planning pass first and hands you a spec to approve before the build.