Report a bug
SpectiX has no crash reporter and no telemetry, because it makes zero network calls — a claim you can verify yourself in four commands. That is the trade, and it cuts both ways: when something breaks on your Mac, nothing anywhere finds out. A bug nobody writes in is a bug that stays.
What to put in it
The first two turn “it doesn't work” into something that can be reproduced, which is most of the way to a fix. The rest take ten seconds each.
- What happened, and what you expected instead.
- How to make it happen again. Even “it shows up after an hour or so” helps, as long as it says what you were doing at the time.
- The SpectiX version — Settings → About, at the foot of the settings window.
- Your macOS version — Apple menu → About This Mac.
- Which terminal or editor the session was in — Terminal, iTerm2, WezTerm, Ghostty, VS Code, Cursor, Windsurf, and so on. Most detection bugs turn out to be specific to one host.
- A screenshot, if you can see the problem. A row in the wrong state says more as a picture than as a sentence.
Send it
That button opens your own mail app with those headings already typed in. Nothing is sent until you press send, and the button is an ordinary mailto: link — neither the app nor this page carries the message. Prefer to write it yourself? The address is taskbeaconlab@gmail.com.
An idea rather than a bug
Same address, same button. A rough edge, a host that is not detected, a setting you went looking for and could not find — all of it is worth sending. Say what you were trying to do, not just what you would like added; the first is what makes the second solvable.
Mail is read by the person who builds SpectiX. It contains exactly what you type into it — there is no hidden diagnostic attachment, because the app has nothing to attach and no way to send it. What this website itself collects is set out on the privacy page.