What is not built yet.
Four things are ahead of us, in the order we are working on them. Everything under them has already shipped and is in the app you can download today.
Direction, not a contract. The order moves; the refusals at the bottom do not.
Cue on your phone
The Cue keyboard and the iOS companion are on the App Store, and still moving fast. The keyboard dictates into any app on the phone; the companion is where you review what Cue captured and where a recording actually happens, because iOS gives a keyboard no microphone.
- Dictation into any iOS app, from the keyboard
- A companion that records the room you are standing in
- One account across your Mac and your phone
Automations on a schedule
Saved routines already run today, started by you. The new part is the trigger: a morning digest of what needs a reply, a Friday summary drafted before you ask for it. Every run still stops at a draft.
- Scheduled and recurring runs
- A confirm gate on anything that would act
- The same run log, halting on the first error
Per-connection activity
Cue promises to read from a connected account and never to write to one without your yes. This is the screen that makes that auditable rather than asserted: what was read, when, and for which ask, per connection, with the scope spelled out and a revoke button on the same view.
- What was read, when, and for which ask
- Per-connection scope, written out in full
- Revoke from the activity view itself
Cue beyond the Mac
The browser demo taught us that people want Cue where the Mac app is not. An extension that brings dictation and one-tap replies to any tab, on the same account, is the obvious answer. It is on this page as a question rather than a promise.
- Dictation and replies in any tab
- The same voice, and the same refusal to send
- Shaped by what demo users actually ask for
The part you can go and try.
None of this is coming soon. It is in the build on the download page, which is the only claim on this page you can check for yourself in the next ten minutes.
- 01
Connected accounts
11 accounts you can link from the app or the web, with the tokens held for you rather than by the app, and web search and browsing on every session with nothing to connect.
- 02
Asks that reach your tools
When am I free Thursday checks the real calendar, and a reply about a date reads the thread first. Reads run on their own; anything that writes waits for you.
- 03
Meetings, recorded and written up
Two tracks clocked together, transcribed while the meeting runs, and a write-up in the template you picked. The audio is deleted the moment the transcript exists.
- 04
Acting in your apps (beta)
Cue can operate the apps in front of you when you ask. Off until you turn it on, a confirm before every step, and deleting and archiving blocked outright. Beta: it works app by app and cannot reach inside a browser tab.
- 05
Hiding from screen sharing
Cue's own windows kept out of what you are sharing, so the room sees your deck and nothing else. Max plan, off until you turn it on.
- 06
Your usage, in the open
Twelve months of history inside the app, broken out by draft, dictation, ask, meeting, workflow, command, counted off the same meter billing reads.
The four we will not build.
A roadmap is also a list of refusals. These are not behind, delayed, or under review. They are out, and they are out by architecture rather than by policy.
Auto-send
No roadmap item will ever press send for you. Not the ones shipping this quarter, and not the ones after them.
Write scopes by default
Connections ask to read. Anything that acts on your behalf is opt-in, gated, and confirmed for that particular run.
Storing your content
Drafts, screens, and messages stay on your Mac. Growth here never comes from warehousing your words.
Destructive actions
Acting in your apps can click and type. It cannot delete, remove, or archive: that is blocked in the app, not discouraged in a prompt.
Tell us what is missing.
The order above moves when somebody makes a case for it. Make yours.