Mirmir for Mac
Mirmir for Mac is a native SwiftUI app for macOS 26.2 or later on Apple silicon. It lives in the menu bar and has a window for throughput and memory charts, the model library, chat, sessions, logs and the servers you use. It includes the MiRMiR runtime (mirmir 0.6.2 and MLX), so nothing else needs to be installed.
Install
- Download Mirmir for Mac, open the disk image and drag Mirmir to Applications. The app is signed and notarized.
- Start Mirmir. It starts the mirmir it includes as its own server.
Its own server
Mirmir runs sandboxed, like an App Store app. Its server lives in the app’s
container, ~/Library/Containers/tech.mirmir.app/Data, with its own
configuration, models and logs, and is separate from the
mirmir CLI:
- the app does not attach to a server the CLI or TUI started, and the CLI does not see the app’s server;
- models the app downloads stay in its container; the CLI’s models are not visible until you grant their folder (see below);
- the app’s OpenAI-compatible API listens on
http://127.0.0.1:18080/v1, so it does not collide with a CLI server on port 8080. Settings → Server shows the address for Zed, Raycast orcurl.
Use the app or the CLI on a Mac; running both means two servers, two model sets and twice the memory for a loaded model. Quitting Mirmir stops its server.
Model folders
The sandbox lets Mirmir read only the folders you choose. In Settings → Model folders, Add Folder… grants one:
- a Hugging Face cache, such as
~/.cache/huggingfaceor itshubfolder: the server lists its models next to its own (throughHF_HUB_CACHE) and restarts once to pick it up; - any other folder with checkpoints: load a model from it by path.
Models → Load from Folder… grants a checkpoint folder and loads it in one step. Grants persist across launches; Remove revokes one.
The app speaks the runtime protocol 2 of MiRMiR 0.6.2 and shows Update needed for an older remote server.
The menu bar and the window
Mirmir is a menu bar app: it has no Dock icon. Its icon shows the decode rate while a model generates; click it for the loaded model, live throughput, memory, active sessions and shortcuts to the window (Open Dashboard, Models…, Instances…, Download a Model…).
Closing the window keeps Mirmir running in the menu bar. To quit, choose Quit Mirmir (⌘Q) in the panel. Quitting stops the app’s server.
Servers
Mirmir shows one server at a time: This Mac, its own server, or a remote one. The Server card at the bottom of the sidebar names it, with its address, status, MiRMiR version and device; every screen’s subtitle starts with its name. Click the card to switch to another server or to manage the list. Switching changes the whole window and the menu bar, including the chat list: each conversation belongs to the server it was started on, because a model name means nothing on another server.
This Mac is always listed. Instances → Add Server adds a remote
server over TLS: enter host or host:port (the default port is 7443) and
an API key created on that server (a pasted grpcs://host:port works too). A
CLI server on the same Mac is reachable this way too, once its remote listener
is on. The app shows the server’s certificate fingerprint before it sends the
key; compare it with mirmir remote status on the server, trust it, then test
and add. Later certificate changes are refused. See
Remote access.
Edit Server… in Instances changes a server’s name, address, API key or trusted certificate and keeps its chats; a changed connection must pass a test before it is saved. Remove Server asks first and keeps the server’s chats: they come back when a server at the same address is added again.
Create the key on the server and name it after the computer that will use it:
mirmir remote key create --name my-mac --scope control
--scope use (the default) allows chat, model lists and monitoring, and a chat
may load a model the server offers; control also loads, unloads, downloads
and removes models and changes model and runtime settings. No key can change
the server’s own settings or stored secrets. Add --system on
a machine that runs the system server; remote servers keep using the CLI.
The first time you add a server on your network, macOS asks whether Mirmir may find devices on your local network: allow it. If you declined, turn Mirmir on in System Settings → Privacy & Security → Local Network; until then the app reports the server’s address as having no route.
API keys are stored in your login Keychain, never in the app’s files. macOS may ask once whether Mirmir may read its key; choose Always Allow.
Share this Mac
Open Instances → This Mac → Remote Access… to let other computers use the
app’s server: turn on the listener, copy
its certificate fingerprint, create keys with the use or control scope
(shown once), revoke them and see which clients connected recently.