Added
- Connect an AI assistant from the browser, not just from a command line. Browser-based clients such as claude.ai sign in through a consent screen instead of carrying a key in a config file: they ask, you paste one of your API keys, and that is the whole connection. Everything the assistant can then read is what that key allows — its role and its sites — and it is still read-only.
- Connected clients are listed on the API Keys page, showing which key each one used, when it connected and when it last read anything. Disconnect one from there, or revoke the key to disconnect everything using it.
- Revoking a key disconnects its clients immediately, and changing a key's role or sites applies to the next thing the assistant asks — no reconnecting.
- New setting under Settings > MCP endpoint: Public URL, the HTTPS address your install answers on from outside.
What you need for this
This only works if your mikr is reachable from the internet over HTTPS — the browser has to open your consent screen and then return to the assistant's site. If mikr lives on your LAN, which is the usual case, nothing changes and nothing breaks: a command-line assistant with an API key still works exactly as it did, and the new endpoints stay switched off until you fill in a Public URL.