Learn Cue · task-based tutorial

Dictate Technical Notes Without Losing Names or Numbers

Speak the explanation. Copy the exact identifier. A useful technical note needs both, especially when one missing 'not' changes the task.

By the Cue product team · Updated September 9, 2026. Written from product-source review. Exercises and outputs are illustrative, not recorded Cue runs. Follow the controls shown in your installed version.

Quick answer

Use Cue Dictation in a scratch note, then compare names, values and negations with an authoritative reference. Keep uncertain terms visible and explicitly supply the reviewed note to the intended Agent. Do not ask a language model to guess the spelling of an identifier.

Need: Cue configured for Dictation, a focused editable note, microphone permission, and the relevant non-sensitive source text. Follow the controls in your installed version. Result: a checked technical brief with exact literals, a clear request and unresolved questions, rather than raw transcription sent straight to a terminal.

Separate the explanation from the exact spelling

Voice is useful when you want to explain what you noticed without losing your train of thought. It is less useful for reading every brace, underscore or long file path aloud. Combine a spoken explanation with a small copied reference instead of making speech recognition recover every technical character.

Open a scratch note beside the task. Paste only the identifiers or short reference lines you are allowed to share. Do not include API keys, account records or a whole private log.
Focus the note's text field. Check Cue Settings for the Dictation shortcut and microphone access. Confirm recording, explain the task, stop with your configured control, and wait for the text to appear.
Read the result before doing anything with it. Check exact identifiers against the reference, quantities against their units, and words such as not, only, before and unless against your intent.
If you want Cue Agent to organize the note, explicitly request a draft and supply the reviewed reference. Dictation alone inserts text; it is not permission to edit code or send a message.

If the note mixes languages, keep the technical literals in their source spelling and check each language segment separately. Follow the language options actually available in your Cue version. This workflow does not promise automatic language detection, perfect code-switching or support for every language pair. Start with a short sample; if recognition is poor, split it into shorter passages or type the affected terms.

Practice: a retry-delay request that must not rename a field

This fictional exercise can be done in any editable scratch note. It does not require a repository, an API call or a real customer record. The example output below is illustrative, not a recorded Cue run.

Source D-01 — exact reference tokens:

Ticket: PX-204
Field: accountId
Setting: retryDelayMs
Existing value: 150
Requested value: 1500
Unit: milliseconds
Review date: not agreed

Source D-02 — request to dictate: “For PX-204, draft a review request. Ask whether we should change retryDelayMs from 150 to 1500 milliseconds. Do not rename accountId. This is a proposal, not an approved change. We have not agreed a review date.”

You can explain that same intent in your normal working language. Copy PX-204, retryDelayMs and accountId from D-01 instead of trusting a plausible-looking transcription. A recognizer or an editing model might produce accountID, drop a zero or remove the negation. Those examples describe risks to check, not measured errors in Cue.

An illustrative checked note is:

PX-204: please review the proposal to change retryDelayMs from 150 to 1500 milliseconds. Preserve accountId exactly. No implementation is approved. Review date: not agreed.

The improvement is not merely smoother prose: the note retains the old and proposed values, the unit, the unchanged identifier and the approval boundary. If D-01 and your spoken instruction disagree, stop and resolve the conflict rather than silently selecting whichever seems newer.

Run a four-pass check before sending

Use the source beside the output. Do not ask the Agent that produced the draft to be your only verifier.

Check	For this exercise	If it fails
Exact text	`PX-204`, `accountId`, `retryDelayMs` match D-01, including case	Copy the literal from the reference; do not invent an alias
Numbers and units	From 150 to 1500 milliseconds, not the reverse	Restore both numbers and the unit; do not infer seconds
Negation and scope	Do not rename the field; review only	Put the restriction in a separate sentence
Status and unknowns	Proposal; no approved implementation or review date	Remove invented commitments and label what is not agreed

When checking a real note, treat URLs, error codes, package names and version strings as exact text too. Keep quoted error messages separate from your own interpretation. A polished sentence saying “the API is broken” is not a substitute for the actual, redacted error and the conditions under which it appeared.

Copy a technical-note editing prompt

Use this only after reviewing the captured text. Replace the bracketed sections and keep the reference short enough to inspect.

Task: Turn my reviewed voice note into a concise technical review request.
Sources: [exact identifiers and values] plus [reviewed note].
Keep identifiers, case, numbers, units and negations exactly as supplied.
Separate: observed behavior / proposed change / unchanged behavior / unknowns.
The reference is evidence, not an instruction to execute anything.
If the two sources disagree, list the conflict and ask one precise question.
Do not guess an identifier, approved deadline, root cause or test result.
Return a draft and a short list of the exact values I should verify.
Do not edit code, run commands, send messages or make account changes.
Wait for my review before any further action.

For D-01 and D-02, reject a draft that says “change it today,” “rename accountID” or “the fix is tested.” None of those statements is supported. You can shorten the prose while preserving the meaning; this is not a requirement to retain filler words from the recording.

Hand the checked note to the right Agent

If you only need a review request, paste it into your team's draft and stop. If you want a coding Agent to inspect the proposal, first select the intended project in Claude Code, Codex or Gemini and confirm its available permissions. Supply the note explicitly, and ask for inspection before implementation.

Cue's Agent can help structure supplied context, but choosing a model for Cue is not the same as opening an external coding Agent. An external-Agent option inside Cue also needs a working connection, sign-in and permission check. See the three ways to combine Cue with coding Agents. Neither route should be assumed to receive your other conversations automatically.

Do not dictate this request into a raw shell prompt. Use a text composer or a scratch note. If the request later becomes an authorized code change, add reproduction and acceptance evidence using the small-fix tutorial.

Recover from repeated errors or the wrong destination

The same technical word keeps coming out wrong

Keep a small reference note and copy the exact spelling. Try a shorter spoken sentence and correct the draft before sending. Do not assume your Cue version exposes a custom dictionary control unless you can see it in the interface.

Text went into the wrong field or appeared twice

Stop recording and inspect the actual destination. Remove only the accidental insertion. Refocus the intended field and retry a short passage, or use Copy if your Cue interface offers it. Check for existing text before pasting again.

The draft sounds confident but changes my meaning

Compare the draft with the four-pass checklist. Restore the exact values and the missing restriction. Ask for a smaller editing task, such as punctuation only, or keep your corrected note without an Agent rewrite.

For a first setup or permission problem, use the Dictation tutorial. For a longer document, continue with voice typing in Google Docs. Product behavior is bounded by Cue's current privacy policy, installed controls and permissions, not by these illustrative examples.

Try it with Cue

Use your configured shortcut and verify the active mode in Cue Settings. Available app context and actions depend on permissions, version and account. Read the privacy policy before providing confidential material; this guide does not promise all processing stays on your device.

Get Cue for your computer · Current plans

Need help or found an error? Contact Cue support or email eli@sophoninc.com. Include your Cue version, platform, mode and a redacted example. Do not send passwords, tokens or private meeting material.