Explain the problem while it's clear in your head.
The reproduction steps, the constraint, the reason the obvious fix won't work. Speak them into the app you're using, then keep the useful context in Cue notes for the next time you pick up the problem.
The upload works. The preview doesn’t.
Reproduction
Upload a second file in the same session. The preview stays empty.
Where to look next
Check how the preview updates after upload.
From a thought
to the next step.
Capture what matters. Keep the context. Put it to work when you need it.
Talk through the bug.
Use dictation to describe what you expected, what happened, and how to reproduce it. Put the explanation into your issue, coding assistant, or working note, then check the technical details before using it.
Keep the reasoning with the project.
Save constraints, rejected approaches, and open questions in local Markdown. Give yourself a record of the thinking that can be hard to reconstruct from a diff.
Bring your notes to your coding assistant.
Connect a compatible tool through Cue's MCP connection and grant access to your Cue context. Ask it to find relevant project notes before starting the next task. Setup and available actions depend on the client.
Try it on the bug you're working on.
Dictate three things: the expected result, the actual result, and the smallest reproduction you know. Add the exact error text yourself, then use the note as the starting point for an issue or prompt.
Explore agent connectionsThe upload finishes, but the preview stays empty until I reopen the page. It happens with a second file in the same session. Start by checking how the preview updates after upload.
The upload works. The preview doesn’t.
Reproduction
Upload a second file in the same session. The preview stays empty.
Where to look next
Check how the preview updates after upload.
Keep the why with the work.
A few useful
details.
Does Cue replace my coding assistant?
Cue helps you capture explanations and keep project context. You can continue using your chosen coding assistant and connect it to Cue when it supports MCP.
Will dictation get every symbol and identifier right?
Review code names, commands, paths, and punctuation. Voice is useful for explaining intent; exact technical text still needs a check.
What stays on my Mac?
Your notes remain local Markdown files. On-device transcription runs on your Mac. Choosing cloud transcription, summaries, chat, or editing sends the relevant input to a provider. Connected AI tools have their own data practices.
Read the full FAQStart with the explanation you'd give a teammate.
Say what matters. Keep the reasoning available for the next step.
Download for Mac