1. Separate JetBrains Air from classic IntelliJ-based IDEs
JetBrains Air is an agentic development environment with its own Chat task input. Its current documentation explicitly includes optional voice input and a dedicated Voice Input setting.
IntelliJ IDEA, PyCharm, WebStorm, and other classic JetBrains IDEs have editor, commit, and AI Assistant text surfaces. The current classic IDE documentation reviewed here does not identify Air’s microphone as a shared platform feature. Do not copy Air setup or local-audio claims into every JetBrains product.
2. Use Air’s native microphone for an Air task prompt
Open Air Settings, search for Voice Input, and download a local Whisper model. JetBrains lets you optionally choose the model size and recognition language. When the status is Ready, return to Chat and select the microphone in the task input.
JetBrains states that Air voice recognition uses the local Whisper model and no audio is sent to the cloud. That narrow statement covers the speech-recognition stage. After transcription, the prompt, selected context, agent, model, environment, permissions, and tool actions follow the Air task you configure.
- Download the Air voice model before the first task.
- Speak into the visible Chat task input.
- Review the task, context, environment, agent, model, and permission mode.
3. Use focused-field Dictation in a classic JetBrains IDE
In IntelliJ IDEA, PyCharm, WebStorm, or another classic IDE, place the insertion point in the exact editor, documentation, comment, commit-message, or AI Assistant prompt field. Start the macOS Dictation shortcut, speak, stop, and confirm the transcript appeared in the intended surface.
JetBrains documents Escape for moving focus back to the active IntelliJ editor and distinct shortcuts for tool windows. Focus matters because a transcript intended for a comment can otherwise land in AI Chat, Search Everywhere, the terminal, or another custom editor.
4. Treat code, commands, and identifiers as high-risk text
Dictation is useful for prose in documentation, comments, commit messages, and agent requirements. It is not deterministic source-code entry. Check case-sensitive symbols, file paths, package names, generics, operators, punctuation, quotes, indentation, numbers, negations, and security-sensitive wording.
For exact code or shell commands, prefer typing or pasting from a trusted reviewed source. Do not press Return in a terminal or accept an AI-generated change merely because the transcript sounds plausible.
5. Keep AI Assistant context and agent actions separate from input
JetBrains AI Assistant supports chat, code-aware context, files, folders, symbols, images, and agent workflows across supported IDEs. Dictation can create text in an accepted prompt field; it does not choose the model, attach the right context, approve a tool call, apply an edit, or run a command.
In Air, JetBrains separately asks you to choose a task run environment, agent and model, permission mode, and context before running a task. Inspect those controls after voice recognition and before submission.
6. Review commit messages and troubleshoot focus separately
IntelliJ IDEA provides an explicit commit-message field and Commit action. Dictate the rationale if useful, then verify issue keys, component names, versions, breaking-change language, and the selected changes before committing or pushing.
If Dictation fails everywhere, test TextEdit and follow Apple’s checks for Keyboard settings, shortcut, language, microphone, Voice Control, and connectivity. If only one JetBrains surface fails, confirm it is editable, move focus deliberately, and use the clipboard fallback for a custom editor that rejects system insertion.
7. Add IraVoice only for the cross-app or structured brief workflow
Use JetBrains Air’s microphone first when the destination is already an Air task prompt. Use macOS Dictation first for occasional prose in a supported classic IDE field.
IraVoice 0.7.1 is the separate option for macOS 26+ Apple-silicon Macs when one held-key workflow should produce editable text across supported apps, or when a longer spoken engineering request should become reviewable Markdown before you choose an IDE or agent. IraVoice does not read a JetBrains project, choose context, control AI Assistant or Air, apply edits, run code, press Commit, or push changes.