Voice Input for Every Text Field in Chrome

Short answer: click into any text field in Chrome, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak, press it again to stop. AICHE drops cleaned-up text at your cursor. No extension, no per-site permission prompt, no Manifest V3 to worry about.

The Problem

Chrome is where the workday actually happens. Gmail, Google Docs, ChatGPT, Claude.ai, Jira, Notion, Linear, Slack web, Salesforce, your internal admin tool, the CMS, the dashboard nobody else uses. Twenty tabs across three profiles.

Every one of them wants you to type. And the voice options inside Chrome are narrow:

• Chrome's built-in Voice Typing only works in Google Docs and Slides, only with the document and account language set to English (commands in English, French, German, Italian, Spanish), and sessions tend to silently disconnect after 10-15 minutes.
• Voice extensions are per-site. They break on the next Manifest V3 update, ask for permission on every domain, and do nothing for the CMS your company built in-house.
• OS dictation (macOS Dictation, Windows Voice Access) fights with rich text editors and inserts raw, unpunctuated text.

You end up typing.

What Changes

AICHE runs as a desktop app, not a Chrome extension. It captures audio at the OS level and inserts text into whatever field has focus. Chrome doesn't know it exists. That's the point.

1. Open any tab. Click into any text field (a Gmail compose window, a Jira comment, a ChatGPT prompt, a Webflow rich text block, the DevTools Console).
2. Press ⌃+⌥+R on Mac or Ctrl+Alt+R on Windows/Linux.
3. Speak. Pace around. Pause to think. The hotkey is a toggle, so the recording stays open until you press it again.
4. Press the hotkey again. AICHE transcribes, cleans the text (filler words out, punctuation in), and inserts it at the cursor.
5. Submit. Send the email, post the comment, run the prompt.

The same hotkey works in tab 1 and tab 27. It works in your work profile and your client profile. It works in a Chrome Incognito window. It works in a Chrome-installed PWA. It works in a Chromium fork (Brave, Arc, Edge, Vivaldi) because none of that matters when you're operating below the browser.

Math: speaking is roughly 150 WPM. Typing is roughly 40 WPM. The 80-word Jira comment that takes you 2 minutes to type takes 30 seconds to speak.

Web Apps Are Text Fields. AICHE Handles Text Fields.

A normal Chrome workday cycles through 8-12 web apps. Each one has its own input quirks:

• Gmail uses a rich text contenteditable. AICHE inserts plain text that respects the cursor and any formatting already around it.
• Google Docs has its own canvas-based editor. AICHE inserts through the active input, so it works without you switching into the built-in Voice Typing dialog.
• ChatGPT, Claude.ai, Gemini, Perplexity all use a textarea or contenteditable for prompts. Long, context-rich prompts that you'd never type in full are easy when you can pace and talk.
• Jira and Linear want structured comments and ticket descriptions. Speak the repro steps in order, fix names, expected vs. actual.
• Notion blocks, Webflow CMS, Ghost, Sanity, Contentful, Strapi are textareas wearing a rich-text costume. AICHE doesn't need a per-CMS integration to work in them.
• Internal admin panels and SaaS dashboards are where extensions never go and where voice support never ships. AICHE works in them anyway.

You stop hunting for the right voice tool for the right app. There is one tool, one hotkey, every field.

Chrome Profiles, Incognito, And Multiple Accounts

If you run separate Chrome profiles for work and personal, or one profile per client, AICHE behaves the same in every profile. No extension to install per profile. No permissions to re-grant. No syncing to wait on.

It also works in Incognito and Guest windows, where extensions are disabled by default. If you've ever opened Incognito to test something and then needed to write a long message, AICHE is still there.

ChatGPT, Claude.ai, And Other Chrome-First AI Tools

Most people use ChatGPT, Claude, and Gemini through their web UIs in Chrome, not through a desktop app. AICHE is built for this. Long prompts get better answers, and speaking is the only way most people will write long prompts.

