Three ways to use the same agent. Look around freely; sign in to download. Bring your own local models or provider keys.
Which Michi should I choose?
I work mostly in
Start with Michi VS Code. You can add Michi Go later — both use the same engine and settings.
A real Michi Desktop session in a new folder: the app ran a real model (gemini-3.5-flash-lite), edited a file and ran its tests. A script typed the task and pressed Approve; idle seconds were trimmed from the start.
Michi Desktop
A native Mac app. Chat, watch tool calls and approve actions visually.
Platform
macOS [MIN VERSION] · [ARCH]
Built with
Electron 39 (39.8.10 installed)
Needs
The michi package, Python 3.11 or later, to run Michi Core
Real VS Code with the Michi extension, a real michi acp agent and a real model (gemini-3.5-flash-lite) in a new session. A script typed the task and pressed Approve once; the screenshot crops the chat panel.
Michi VS Code
Suggested for you
Michi in your editor, talking to Michi Core over ACP — the Agent Client Protocol.
Requires
VS Code 1.94 or later
Needs
The michi package, Python 3.11 or later, on the PATH (the extension starts `michi acp`)
A real michi go session in a new folder with a real model (gemini-3.5-flash-lite). A script typed the task and answered the approvals; the recorded terminal output is replayed at its original timing in a terminal emulator, and idle time after the finish is cut.
Michi Go
The interactive terminal agent. The most direct line to Michi Core.
Installs the michi package, Ollama and a default model. The repository is private today, so GitHub CLI must be signed in as a collaborator (gh auth login). On Windows use install.ps1. Local use needs no Michi account.