Web dashboard
The browser dashboard is disabled by default. Enable it and restart the server:
mirmir config set server.web_enabled true
mirmir serve
Open http://127.0.0.1:8080/ui/.
What it exposes
- Dashboard shows live and historical throughput, prefill, decode, TTFT, memory, K/V occupancy, runtime counters, and recent activity;
- Models lists local snapshots, searches Hugging Face, and performs download, inspect, load, unload, and removal actions;
- Chat streams content and reasoning, accepts one image, exposes generation parameters, reports request metrics, and keeps recent conversations;
- Settings shows effective values, their source, restart requirements, paths, raw TOML, and redacted secrets.
One WebSocket carries telemetry, model snapshots, configuration, startup readiness, and activity. The browser does not poll each view independently.
The header of every view shows whether the runtime is generating, the active model, and the accelerator.
Models
Search Hugging Face by owner or model name and manage snapshots already present on the machine. Each row shows the weight encoding, the backends that can run it, and its capabilities (tools, thinking, vision). Model actions use the same runtime queue and memory checks as the terminal and CLI clients.
Chat
Select a loaded model, optionally attach one supported image, adjust one-off generation parameters, and stream reasoning and final content independently. The latest reply reports TTFT, prefill, decode, and end-to-end throughput.
Recent conversations appear beside the chat. Start another with New chat, reopen one from the list, or delete it. The history stays in this browser’s local storage, not on the server, and keeps the 30 most recent conversations.
Settings
Settings are grouped by section. Each row shows the effective value, its source,
and whether a change applies live or after a restart. After you change a
restart-bound setting, a banner lists it until you restart mirmir serve or
dismiss it. Secrets are redacted and use dedicated mutation paths.
Local security boundary
The dashboard can only be enabled on a loopback HTTP bind. Opening it creates an
eight-hour local session in an HttpOnly, SameSite=Strict cookie. Mutations
also require a CSRF token held in page memory. The OpenAI bearer token is not
accepted as dashboard administration authority.
For remote programmatic access, keep the dashboard local and configure the HTTP API security boundary separately.
Appearance and runtime details
The theme follows your system until you choose another appearance with the sun/moon button in the sidebar. Your choice is remembered. The Dashboard view includes prefill and decode charts, device telemetry, and server platform, backend support, device and host-memory details. Use Open chat on a resident model to start chatting with it. Screenshots use demonstration data.