Explain the change in a coding assistant’s chat field
In Cursor, Codex or another tool with a compatible prompt field, explain the current behaviour, the expected result and the constraints. Paste exact paths, identifiers, logs and code separately, then review the combined request.
Example: “The account menu stays open after I click outside it. Find the handler and make the smallest change that closes it. Keep the keyboard shortcut behaviour unchanged. Explain the change before editing.” This is an illustrative prompt, not an app integration or automatic authorisation.
Draft a bug report that another person can follow
State what you were doing, the steps that led to the problem, what happened and what should have happened. Add version details and the exact error after dictation. A short ordered report is easier to investigate than a stream of guesses.
Write review comments and project notes
Dictate why a change matters, the concrete behaviour it affects and the suggested next step. For a review comment, attach the relevant line or code through your normal development tool. Whispek does not know which repository or file you mean unless you include that information in a request.
For a handover, capture the current state, unresolved question and next action. Review any dates, owners and decisions before saving it to your project.
Keep identifiers and syntax under your control
Personal dictionary entries can help you manage recurring project names and technical vocabulary. They do not guarantee verbatim code syntax, punctuation, casing or paths.
Use dictation for explanatory prose. Insert exact code from its source, then inspect the completed text. Choose a prompt or notes field rather than a terminal where unexpected text could be interpreted as a command.
Recover a draft that did not reach the intended field
Confirm that the intended prompt or editor field is focused and accepts normal text. Start recording with the shortcut displayed in Whispek, speak and stop. If automatic insertion is unsuitable, copy the available result and paste it into the right field.
Whispek does not tag IDE files, edit repositories, run commands or send a request to another coding service automatically. Those actions and permissions belong to the tool you choose.
Use core tools free, with a weekly allowance
Free includes voice input, text cleanup, a personal dictionary, local history and the separate Whispek AI assistant. Plus and Pro increase weekly use. Your account shows remaining allowance and the next refresh.
Recognition and AI processing require an internet connection. Only submit project material you are allowed to process through these cloud features. Local history is not an offline recognition mode.