How Michi works
One engine, three clients, and a router that shows its reasoning. Start with the short version and go deeper where you want.
Michi Core
The shared engine behind every client: agent loop, routing, tools, sessions, approvals. Desktop, VS Code and Go are clients of it.
Michi Router
How Core picks an eligible model offering for each task and records why. It checks which models you can use — local, API or subscription — weighs capability, cost and your policies, then selects one.
ACP
The Agent Client Protocol lets an editor talk to Michi Core. Michi VS Code connects to Core this way.