Coming From…

Mochi doesn't ask you to switch task runners. Keep the one you have; Mochi finds its tasks and adds search, history, a desktop app, AI and agent controls around them.

Make

Your targets show up as tasks, and make still runs them. What you gain is everything Make doesn't keep: a searchable list of every target across every repo, the output of every run, and an answer when one fails. A target named docker-build is filed as a build, so it sits with your other builds.

npm scripts

Your package.json scripts become tasks. npm still runs them. Search across all your projects instead of opening package.json to remember whether it was dev, start or serve.

just and Task

Recipes and tasks show up like any other, with their descriptions. Mochi doesn't replace your Justfile or Taskfile: it reads them and runs them through just and task.

Shell history and READMEs

If your commands live in your head, your shell history or a README, write them down as a flow executable once. From then on they're searchable, documented and recorded like everything else. See Workspaces & Secrets.

flow

Nothing to migrate. Your workspaces, flow files, vaults and history work as they are, every flow command also works as mochi, and the two can stay installed side by side, reading the same data.