Dictate code comments and commit messages in VS Code
VS Code runs on macOS, Windows, and Linux, and voice input works in every editor tab, source control message field, and markdown preview using the system dictation.
Code comments and commit messages get skipped when typing feels slow, and voice input keeps that history rich so the next reader gets the why behind the change.
Start voice input
On Mac press the Fn key twice inside the target field.
On Windows press Windows plus H to open voice typing.
On Chromebook enable dictation in Accessibility settings.
Click into a comment line, the source control message box, or a markdown file before you speak.
Comments vs commits vs markdown
Code comments explain intent. Commit messages carry the shape of the change. Markdown files hold docs. Speak in each shape and the repo stays readable.
Draft in Zahvox for public copy
For anything published as public docs, a readme, or a release note, dictate the raw thought in Zahvox, tighten the wording, then paste it back. That extra pass keeps the tone steady and removes filler.
Small habits that keep it readable
Say punctuation out loud, including commas and periods.
Keep one thought per sentence so cleanup is fast.
Do a short review pass at the end of every session.
Save common phrases in a snippet tool so voice input can call them.
Measure the workflow by output, not by feel
A month into using dictate code comments and commit messages in vs code, look at what actually shipped: emails sent, notes filed, posts published, tickets closed. That number is the honest scorecard. The workflow either produced more finished writing than the keyboard-only version or it did not. If it did, keep going and stop second-guessing. If it did not, one specific piece is broken — usually the edit step, not the capture step — and that is the piece to fix next.
Where Zahvox fits after the raw capture
Zahvox is the careful second pass that sits after the raw capture. The browser, the OS, or the app you used for dictate code comments and commit messages in vs code gave you words on a page. Zahvox at /tool is where you paste those words, tighten the wording, fix the shape of the sentences, and copy the result back into wherever it needs to live. Raw capture anywhere, careful edit in Zahvox — that is the whole loop, and it stays the same whether the source was a laptop, a phone, or a meeting transcript.
