Does Parakeety work with all the JetBrains IDEs?

Yes. IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, PhpStorm, CLion, RustRover, DataGrip and the rest of the family share the same underlying IntelliJ Platform, and Parakeety pastes at the cursor in every one. The dictation surfaces below describe the platform as a whole; the same workflow applies across languages.

Where is the dictation actually useful in IntelliJ?

In the AI Assistant chat, in the VCS commit message dialog, in JavaDoc / KDoc / Python docstring blocks, in TODO and FIXME annotations, in markdown plugin previews for READMEs, in commit-message templates, and in the description field of run configurations. Any text input the IDE shows you, Parakeety can dictate into.

Should I dictate code in IntelliJ?

No, type code. JetBrains IDEs have aggressive code completion, live templates and Postfix completion that make typing identifiers very fast; dictation has no advantage there and will fight the model on casing. Reserve dictation for the JavaDoc-style narrative, commit messages, and AI Assistant prompts that benefit from longer prose.

Does Parakeety conflict with Code With Me or other collaborative features?

No. Parakeety captures your microphone for dictation only; it does not interact with Code With Me audio, screen sharing, or remote-development sessions. You can dictate into a shared editor the same way you would dictate into a local one; only your transcript reaches the shared session.

← Resources

Dictating into JetBrains IDEs with Parakeety

The JetBrains family (IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, PhpStorm, CLion, RustRover, DataGrip) shares one IDE platform and one set of conventions. Dictation fits the same shape across all of them: not the code, not the identifiers, not the live-template expansion. The narrative around it: the AI Assistant prompts, the doc comments, the commit messages, the TODO annotations, the README files in the markdown plugin. Push-to-talk for the prose; the keyboard for everything else.

Where dictation fits inside an IntelliJ-family IDE

The places worth holding the section key:

AI Assistant chat. The side-panel chat that takes longer prompts and asks the model to plan changes. Dictate the intent; type the identifiers you reference.
Commit message dialog. The VCS commit panel that opens before every commit. The prose-friendly part of source control; dictation produces noticeably better commit messages than typing.
Doc comments. JavaDoc, KDoc, Python docstrings, Go doc comments, the structured comment block that lives above each function. Type the comment delimiters; dictate the description.
TODO and FIXME annotations. The inline notes you leave for yourself or for review. Quick, low-formality, dictation-friendly.
README and markdown documentation. The markdown plugin previews work cleanly; whole-document dictation is the highest-payback workflow.
Run configuration descriptions. The "why does this run-config exist" notes you write into the description field, which future-you will thank you for.
Issue templates and code review comments. When you write back to a teammate through the IDE's integrated review tooling, dictation matches the tone.

A worked example

You just shipped a fix for an issue that took three hours to reproduce. The commit is staged; the VCS commit dialog is open. Typing the commit message, most engineers settle for "fix race condition in upload handler". Dictated, you naturally write the version your future self and your reviewers actually need:

"Fix a race condition in the upload handler that left zero-byte files in storage on slow connections. Two goroutines were closing the multipart writer concurrently when the request context was cancelled mid-flight; the second close call was a no-op but left the underlying file descriptor in a state where the size header had not been written. The fix is to gate the close call on a sync.Once. There is a new test that reproduces the original failure by cancelling the request after the first chunk; it fails on main and passes on this branch."

Around thirty seconds dictated, two minutes typed. The reviewer no longer has to reconstruct that story from the diff and the linked issue.

Tips specific to JetBrains IDEs

Focus on the input field. JetBrains layouts have many tool windows; the cursor needs to be in the AI Assistant chat or commit dialog, not in the editor, before you start holding the key.
Doc-comment templates. Type the comment delimiters and the IDE's live template fills in the parameter scaffold; dictate the description into each section that lights up.
Code With Me and remote dev still work. Parakeety only captures your local microphone for transcription; the JetBrains collaboration features carry their own audio/text channels separately.
Section key as the shortcut. The default Parakeety key (§) does not conflict with the JetBrains IDE shortcuts (which lean heavily on Cmd, Cmd-Alt, Cmd-Shift). No keybind remapping needed.
Commit-template plugins. If your team uses a commit-template plugin (Conventional Commits, etc.), expand the template first, then dictate the body. The structured fields stay typed; the body gets the speed-up.

NDA-bound code paths

Internal product names, customer names, unreleased feature codenames and in-progress designs show up in your AI Assistant prompts and commit messages. Parakeety keeps the audio leg on the Mac: the speech model runs on the Apple Neural Engine, the audio is captured to memory and discarded after transcription. AI Assistant itself sends the prompt text to JetBrains' configured model provider; that is a separate setting (and an organisational decision) governed by your JetBrains AI subscription and any team-level controls.

The wider engineer-side framing is in Parakeety for engineers and developers; the Cursor-specific workflow piece is Dictating into Cursor with Parakeety.

FAQ

Does Parakeety work with all the JetBrains IDEs?: Yes. IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, PhpStorm, CLion, RustRover, DataGrip and the rest of the family share the same underlying IntelliJ Platform, and Parakeety pastes at the cursor in every one. The dictation surfaces below describe the platform as a whole; the same workflow applies across languages.
Where is the dictation actually useful in IntelliJ?: In the AI Assistant chat, in the VCS commit message dialog, in JavaDoc / KDoc / Python docstring blocks, in TODO and FIXME annotations, in markdown plugin previews for READMEs, in commit-message templates, and in the description field of run configurations. Any text input the IDE shows you, Parakeety can dictate into.
Should I dictate code in IntelliJ?: No, type code. JetBrains IDEs have aggressive code completion, live templates and Postfix completion that make typing identifiers very fast; dictation has no advantage there and will fight the model on casing. Reserve dictation for the JavaDoc-style narrative, commit messages, and AI Assistant prompts that benefit from longer prose.
Does Parakeety conflict with Code With Me or other collaborative features?: No. Parakeety captures your microphone for dictation only; it does not interact with Code With Me audio, screen sharing, or remote-development sessions. You can dictate into a shared editor the same way you would dictate into a local one; only your transcript reaches the shared session.

Try it

Parakeety is a Mac menu-bar app. Hold the section key, talk, release; your words paste at the cursor in whichever app you were typing into, including every input surface in the JetBrains IDE you spend your day in. Audio never leaves the machine. There is a free 7-day trial with no card required. After that it is $30 once.

Try Parakeety free →