Short answer: place your cursor in any cmux tab, press ⌃+⌥+R, speak your prompt, press the hotkey again. AICHE inserts the cleaned-up text at the cursor in 2-3 seconds. Works in every tab, every pane, any agent.
cmux is a native macOS terminal multiplexer built on Ghostty's rendering engine. Vertical tabs in the sidebar, notification rings when a pane needs your attention, split panes for code alongside the agent, and an embedded browser so you don't leave the workspace to look something up. It was built specifically for running multiple AI coding agents in parallel - Claude Code in one tab, Codex in another, OpenCode on a different branch in a third.
The organizational side of that workflow is solved. The input side is not. You still type to every waiting agent.
AICHE changes that part.
The Multi-Agent Workflow
Each agent periodically pauses at a decision point - a question, a clarification, a request for more context. The notification ring fires in the sidebar. You switch to that tab. And then you respond.
A short response ("yes, proceed") gets mediocre output. A full response - one that covers the context, the constraints, the tradeoffs you already considered - gets something you can ship. That kind of response takes 90 seconds to type and 12 seconds to say.
The workflow with AICHE:
- Notification ring fires. Switch to the waiting tab.
- Place your cursor at the agent prompt.
- Press ⌃+⌥+R.
- Speak the full answer - the context, the constraints, the "by the way" details.
- Press ⌃+⌥+R again. The response appears, filler removed, punctuated.
- Hit Enter. Switch to the next waiting tab.
You spend 15 seconds per agent response instead of 90. The agents get better prompts. With four agents running in parallel, the time difference compounds quickly.
Notification Rings and the Response Loop
cmux fires a visual ring in the tab sidebar when a pane needs your attention, triggered by standard terminal escape sequences (OSC 9/99/777) or directly from agent hooks. You don't poll through tabs looking for a waiting agent - the sidebar tells you.
The combination with AICHE is tight: ring fires, you switch, you speak, you move on. The visual cue and voice response form a loop that doesn't require your hands between steps. You can be reading the output of one agent while a ring fires for another - glance at the sidebar, switch tabs, dictate the answer, return.
Split Panes
cmux splits panes horizontally and vertically within a tab. The standard agent work pattern: code or diff on one side, agent prompt on the other. You see what you're responding to without switching apps or windows.
AICHE inserts into whichever pane has focus. Put the cursor in the agent pane, look at the code pane, and speak what you want changed. Eyes on the source, voice into the agent.
This works inside nested sessions too. If you run tmux inside a cmux tab - some workflows use both - AICHE inserts into whichever tmux pane has focus.
Embedded Browser
cmux includes a split-screen browser panel alongside your terminal. The intended use is staying in the workspace while checking docs, a PR, or a ticket - without opening a separate window.
The agent pane next to the browser is a standard text target. Look at what you need in the browser panel, switch focus to the agent, and speak the task. "Implement the endpoint shape shown in the docs I have open, match the error codes exactly, and keep the existing retry logic." You describe what you see without copy-pasting anything across windows.
Commit Messages Across Tabs
The voice workflow works in every cmux tab because AICHE inserts at the cursor regardless of which tab is focused. git commit opens your editor. Press i in vim, press ⌃+⌥+R, speak what the change actually does - not just what changed but why, what you considered, what reviewers should know. AICHE cleans it up and inserts it in about 20 seconds.
If you have several agents committing independently as they finish work, you can dictate the commit message into each tab in sequence without breaking the multi-agent rhythm.
What You Get
- Unlimited voice input with AI cleanup - filler words removed, punctuation added, ready to send to any agent.
- System-wide hotkey - one shortcut, every cmux tab, every pane. Works in your IDE, browser, and Slack too.
- Software Development profile (Pro) - recognition tuned for code terms, CLI flags, library names, API identifiers.
- Custom vocabulary - add project names, internal service names, and agent-specific jargon. Spelled correctly every time.
- Zero-retention audio - 2-3 second processing window, then deleted. Nothing stored.
Plans start at $3.99/mo (annual) with a 7-day free trial, no credit card required. See pricing.
Common Questions
Does the AICHE hotkey conflict with cmux shortcuts?
⌃+⌥+R is not used by any cmux default shortcut. cmux chords use Cmd-based combinations. If you have a custom mapping that conflicts, remap AICHE's hotkey in its preferences.
Does it work inside tmux running inside a cmux tab?
Yes. AICHE sends keystrokes to whichever window has OS-level focus. If a tmux session is running inside a cmux tab, text goes into the focused tmux pane.
Does Secure Keyboard Entry affect AICHE in cmux?
No. cmux is built on libghostty, and the same answer applies as Ghostty: AICHE does not use the macOS dictation stack, so Secure Keyboard Entry doesn't interfere. Leave it on.
Does it work with every agent cmux supports?
Yes - Claude Code, Codex, OpenCode, Gemini CLI, Aider, Amp, Cline, Cursor Agent, Goose, and any other agent running in a terminal pane. AICHE doesn't know or care what agent is in the tab. It inserts text wherever the cursor is.
Can I use the Software Development profile?
Yes. The Pro-tier profile tunes recognition for code terms, API names, CLI flags, library identifiers, and developer jargon. When your prompts include technical context, it improves accuracy on the terms that matter most.
Result
cmux handles the organizational side of parallel agent work: tabs, rings, splits, browser access. AICHE handles the input side: you speak to your agents instead of typing at them.
The notification ring becomes a cue to switch and speak, not switch and type. The agents get full context instead of compressed shorthand. The prompts get better because speaking a 200-word response is faster than typing a 30-word one.
Try it now: open cmux with two or more agent sessions running, wait for a notification ring, switch to that tab, put your cursor at the prompt, press ⌃+⌥+R, and say the full response you actually want to give.