A real prompt looks like: "We're refactoring the checkout flow. The current code splits validation across three React components and the cart store. I want you to propose a structure that consolidates validation in a single hook, keeps the existing error messages, and doesn't require changes to the API. Show me the file layout first, then the hook signature, then one example component."

You will type a third of that. You will speak the whole thing.

DevTools Console

Click into the Console tab inside Chrome DevTools, press the hotkey, and dictate a fetch call, a query selector, or a multi-line expression. Bracket-heavy JavaScript is annoying to type and trivial to speak when AICHE handles the punctuation. The same trick works in the Sources panel for quick logpoint conditions.

Installed PWAs

When you install a PWA from Chrome (Notion, Linear, ClickUp, Figma, Spotify, WhatsApp Web), it gets its own window and behaves like a native app. AICHE doesn't care that it came from a browser. The hotkey works in the PWA window the same way it works in a regular tab.

What About Chrome's Built-In Voice Typing?

It exists. It's good for what it does. It is not what you want for prompt-heavy or cross-app work:

• Tied to Google Docs and Slides only.
• Account and document language must both be English to use voice commands.
• Sessions tend to drop after 10-15 minutes without telling you.
• No custom vocabulary, no filler removal, no AI cleanup.

If you have Chrome's voice typing enabled in a Docs tab, turn it off there to avoid two listeners fighting for the mic. AICHE handles the rest of Chrome.

What You Get

• Global hotkey capture across every Chrome tab, window, profile, and PWA - because AICHE is desktop-level, not browser-level.
• Smart Insert - cleaned text lands at the cursor in whatever editor you're in.
• Software Development profile (Pro) - recognition tuned for API names, kebab-case flags, snake_case identifiers, library names. Useful for DevTools and AI prompts about code.
• Custom vocabulary - drop in product names, internal services, teammate names, repo names. Spelled the way you want them.
• Multilingual input and auto-translation - speak in your native language, get English text in the field. Useful for prompts and customer-facing replies.
• Offline queueing - record on a flight or a train. Process when you're back online.
• Zero-retention audio - audio is purged immediately after processing, within 1 second.

Plans start at $3.99/mo (annual) with a 7-day free trial, no credit card. See pricing.

Common Questions

Q: Do I need to install a Chrome extension?
A: No desktop extension is required for this workflow. AICHE can run as a desktop app alongside Chrome, and AICHE also has a separate Chrome extension surface where that fits better.

Q: Does it work in Incognito windows?
A: Yes. AICHE is not a browser extension, so Chrome's Incognito extension restrictions don't apply.

Q: I use 4 Chrome profiles for different clients. Do I have to set AICHE up in each one?
A: No. AICHE runs once, on the OS. The same hotkey works in every profile and every window.

Q: Will it work in a Chromium fork like Brave, Arc, Edge, or Vivaldi?
A: Yes. Anything that renders a focused text field on macOS, Windows, or Linux is fair game.

Q: Does it work in Google Docs without Chrome's Voice Typing turned on?
A: Yes, and we recommend turning Chrome's Voice Typing off in Docs so the two don't compete for the microphone.

Q: Will it mess up code I dictate into the DevTools Console?
A: Turn on the Software Development profile (Pro). It handles bracket-heavy syntax, method names, and identifiers more cleanly than a general-purpose model. Smart quotes off in settings keeps strings shell-safe.

Q: ChatGPT and Claude.ai already have voice input in the web UI. Why use AICHE?
A: The built-in voice modes are conversational and tied to that one site. AICHE works in ChatGPT's input field, then in your Gmail reply, then in the Notion doc where you're saving the output, all with the same hotkey and the same cleanup behavior.

Result: Chrome stops being the place where you type all day. The tabs don't change. The hotkey does the work.

Try it now: open the Chrome tab you used most yesterday, click into its main text field, press your hotkey, and speak the message you would have typed.