Permissions

Wisspa asks for four macOS permissions. Each one maps to a specific job — here's exactly what, why, and how to fix it when something's off. Every one of these is also listed live in the app under Settings → About, with buttons that deep-link into the right System Settings pane.

Microphone

Why: captures your voice while you hold a hotkey. Audio is buffered only during the press and discarded after the transcription request completes.

When you're asked: during onboarding, or the first time you dictate.

Re-grant: System Settings → Privacy & Security → Microphone → enable Wisspa.

Accessibility

Why: Wisspa pastes by simulating Cmd+V into whatever app has focus. macOS only allows synthetic keystrokes from apps with Accessibility access. Without it, dictation transcribes fine but nothing pastes — the single most common setup issue.

When you're asked: the first time Wisspa tries to insert text.

Re-grant: System Settings → Privacy & Security → Accessibility → enable Wisspa.

Screen Recording (optional)

Why: only the screenshot and save screenshot voice actions need it — macOS gates screen capture APIs behind this permission. Dictation, prompting, and every other action work without it.

When you're asked: when you first run a screenshot action, or from the onboarding step.

Re-grant: System Settings → Privacy & Security → Screen Recording → enable Wisspa.

Automation (System Events)

Why: two jobs — detecting the frontmost app (so dictation tone and prompt format adapt to where you're working), and dispatching the Cmd+V keystroke via System Events. Also used by AppleScript actions like "mute audio".

When you're asked: the first time Wisspa detects the focused app or pastes. macOS shows a "Wisspa wants to control System Events" prompt — click OK.

Re-grant: System Settings → Privacy & Security → Automation → enable the entries under Wisspa.

If grants go stale

macOS ties permissions to the app's code signature. Two situations reset them:

• After a TCC reset or macOS upgrade — re-open the app and grant as prompted.
• Unsigned builds (dev builds you compile yourself) — each new binary can be treated as a new app, so you'll re-grant on update. Signed release builds keep their grants across updates.

Nuclear option when the panes get confused — quit Wisspa, then:

tccutil reset All com.techguider.wisspa

Relaunch and grant fresh. Your settings, history, and API keys are untouched — this only resets the permission grants.