Note
Mochi is in early access. Join the waitlist at mochiexec.io.
Mochi is a local-first DevOps dashboard built on top of Flow. Point it at a directory and it finds your development workflows and turns them into a unified, AI-enriched interface.
Design Philosophy
- Local-first: No cloud sync, no external accounts required. Your workflows never leave your machine.
- Built on Flow: Mochi inherits Flow’s execution engine, secret management, and composability model rather than building a parallel system from scratch.
- AI-enriched, not AI-dependent: AI augments the experience with workflow analysis and suggestions, but the tool works without it.
- Unified discovery: Meet developers where they are instead of requiring migration to a new workflow format.
System Overview
Mochi wraps Flow’s CLI engine as its execution runtime. The desktop app and CLI share the same binary, with the desktop communicating through process execution in the same pattern as Flow’s architecture. Discovery runs at startup and on sync, after which all discovered executables are available in both the dashboard and CLI identically.
The desktop is not yet released, but the architecture is taking shape. Here’s a preview:
Auto-Discovery Engine
Mochi’s discovery layer imports executables from common developer workflow files without requiring any configuration changes.
Discovered executables are treated identically to native Flow executables once imported: they appear in the browse interface, support the same reference patterns, and can be composed into larger workflows. The sync step surfaces naming conflicts clearly so nothing is silently overwritten.
This discovery system is built on the same import infrastructure in Flow’s core. See the Flow architecture for implementation details.
AI Enrichment Layer
Mochi connects to an AI provider for workflow analysis, troubleshooting suggestions, and workflow context. You can use Anthropic’s cloud API or a local Ollama instance depending on your preference and privacy requirements.
The enrichment layer is optional and additive. The dashboard is fully functional without it, and workflow definitions are processed locally before anything is sent externally.
Desktop and CLI Architecture
Mochi ships as a single binary that includes both the CLI and the Tauri desktop backend. I chose Tauri because it was the most interesting option at the time, given my interest in learning Rust and building a desktop app without the overhead of Electron. The frontend is TypeScript/React with Mantine UI.
Type safety across Go, TypeScript, and Rust is maintained through code generation from a shared JSON schema. Schema changes propagate to all three languages automatically during the build, and the same schema generates documentation as a side effect. This has been one of the best quality-of-life decisions in the project — make a change in one place and have confidence everything stays consistent.
