Cue · Use Cases · Voice coding in Cursor and desktop editors

Voice coding in Cursor and desktop editors

In Cursor or another supported desktop editor on Mac or Windows, select or show the relevant code and describe the change you want. Review and edit the proposed code before you save it or run tests.

Voice coding can help you describe a change while the relevant code is already in front of you. Editor and text-field behavior varies by current Cue version, and you remain responsible for reviewing the implementation.

3 example scenarios

Refactoring a component

You say: "Draft a version of this component that uses a reducer for the form state"

Cue does: Cue uses the code context you provide to prepare a proposed rewrite. Review the diff and behavior before applying it.

Reading an error

You say: "Explain this stack trace and suggest the next checks"

Cue does: Cue prepares an explanation and possible checks from the visible or selected context. Verify the diagnosis against the source and runtime.

Drafting a utility

You say: "Draft typed debounce and throttle helpers for this project"

Cue does: Cue prepares code for you to review, adapt to the repository conventions, and validate with your own tests.

How Cue does it

Open Cursor or another supported desktop editor on Mac or Windows and select or show the relevant code
Place the text cursor where you want to work, then use Cue to describe the change, explanation, or draft you want
Review and edit the result, then save and run the repository's normal checks yourself

Try Cue

Download for Mac or Windows. Cue is free to start.

Get Cue →

FAQ

Can I use Cue for voice coding in Cursor or VS Code?

Try Cue in Cursor, VS Code, or another desktop editor or text field available on your supported Mac or Windows setup. This page does not promise a dedicated editor integration. Behavior varies, so test your current Cue version with your own editor, permissions, and project.

How do I start a voice coding request?

Use the Cue hotkey configured for your current app version, then describe the change while the relevant code is selected or visible. Check the current product instructions for shortcut details.

Which spoken languages work for voice coding?

Language support can vary by product version and workflow. Test Cue with your own language, technical vocabulary, microphone, and codebase before relying on it.

Should I apply generated code without review?

No. Review the proposed code, adapt it to your repository, and run the same tests and checks you would use for any other code change.

They hear what you said.
Cue sees what you're doing.
And does the thing, in supported apps.