m’kay

m’kay is a voice interface for the AI coding agents already running on your Mac. Rather than sitting at a terminal or an editor window to check on a task, you open a browser page or pick up your phone and simply talk to Claude, ChatGPT/Codex and Cursor. It is built for developers who want to stay in touch with their coding agents when they step away from the desk, and its main purpose is to give one voice to all of your agents — not just a single assistant — while the agents themselves keep running as the real desktop apps you already use. Most voice tools for AI are designed around talking to one assistant. That model breaks down for developers, because real work is often spread across several coding agents running side by side on the same machine. m’kay was built for that reality: it talks to all of your agents rather than one. It also drives the real desktop applications instead of a remote copy, which means the sessions and projects you already have stay exactly where they are. The problem it solves is one of distance — your work lives on your Mac, but you are not always sitting in front of it, and the tools you use to reach it should not force you to relocate that work somewhere else. Getting started is described as a short linking step. A small open-source connector runs on your Mac and drives the agent apps you already use. You sign in once to link the connector, and from that point on your Mac and your browser session are connected. Because the connector is open source, you can inspect what it does, and because it works with the applications you already have installed, there is no need to move your coding sessions into a new environment or re-create your projects elsewhere. The setup is deliberately light: link once, and the voice channel to your machine is available. Once your Mac is linked, the whole product is accessed through voice. You can ask what your agents are doing, have their replies read aloud to you, and give them the next task — all from any browser or phone. That means the interface is not tied to a particular device or operating system: a phone's browser is enough. The workflow is conversational. You ask a question, you get an answer spoken back to you, and you respond with the next instruction, which is then carried out on your Mac. Reading replies aloud matters because the answers arrive where your attention already is, rather than requiring you to read a terminal window on a small screen. One voice reaching multiple agents is the core idea. Your Mac may be running Claude Code, Codex and Cursor at the same time, and m’kay lets you address all of them. You can ask which one is done, hear its reply, and tell it what to do next. This matters because the natural question when several agents are working is not what the assistant is doing, but which of my agents has finished — and the product is built to answer exactly that. Speaking to several agents through one channel removes the need to switch between separate tools or windows just to find out where each one stands. m’kay includes an explicit confirmation step before anything is sent. Nothing is sent until you say \"yes\" to a read-back, meaning the instruction is spoken back to you for approval before it is passed to the agent. For voice-controlled developer tooling this is a meaningful safeguard: spoken input is easy to mishear, and a command sent to a coding agent can change real files in real projects. The read-back gives you an opportunity to catch a misunderstanding before it reaches your codebase, so remote convenience does not come at the cost of unintended changes. You can run m’kay in two different ways. The first is the hosted voice page: you sign up and use the hosted service to talk to your Mac. The second is fully local: you clone the project and run everything on your Mac, using local models or your own API keys. There is also a menu-bar Mac app. The open-source nature of the project is central to this choice — the connector and the ability to run the whole thing locally mean you are not required to route your voice traffic through someone else's infrastructure if you would rather keep it on your own machine. The website presents both paths as equal options rather than a single mandated route. The benefit is continuity. Because m’kay drives the real desktop apps, your sessions and your projects stay where they are; nothing has to be migrated, and the state of your work does not depend on a separate environment being kept in sync. You also gain reach, because the distance between you and your Mac stops being a barrier — a browser tab is enough to check in, listen to a reply, and issue the next instruction. And because every instruction is confirmed through a read-back, that reach does not come at the cost of accidentally sending the wrong command to a live project. The scenarios described are ordinary moments of being away from the desk. You are on the train and want to know which agent has finished, so you open the voice page in your phone's browser, ask, and hear the answer. You are at the gym and want to give the next task without going home first — you speak the instruction, hear it read back, confirm it, and it is sent to your Mac. Or you are simply in another room with a laptop and would rather talk to your agents than walk back to the machine that is running them. m’kay is aimed at developers who run AI coding agents locally and want a lightweight way to reach them by voice. The Mac app requires Apple Silicon and macOS 13 or later, and there is a direct DMG download. You can also sign up free for the hosted option, or clone the project from GitHub and run it locally. The Product Hunt listing describes it as open source and lists it under Productivity, Open Source, GitHub and Menu Bar Apps, and the website presents the same fork in the road: use the hosted voice page, or keep everything on your own Mac. m’kay's value proposition is simple to state and specific in what it delivers: one voice for all of your coding agents, reachable from any browser or phone, driving the real desktop apps so your sessions and projects stay put, with a read-back confirmation before anything is sent. It does not try to replace your agents or move your work — it gives you a way to talk to what is already running on your Mac, from wherever you happen to be.