Cue use cases
Practical AI workflows across the apps you already use. One hotkey, one natural request, and the work stays where it belongs.
Collections
Featured
The workflows people reach for first — each one done in under a minute.
Try saying: “Reply to this: thanks for the intro, we are interested — ask if Thursday afternoon works for a thirty-minute call, and CC Anna.” · about 30 second demo in Mail.
Say the context and points you want to make; Cue drafts a reply in the current email field for you to review and send yourself.
Try saying: “Turn these notes into action items with owners, then draft the follow-up email to the team.” · about 45 second demo in Notes.
Point Cue at your raw notes; get owners, deadlines, and a drafted follow-up — before the context evaporates.
Try saying: “Extract the retry logic into its own function, add a max-attempts argument, and update the call sites.” · about 45 second demo in Cursor.
Describe the change like you would to a colleague; Cue edits the code in your editor and explains what it touched.
All use cases
Try saying: “Reply to this: thanks for the intro, we are interested — ask if Thursday afternoon works for a thirty-minute call, and CC Anna.” · about 30 second demo in Mail.
Say the context and points you want to make; Cue drafts a reply in the current email field for you to review and send yourself.
Try saying: “Turn these notes into action items with owners, then draft the follow-up email to the team.” · about 45 second demo in Notes.
Point Cue at your raw notes; get owners, deadlines, and a drafted follow-up — before the context evaporates.
Try saying: “Extract the retry logic into its own function, add a max-attempts argument, and update the call sites.” · about 45 second demo in Cursor.
Describe the change like you would to a colleague; Cue edits the code in your editor and explains what it touched.
Try saying: “Polish this — keep my meaning, make it tighter.” · about 20 second demo in Notes.
Select any rough sentence and have it rewritten in place — same meaning, cleaner writing, no copy-paste round trip.
Try saying: “Translate this to English and keep the tone.” · about 20 second demo in Safari.
Turn selected text into another language in place — replies, docs, or messages — without opening a translator tab.
Try saying: “Turn this into a structured page: we should launch a beta waitlist — perks for early users, a simple signup form, and a three-email drip. Draft the sections.” · about 40 second demo in Notion.
Keep a Notion text field focused, speak a messy idea, and get headings, bullets, and next steps as a draft to review.
Try saying: “Write this as a post: we just cut our export time from four minutes to nine seconds — and the fix was one database index.” · about 25 second demo in X.
Say the idea like you would tell a friend; get a post shaped for the platform, ready to review before publishing.
Try saying: “Thanks for the update. Thursday at 2 PM works for me. Please send the agenda beforehand.” · about 20 second demo in Outlook.
Keep the message body focused, use your configured Dictation hotkey, speak, then review the draft text before you decide whether to send it.
Try saying: “Add a short summary of the project update, then leave a blank line for the next section.” · about 20 second demo in Google Docs.
Keep the document focused, use your configured Dictation hotkey, speak, then review the text before you continue writing.
Try saying: “Reply: yes to the Tuesday deadline, but the API piece slips to Friday — tag Marco so he sees it.” · about 25 second demo in Slack.
Speak the key points once and get a short Slack reply draft to review before you send it.
Try saying: “Start recording for this meeting — decisions, owners, and follow-ups.” · about 50 second demo in Zoom.
Start the desktop recorder when you choose. Nothing joins the call; during longer meetings, Cue shows a progressive transcript draft and creates structured notes after you stop.
Try saying: “What is actually wrong here, and what is the smallest fix?” · about 35 second demo in Terminal.
Stuck on a stack trace? Ask out loud. Cue reads exactly what is on screen and tells you what broke and where to look.
Try saying: “Set up a client folder for Meridian: contracts, invoices, assets, and notes — with a README that lists the contacts I mention.” · about 40 second demo in Finder.
Ask for the folder structure you need — project scaffolding, doc templates, weekly folders — and watch it appear.
Try saying: “Read this contract and flag anything unusual — liability, termination, auto-renewal, IP. Rank by risk.” · about 45 second demo in Preview.
Open the PDF, ask for the risks. Get a plain-English list of the clauses to question before you sign.
Try saying: “Summarize this: key findings, how they got them, what the limitations are — and whether it applies to consumer apps.” · about 40 second demo in Chrome.
Forty pages, one question: is this worth my time? Get findings, method, and limits in a scannable brief.
Try saying: “Build a comparison table for these three tools: price, seats, API, support, migration effort. Mark the winner per row.” · about 40 second demo in Numbers.
Three vendors, six criteria, one table. Cue reads the tabs and notes you have open and builds the comparison.
Try saying: “Clean this up: fix the dates, remove duplicates, split the name column — then tell me what each column actually contains.” · about 50 second demo in Excel.
Inherited a sheet with merged cells and mystery columns? Have it cleaned, labeled, and explained back to you.
Try saying: “Extract every requirement into a checklist — group by section, and flag the ones we cannot meet today.” · about 45 second demo in Word.
Feed it an RFP or spec; get every requirement as a checkable line, grouped, numbered, with the gaps flagged.
Try saying: “Research how the EU AI Act affects small SaaS companies and save a one-page brief with sources to my notes.” · about 50 second demo in Chrome.
Ask the question once; Cue researches across sources and leaves a cited one-page brief in your notes.
Try saying: “Rename everything here to date first, then a short description — like 2026-07-17-client-invoice. Keep the extensions.” · about 35 second demo in Finder.
Describe the naming scheme in one sentence; every file in the folder falls in line.
Try saying: “Clean up my desktop: screenshots into one folder, documents by topic, and trash the old installer files.” · about 40 second demo in Finder.
A desktop full of screenshots, PDFs, and installers becomes four tidy folders — with a plan you approve before anything moves.
Try saying: “Organize my Downloads: group by type, pull out the duplicates, and archive anything older than six months.” · about 45 second demo in Finder.
Group by type, flag the duplicates, archive the ancient — the folder where files go to disappear becomes findable again.
Try saying: “Turn the visible steps for last month’s invoice report into a checklist. Stop before any export, download, rename, or move action.” · about 50 second demo in Chrome.
Describe the steps visible in the current page and get a checklist with confirmation points before any browser or file action.
Try saying: “Turn these visible video details into a viewing checklist with the chapters I should prioritize.” · about 40 second demo in Chrome.
Use the title and details visible on a video page to draft a viewing checklist while the media stays on its original platform.
Try saying: “Using only the items I selected, draft a morning brief with meeting prep, replies I should write, and unfinished tasks.” · about 40 second demo in Notes.
Bring selected meeting details, email excerpts, and unfinished tasks into one visible note, then draft a brief for review.
Try saying: “Build a presentation about our office move — timeline, floor plan highlights, and an FAQ slide. Dark theme.” · about 50 second demo in Chrome.
Say the topic and the occasion; Cue writes a complete presentation as a web page and opens it ready to present.
Try saying: “Turn these photos into a simple gallery page called Kyoto Weekend — group by day, add short captions.” · about 50 second demo in Finder.
Point at a folder of photos; get a clean gallery page you can send — layout, sections, and captions handled.
Try saying: “Build a one-page site for a pottery workshop: hero with the date, three photo slots, a short about section, and a signup link.” · about 50 second demo in Chrome.
Describe the page like you would brief a freelancer; Cue writes the files and opens the result in your browser.
Try saying: “Turn these notes into a ten-slide outline: problem, evidence, proposal, ask — with one line of speaker notes per slide.” · about 45 second demo in Keynote.
From a page of notes to a deck skeleton — sections, slide titles, and speaker notes — ready to design.
Try a different word — or clear the filters and browse the full library.
Workflow details
Each card above links to its walkthrough below — setup, the exact prompt, what Cue does, and the result.
Say the context and points you want to make; Cue drafts a reply in the current email field for you to review and send yourself.
Set the scene
Open the email you want to answer and place the cursor in its reply field. Include the relevant context and facts in what you say.
Try saying
“Reply to this: thanks for the intro, we are interested — ask if Thursday afternoon works for a thirty-minute call, and CC Anna.”
What happens next
Result
A reply draft based on the context you supplied, ready for you to review, edit, and send.
Point Cue at your raw notes; get owners, deadlines, and a drafted follow-up — before the context evaporates.
Set the scene
Open the note you scribbled during the meeting — fragments are fine. Names and half-sentences are enough to work with.
Try saying
“Turn these notes into action items with owners, then draft the follow-up email to the team.”
What happens next
Result
A clean action list in the note, plus a follow-up draft to the room — sent only when you say so.
Describe the change like you would to a colleague; Cue edits the code in your editor and explains what it touched.
Set the scene
Open a file with a function that has grown too long — in Cursor, VS Code, or your editor of choice. Leave the cursor inside it.
Try saying
“Extract the retry logic into its own function, add a max-attempts argument, and update the call sites.”
What happens next
Result
The refactor applied in your editor, with a short summary of what changed — ready to diff and commit.
Select any rough sentence and have it rewritten in place — same meaning, cleaner writing, no copy-paste round trip.
Set the scene
Open any draft with a clumsy paragraph — an email, a doc, a Notes entry. Select the sentences you want to fix and leave them selected.
Try saying
“Polish this — keep my meaning, make it tighter.”
What happens next
Result
The same paragraph, tightened and typo-free, sitting exactly where the rough one was.
Turn selected text into another language in place — replies, docs, or messages — without opening a translator tab.
Set the scene
Open a page, email, or message in another language — or a reply you drafted that needs to go out in one. Select the text.
Try saying
“Translate this to English and keep the tone.”
What happens next
Result
A natural translation where the original text was — no tab switch, no lost formatting.
Keep a Notion text field focused, speak a messy idea, and get headings, bullets, and next steps as a draft to review.
Set the scene
Open the Notion page where the draft belongs and place the cursor in its text field. Have a real idea you can think out loud for twenty seconds.
Try saying
“Turn this into a structured page: we should launch a beta waitlist — perks for early users, a simple signup form, and a three-email drip. Draft the sections.”
What happens next
Result
A structured draft — overview, sections, next steps — ready for you to verify and edit.
Say the idea like you would tell a friend; get a post shaped for the platform, ready to review before publishing.
Set the scene
Open the compose box on X or LinkedIn. Know the one point you want the post to make.
Try saying
“Write this as a post: we just cut our export time from four minutes to nine seconds — and the fix was one database index.”
What happens next
Result
A publishable draft in the box — hook first, tight, in your voice. You still press Post.
Keep the message body focused, use your configured Dictation hotkey, speak, then review the draft text before you decide whether to send it.
Set the scene
Open Outlook, start a new email or reply, and place the cursor in the message body where you want text to appear.
Try saying
“Thanks for the update. Thursday at 2 PM works for me. Please send the agenda beforehand.”
What happens next
Result
Your spoken text appears in the Outlook draft for you to review and edit.
Keep the document focused, use your configured Dictation hotkey, speak, then review the text before you continue writing.
Set the scene
Open a Google Doc and place the cursor where you want text to appear.
Try saying
“Add a short summary of the project update, then leave a blank line for the next section.”
What happens next
Result
Your spoken text appears in the Google Doc for you to review and edit.
Speak the key points once and get a short Slack reply draft to review before you send it.
Set the scene
Keep the relevant Slack messages visible or include the context in your request, then focus the reply box.
Try saying
“Reply: yes to the Tuesday deadline, but the API piece slips to Friday — tag Marco so he sees it.”
What happens next
Result
A Slack reply draft in the focused box for you to edit and send.
Start the desktop recorder when you choose. Nothing joins the call; during longer meetings, Cue shows a progressive transcript draft and creates structured notes after you stop.
Set the scene
Join the meeting as usual — Zoom, Meet, or an in-person conversation. When you decide to capture it, choose Start in Cue’s desktop recorder; no invite or extra participant is needed.
Try saying
“Start recording for this meeting — decisions, owners, and follow-ups.”
What happens next
Result
A completed transcript and structured note with decisions, owners, and next steps — captured without a bot in the room. Ask Cue to draft a follow-up when you want one.
Stuck on a stack trace? Ask out loud. Cue reads exactly what is on screen and tells you what broke and where to look.
Set the scene
Reproduce the failure so the error is on screen — a stack trace in the terminal, a red overlay in the browser, a failing test.
Try saying
“What is actually wrong here, and what is the smallest fix?”
What happens next
Result
A diagnosis in plain English — cause, file, line, fix — instead of twenty minutes of searching the error text.
Ask for the folder structure you need — project scaffolding, doc templates, weekly folders — and watch it appear.
Set the scene
Open the folder where the new structure should live. Know the shape you want — folders, starter files, naming.
Try saying
“Set up a client folder for Meridian: contracts, invoices, assets, and notes — with a README that lists the contacts I mention.”
What happens next
Result
The whole structure exists — consistent names, starter files filled in — without typing a single mkdir.
Open the PDF, ask for the risks. Get a plain-English list of the clauses to question before you sign.
Set the scene
Open the contract PDF — an NDA, an MSA, a lease. Any document you would otherwise skim and hope for the best.
Try saying
“Read this contract and flag anything unusual — liability, termination, auto-renewal, IP. Rank by risk.”
What happens next
Result
A short memo: what is standard, what is not, what to push back on — with clause numbers to bring to your lawyer.
Forty pages, one question: is this worth my time? Get findings, method, and limits in a scannable brief.
Set the scene
Open the paper — a PDF in the browser or a long report. The denser it is, the better the payoff.
Try saying
“Summarize this: key findings, how they got them, what the limitations are — and whether it applies to consumer apps.”
What happens next
Result
A one-page brief that answers your actual question — with page numbers for anything you want to verify.
Three vendors, six criteria, one table. Cue reads the tabs and notes you have open and builds the comparison.
Set the scene
Gather the raw material on screen — pricing pages, notes, quotes. Open the sheet or doc where the table should go.
Try saying
“Build a comparison table for these three tools: price, seats, API, support, migration effort. Mark the winner per row.”
What happens next
Result
A decision table you can defend in a meeting — criteria down the side, options across, winner marked.
Inherited a sheet with merged cells and mystery columns? Have it cleaned, labeled, and explained back to you.
Set the scene
Open the spreadsheet someone handed you — inconsistent dates, duplicate rows, columns nobody remembers naming.
Try saying
“Clean this up: fix the dates, remove duplicates, split the name column — then tell me what each column actually contains.”
What happens next
Result
A tidy sheet plus a plain-English data dictionary — and a record of exactly what changed.
Feed it an RFP or spec; get every requirement as a checkable line, grouped, numbered, with the gaps flagged.
Set the scene
Open the requirements document — an RFP, a security questionnaire, a spec. The kind with a "shall" in every paragraph.
Try saying
“Extract every requirement into a checklist — group by section, and flag the ones we cannot meet today.”
What happens next
Result
A response checklist the whole team can work through — no requirement silently missed on page 34.
Ask the question once; Cue researches across sources and leaves a cited one-page brief in your notes.
Set the scene
Have a question you would otherwise lose an hour to — a market, a technology choice, a competitor. Open the note where the brief should land.
Try saying
“Research how the EU AI Act affects small SaaS companies and save a one-page brief with sources to my notes.”
What happens next
Result
A one-page brief with linked sources, saved where you will actually find it — instead of nine open tabs.
Describe the naming scheme in one sentence; every file in the folder falls in line.
Set the scene
Open the folder of chaos — screenshots, scans, exports. The kind full of IMG_4032 and final_v2_REAL.
Try saying
“Rename everything here to date first, then a short description — like 2026-07-17-client-invoice. Keep the extensions.”
What happens next
Result
A folder that sorts chronologically and reads like a filing system — in the time it took to describe it.
A desktop full of screenshots, PDFs, and installers becomes four tidy folders — with a plan you approve before anything moves.
Set the scene
A desktop that has become a junk drawer — screenshots, PDFs, installers, three months of it. The messier, the better.
Try saying
“Clean up my desktop: screenshots into one folder, documents by topic, and trash the old installer files.”
What happens next
Result
A desktop with four folders and room to think — and nothing deleted without your say.
Group by type, flag the duplicates, archive the ancient — the folder where files go to disappear becomes findable again.
Set the scene
Open Downloads — duplicates, one-time installers, and files from 2024 welcome.
Try saying
“Organize my Downloads: group by type, pull out the duplicates, and archive anything older than six months.”
What happens next
Result
A Downloads folder you can actually find things in — duplicates flagged, history archived, nothing lost.
Describe the steps visible in the current page and get a checklist with confirmation points before any browser or file action.
Set the scene
Open the page where the chore happens and select or make visible only the steps you want to plan. Sign in yourself if the site requires it.
Try saying
“Turn the visible steps for last month’s invoice report into a checklist. Stop before any export, download, rename, or move action.”
What happens next
Result
A reviewed checklist for the workflow, with consequential browser and file actions left under your control.
Use the title and details visible on a video page to draft a viewing checklist while the media stays on its original platform.
Set the scene
Open a video page and select or make visible the title, description, and chapters you want to use for planning.
Try saying
“Turn these visible video details into a viewing checklist with the chapters I should prioritize.”
What happens next
Result
A study plan for the video, with the media left on its original platform.
Bring selected meeting details, email excerpts, and unfinished tasks into one visible note, then draft a brief for review.
Set the scene
Select or place in the current note the exact meeting details, email excerpts, and unfinished tasks you want included.
Try saying
“Using only the items I selected, draft a morning brief with meeting prep, replies I should write, and unfinished tasks.”
What happens next
Result
A daily-brief draft based only on the items you supplied, ready for you to verify and edit.
Say the topic and the occasion; Cue writes a complete presentation as a web page and opens it ready to present.
Set the scene
Have the topic and the occasion in mind — a pitch, a class, a weekly review. Nothing needs to be open yet.
Try saying
“Build a presentation about our office move — timeline, floor plan highlights, and an FAQ slide. Dark theme.”
What happens next
Result
A presentation running in the browser — arrow keys to present, print to PDF to share.
Point at a folder of photos; get a clean gallery page you can send — layout, sections, and captions handled.
Set the scene
Open the folder with the photos — a trip, an event, a product shoot. A dozen images is plenty.
Try saying
“Turn these photos into a simple gallery page called Kyoto Weekend — group by day, add short captions.”
What happens next
Result
A shareable gallery page built straight from the folder — done before you would have picked a template.
Describe the page like you would brief a freelancer; Cue writes the files and opens the result in your browser.
Set the scene
Have a clear one-liner of what the page is for — a launch teaser, an event invite, a portfolio intro. Nothing needs to be open yet.
Try saying
“Build a one-page site for a pottery workshop: hero with the date, three photo slots, a short about section, and a signup link.”
What happens next
Result
A working page you can iterate on out loud — real files on disk, not a mockup.
From a page of notes to a deck skeleton — sections, slide titles, and speaker notes — ready to design.
Set the scene
Open the notes that need to become a deck — a strategy doc, research findings, a project recap. Open Keynote or PowerPoint alongside.
Try saying
“Turn these notes into a ten-slide outline: problem, evidence, proposal, ask — with one line of speaker notes per slide.”
What happens next
Result
A deck skeleton with a story — you spend your time on design and delivery, not staring at slide one.