Typeless’s Windows release notes for September 16, 2026 announced mouse-button shortcuts in version 2.7.0. The entry lists side buttons and middle click as triggers for Dictate, Translate and Ask anything. For a Windows user whose hand is already on the mouse, this offers another way to start voice input. The practical decision is whether one binding fits your existing workflow.
This is an analysis of the official announcement, checked September 27, 2026; we have not tested the feature, and the exercise below is a proposed evaluation, not an observed result.
Choose one operation and one button
Pick a task you repeat, such as adding a paragraph to a document. Decide which operation you want before assigning a trigger: dictation, translation and asking for an answer produce different kinds of output. The exercise below is for dictation into an editable draft.
Check that the feature is present in your installed Windows app and account. The announcement does not specify plan or regional restrictions, or establish compatibility with every mouse and application.
Before changing a button, check its current job in your browser, document app and mouse software. Record its assignment and keep your existing input method available. The vendor describes opening Settings, using Add another under Shortcuts, then pressing the desired mouse button. If those controls are absent, check current vendor help before changing your setup.
Try a disposable draft
Use a blank document or unsent practice draft, away from a live submission form. Check microphone access and locate the documented stop and cancel controls before recording. Avoid capturing anyone else’s conversation.
Use this fictional input:
Project Cedar review is on October 6, 2026. Please confirm the agenda by October 2, 2026. Do not send this draft.
The project and dates are invented practice data. Your review target is an editable draft preserving the name, both complete dates and the request. A spoken “do not send” is not a control that prevents submission.
Click the intended field, confirm the insertion point, activate the binding and check which operation starts before speaking. Finish with the documented control, then inspect the result. In a second disposable draft, test the documented cancel path. Record each check as pass, fail or not tested.
Five checks before keeping the binding
| Check | Keep criterion | If it fails |
|---|---|---|
| Trigger | The intended operation starts. | Review the binding; stop if uncertain. |
| Existing button action | No essential action is lost. | Choose another button or keep the old input method. |
| Destination | Text reaches the intended disposable field. | Stop; inspect focus before another dummy-text attempt. |
| Meaning | Names, dates and the request remain correct. | Correct the draft and investigate before relying on it. |
| Recovery | You can stop and restore the previous setup. | Revert until the control path is clear. |
If the result lands in the wrong field, stop and undo or discard only the disposable content you created. If behavior remains unclear, restore your previous binding through documented controls. For vendor support, record the app version, mouse model, target application and non-sensitive reproduction steps.
These checks help you decide whether the trigger behaves predictably in your chosen app. They are not a speed, accuracy or accessibility benchmark. Keep the binding only when the destination and recovery checks are clear.
Put the announcement in context
For a broader comparison of outcomes and controls, read Voice AI vs Dictation. The glossary explains dictation and voice AI.
This article does not announce mouse shortcuts in Cue or imply that Cue and Typeless share the same capabilities.