Cue learning paths

Put your voice and context to work

Start with the task you need to finish, not a model name. These guides show what to bring, what to ask Cue, and how to check the result before you use it.

Write by voice

Use Dictation when you already know what you want to say. Speak a rough draft into a focused text field, then review names, numbers and commitments. Dictation is not the same as asking an Agent to act.

Dictate your first useful draft

Start withA focused text field and a short message you can check.

Work towardA reviewed draft, with a recovery path if text lands in the wrong place.

Turn conversations into useful context

A transcript is source material, not a decision log. Start with notes or a recording you are allowed to use. Correct the relevant excerpt, separate facts from suggestions, and carry only the necessary context into the next task.

Extract actions from meeting notes

Start withA reviewed meeting excerpt with decisions and open questions.

Work towardAn action table whose owners and deadlines are supported by the source.

Track What Changed Between Meetings with Cue

Start withTwo reviewed meeting excerpts, their dates, a known approval rule, and configured Cue Agent.

Work towarda source-linked decision change log and a checklist of affected actions to inspect.

Give an Agent a task it can verify

For analysis or action, use an Agent with an explicit goal, selected context, constraints and a way to verify success. Bringing an Agent into your current app does not mean it can see every file or act without the required permissions.

Complete your first bounded Agent task

Start withOne clear goal and the smallest useful piece of app context.

Work towardA result you can inspect against acceptance checks before taking the next step.

Prepare context for Claude Code or Codex

Start withA task brief, relevant evidence and access to your chosen coding Agent.

Work towardAn explicit handoff, with connection, context and execution checked separately.

Describe a reproducible bug by voice

Start withSteps, expected behavior, observed behavior and non-sensitive evidence.

Work towardA bug report another person or Agent can reproduce, not an assumed diagnosis.

Finish a small task from selected context

Start withA passage already open in the app you are working in, and one small output you need from it.

Work towardA checked result whose source you proved, plus a clear boundary for actions that leave your machine.

Combine the guides into a real workflow

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.

Before you start

  • Check shortcuts, microphone access and any required app permissions in your installed Cue version. If automatic context capture is unavailable, explicitly paste a reviewed excerpt you are permitted to share.
  • Recording an ongoing meeting and dictating a recap after it ends are different workflows. Get any required recording consent, and check names, dates and speaker attribution before reusing the transcript.
  • Cue model selection and external Agent access are separate. A listed model or a Claude, Codex or Gemini option does not prove that the corresponding connection, account or task execution is ready. Do not assume Agents share history or permissions.
  • Practice examples are illustrative learning material, not recorded Cue runs or speed benchmarks. Start with non-sensitive material, inspect the output, and confirm before sending, publishing or changing files.

Capture tools and reusable evaluation resources

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.