Useful details#
A good report includes the CueSpec version and build, macOS version, the affected action, the input device if voice is involved, and what happened instead of the expected result. State whether the draft was created, whether a send receipt appeared, and whether the original Codex conversation received the message.
For example: “On Mac 0.3.0 build 20, releasing Fn creates an empty draft with the built-in microphone. Ordinary speech in another recording app works.” This identifies the stage without disclosing your project.
Choose the right evidence#
A cropped screenshot of the error can help. Use an invented sentence to reproduce a speech issue. Do not post login codes, credentials, full private transcripts or unsanitized device logs in a public thread. Diagnostic summaries can contain enough context without the contents of your work.
The documented community entry is CueSpec Discord, and the support contact is service@sparock.ai. This library does not promise a response-time agreement. If sending is uncertain, check the original conversation first so the report distinguishes failed delivery from successful delivery followed by unfinished AI work.