It stopped working: which permissions should I check?

Open System Settings, then Privacy & Security, and make sure Writhere is enabled under Microphone, Accessibility and Input Monitoring (plus Screen Recording if you transcribe calls). Then relaunch the app: macOS applies some of these only to a fresh start. You can check them anytime from the Autorizzazioni section in the app dashboard.

What are the system requirements?

A Mac with macOS 13 or later. Apple Silicon (M1 or newer) is recommended: everything runs on-device, and the AI features are dramatically faster there. Intel Macs work too, with longer processing times for call transcription and summaries.

Why does it ask for the Microphone?

To hear your voice while you dictate. The audio is processed on your Mac and never leaves it.

Why does it ask for Accessibility?

To type the dictated text straight into your apps and to catch the shortcut in any app. Without it, Writhere would be stuck in its own window.

Why does it ask for Screen Recording?

Only to hear the other side of a call you want transcribed: macOS gates system audio behind this permission. It is optional, nothing is filmed, and no audio ever leaves your Mac.

€49 forever — what's the catch?

There isn't one. The AI runs on your device, so there's no ongoing cost on our side to pass on to you. One payment, yours to keep.

Is my voice really private?

Yes. Everything is processed locally. Your audio and text never leave your machine — there's no server to send them to.

What happens when I switch computers?

Your license covers every device you own. Install Writhere on the new one and you're set — no account, nothing to migrate from the cloud.

Yes — improvements land as free updates, so the app you own keeps getting better at no extra cost.

July 21, 2026

Voice Dictation for Developers: Does It Work in VS Code, Cursor, and Terminal?

Dictation gets pitched at writers and email-heavy jobs, and developers tend to assume it's not for them — code has syntax, terminals have exact commands, and most dictation tools are built for prose. In practice, a lot of a developer's typing isn't code at all.

Quick answer

Writhere works in any text field, including VS Code, Cursor, and Terminal — because it types into whatever app currently has focus, the same way a keyboard does. It's most useful for the prose parts of a dev's day: commit messages, comments, PR descriptions, and prompts to an AI pair programmer.

Where it actually helps

— Commit messages. Dictate the "why" behind a change faster than typing a full sentence.
— Code comments. Explaining a non-obvious workaround in a docstring is prose, not syntax.
— Prompts to AI tools. Cursor, Claude Code, and similar tools take natural-language prompts — exactly what dictation is good at.
— PR descriptions and issue write-ups. Longer-form explanation is where typing speed matters most, and where dictation saves the most time.

Where it doesn't help (and shouldn't try to)

Nobody should dictate exact syntax character by character — that's what a keyboard and autocomplete are for. Dictation is for the English sentences woven through a developer's day, not for replacing typing code itself.

Why on-device matters here specifically

A lot of what developers dictate — commit messages about a security fix, comments referencing internal systems, prompts describing proprietary logic — is exactly the kind of text you don't want routed through a third-party server. On-device processing means none of it leaves the machine to become text.