Mochi

How Mochi finds what you can run, and why discovered executables are generated at read time instead of written into your repo.

One binary, two surfaces. The Tauri sidecar boundary, the JSON contract between Rust and Go, and how types stay honest across three languages.

What Mochi remembers about every run, where it is stored, and how the dashboard turns it into something readable.

A provider-agnostic AI layer, bring your own key, and why the secret never lands in Mochi configuration.

Reflections on how I’ve been using AI as a development partner - what I delegate, what I don’t, and what it’s produced.