Support
Something broken? Something missing?
Support lives inside the app — one form, one path, routed directly to the people who build VocaPulse. This page explains how to use it and what helps us fix things quickly.
Before you send
Most problems have a published answer.
- Troubleshooting — startup failures, auto-paste issues, Bluetooth cutouts.
- Permissions — the common case is a missing
inputgroup membership. - Changelog — check if the version you are running has known issues that are fixed upstream.
Send a report from the app
Open VocaPulse and go to Settings → Support. Sign in first if the app prompts you — reports are attached to your account so we can follow up. Pick Bug report or Feature request, write a short summary, then describe what happened or what you'd like.
The app attaches a small, fixed set of diagnostics automatically — app version, OS, and your account and device identifiers. No audio, no transcripts, no file paths, no environment variables. What you type is what we see.
What helps us fix things fast
A good bug report answers three questions.
- What did you do? The exact steps — hotkeys pressed, app in focus, settings changed. If you can reproduce the bug, list the steps in order.
- What did you expect? One sentence is enough. “Text should paste into the editor,” for example.
- What happened instead? Observable behavior only — “nothing pasted, the pill turned green and then disappeared” beats “it doesn't work.”
Include your distribution (Fedora 43, Arch, Ubuntu 24.04, …) and your Wayland compositor (KDE Plasma, GNOME, Hyprland, …) if the problem is audio, paste, or overlay related.
Feature requests
Pick Feature requestin the same form. One idea per report, with a sentence on the problem you're trying to solve. Small, concrete requests are easier to act on than big, abstract ones.
Privacy
Reports are stored in our private issue tracker. The only personal data attached is your opaque account and device id — enough to reply, not enough to link to your email in a dump. When you delete your account, report bodies are rewritten to remove the identifying link. The text of the report itself stays, because fixing the bug is why it was sent. Full details live in the Datenschutzerklärung.
Can't reach the in-app form?
If the app won't start at all, the troubleshooting section covers the failure modes we see most often. A dedicated community channel is in the works — the link will land in the footer when it's open.