m’kay is a voice layer for the AI coding agents that already run on your Mac. It lets you talk to Claude, ChatGPT/Codex and Cursor on your own Mac from any browser or phone, so you can ask what your agents are doing, hear their replies read aloud, and hand them the next task without being at your desk. It is built for people who keep coding agents running and want a single voice interface that reaches all of them, rather than a separate assistant to manage alongside their work. The Mac app runs on Apple Silicon and requires macOS 13 or later, and you can either download the menu-bar Mac app or clone the open source project and run it locally.
The problem m’kay addresses starts with a mismatch. Most voice tools for developers are built around a single assistant: you talk to one model, in one session, and that is the whole conversation. Developers rarely work that way. A working machine often has Claude Code, Codex and Cursor available at the same time, each with its own sessions and projects. The product's own framing puts it plainly — other voice apps talk to one assistant, while m’kay talks to all of your agents. On top of that, the moments when you most want to check in on a long-running task are often the moments when you are furthest from the keyboard: on the train, at the gym, or simply away from the desk. m’kay is designed for exactly those gaps, so progress on your agents is not tied to you sitting in front of the machine.
The core capability is multi-agent voice control. m’kay talks to Claude Code, Codex and Cursor on your Mac, not to a single assistant, and it lets you ask which one is done, hear its reply, and tell it what to do next. Because it drives the real desktop apps rather than a separate environment, your sessions and projects stay where they are — the work already open on your Mac is the work you are talking to. That continuity matters: there is no second copy of a project to keep in sync and no separate workspace to reconstruct before an agent can continue. The packaged menu-bar Mac app puts this control within reach whenever you are at the machine, and the same voice channel is what you use once you step away from it.
Remote access is the other half of the idea. The voice interface is reachable from any browser or phone, so the desk is optional. The product describes giving instructions from your phone's browser — on the train, or at the gym — where you ask what your agents are doing, listen to their replies read aloud, and give the next instruction by voice. Reading replies aloud is what makes this practical in situations where looking at a screen is awkward or impossible, and the browser-based interface means you are not tied to a particular device. The hosted voice page is available after a free sign-up, or you can run everything on your own Mac instead.
m’kay also builds in an explicit confirmation step for anything it sends. The product states that nothing is sent until you say "yes" to a read-back. In practice, the system reads back what it is about to pass to an agent, and the instruction only goes through after you confirm it out loud. Because the agent apps being controlled can act on real code and projects, that read-back works as a checkpoint between what you said and what an agent is actually asked to do, which is a meaningful safeguard when your instructions arrive by voice from a phone.
Getting started begins with linking your Mac. A small open source connector runs on your Mac and drives the agent apps you already use, and you sign in once to link it. From there you decide how to run the voice side of things: sign up for the hosted voice page, or run everything on your Mac with local models or your own API keys. The project is open source, so running it yourself is a supported path rather than a workaround, and the menu-bar Mac app is offered as the packaged way to use it on the desktop.
The benefits follow directly from those choices. You are no longer chained to your desk to know what your agents are doing, because you can ask and hear the answer from any browser or phone. You do not have to juggle separate assistants for separate tools, because one voice interface reaches Claude Code, Codex and Cursor together. Your sessions and projects stay in the real desktop apps, so nothing is disrupted when you check in remotely. And because the read-back confirmation gates every send, you keep a spoken checkpoint before anything is passed to an agent. If you want to keep everything on your own machine, running locally with local models or your own API keys is an available route.
Concrete use cases follow the workflow the product describes. You can ask which agent is done while you are away from your desk and hear its reply read aloud, then tell it what to do next. You can give a long-running agent its next task from your phone's browser on the train, without opening a laptop. You can check in and issue an instruction at the gym, where reading a screen is not practical and voice is the natural interface. You can run the whole thing locally on your Mac with local models or your own API keys. And because m’kay talks to all of your agents, you can move between Claude Code, Codex and Cursor through one voice channel instead of switching between separate interfaces.
m’kay is aimed at developers who already run coding agents such as Claude Code, Codex and Cursor on a Mac and want to reach them by voice from anywhere. It runs on Apple Silicon and requires macOS 13 or later, and it is available as a menu-bar Mac app or as an open source project you can clone and run yourself. The voice interface is used from any browser or phone, with a hosted voice page available after a free sign-up.
In short, m’kay turns the coding agents you already run on your Mac into something you can talk to from anywhere. One voice for all your agents, replies read aloud, a read-back before anything is sent, and sessions that stay in the real desktop apps — that is the value it offers to developers who want to stay in touch with their work without staying at their desk.