Dictate Your First Useful Draft
BringA focused text field and a short message to check
MakeA reviewed draft, plus steps to fix misdirected text
Cue learning paths
Set up Cue, try a practical exercise and learn what to do when a step needs attention
Use Dictation when you know what to say: speak into a focused field, then review the draft
BringA focused text field and a short message to check
MakeA reviewed draft, plus steps to fix misdirected text
BringThe recipient, agreed facts and clear next steps
MakeA draft email to review before sending, without invented promises
BringCompleted work, blockers, next steps and open requests
MakeA concise update separating completed items from ongoing work
BringTechnical notes with names, identifiers and numbers to preserve
MakeA verified brief with exact terms and open questions
BringConfigured Cue Dictation, an editable field, ticket facts and rules
MakeA grounded support draft and checklist without unapproved promises
BringThree sample screen notes, review rules and spoken feedback
MakeNine located feedback items separating requirements, preferences and open checks
Start from notes or recordings you may use, keeping sources and separating decisions from suggestions
BringA reviewed meeting excerpt with decisions and open questions
MakeAn action table with source-backed owners and due dates
BringPermitted interview notes and selected, corrected excerpts
MakeA requirements draft that separates evidence, proposals and unknowns
BringA permitted recording, source playback and a clear task
MakeA focused context brief with source links and open questions
BringReviewed meeting notes, an agenda goal and time limits
MakeA timed agenda draft, pre-read checklist and open questions
BringTwo reviewed meeting excerpts, dates, rules and Cue Agent
MakeA source-linked change log and checklist of affected actions
Give Agent a goal, the material and a way to check the result (connections and permissions decide its reach)
BringOne clear goal and minimal relevant app context
MakeA verifiable result to inspect before taking next steps
BringA task brief, relevant evidence and coding Agent access
MakeA structured handoff checking connection, context and execution separately
BringRepro steps, expected and actual behavior, and non-sensitive evidence
MakeA clear bug report another person or Agent can reproduce
BringSource notes with conflicting scope, status or decisions
MakeA brief noting source authority and flagging unresolved conflicts
BringA reproducible bug in an authorized project and Claude Code access
MakeA scoped patch with failing tests before and passing after
BringA specific Git diff, intended behavior and Codex access
MakePrioritized findings with supporting evidence for your next fix
BringA sample practice CSV and Python 3 for validation
MakeA verified subtotal showing included, excluded and unresolved rows
BringCue Dictation, scratch notes and authorized task evidence
MakeA recovery brief keeping completed work while retrying remaining steps
BringSelected text in your active app and the needed output
MakeA source-backed result to review, with boundaries for actions outside your device
BringA sample docs folder, reference key and read-only request
MakeA report separating missed defects, false positives and unchecked links
BringA small reviewed diff and verification records
MakeRelease notes, an evidence table and verified claims for practice
New to Cue? Pick one task from these guides and try it with non-sensitive material. Cue is free to start. No payment method required. Check the result before deciding whether a paid plan fits your work.
Download Cue free · See plans and how to upgrade
Upgrades start inside the Cue desktop app, not on this page. Check your account's current options and limits; external Agent access is separate.
Do not pass the entire conversation along by default. At each handoff, keep the evidence needed for the next task and retain a link or source identifier so the result can be checked.
Extract actions and leave missing owners or dates explicitly unassigned.
Use those checked facts to describe progress and blockers.
Draft a follow-up with one clear request; review it before sending.
Turn a small interview excerpt into evidence-linked requirements.
Resolve disagreements with approved scope before assigning work.
Give an Agent one bounded task and explicit acceptance checks.
Capture the reproduction steps while the relevant app is in front of you.
Prepare the brief and explicitly supply it to the connected coding Agent.
Compare the proposed fix and test evidence with your original report. A generated patch is not proof that a bug is fixed.
Choose the capture workflow first, then evaluate the result. These additional resources are currently in English.
Use the benchmark methodology and linked public resources to define useful checks. A framework for evaluation is not a claim that Cue outperforms other products.