Mochi

Mochi is a desktop and CLI platform built on top of Flow. Point it at any directory and it finds your Makefiles, npm scripts, Justfiles, Taskfiles, and GitHub Actions, turns each one into a runnable and documented workflow, and keeps a record of every run.

Three verbs describe what it does, and they’re a useful way to read the architecture too: find, run, and remember.

Design Philosophy

• Local-first: Your commands, your logs, and your secrets stay on your machine. AI is optional. Bring your own key, or run fully offline.
• Built on Flow, not forked from it: Mochi inherits Flow’s execution engine, vault, and composability model. It doesn’t reimplement any of them.
• Nothing written into your workspace: Discovery surfaces what you can already run. It does not generate files into your repo.
• AI-enriched, not AI-dependent: Everything works without a model configured.

One Binary, Two Surfaces

Mochi does not fork Flow. cmd/mochi builds its command tree from Flow’s public pkg/cli extension API, so mochi is Flow’s entire command set plus a few of its own, with license validation applied as a pre-run hook.

The extension surface is small on purpose. Build the root command, register all of Flow’s commands, then find existing ones and graft onto them. Mochi’s vault preset hangs off Flow’s vault group; executable edit and executable add hang off executable; sync is wrapped so discovery runs before Flow’s own sync. Each graft degrades gracefully: if Flow ever stops shipping vault, the presets are simply unavailable rather than orphaned under a group of their own.

Resources

• mochiexec.io
• Flow architecture
• Homelab