Connected accounts, asks that reach your tools, and the iPhone keyboard have all landed. What follows is what we’re building next, in the order we’re building it.
Calendar, mail, docs and chat link to Cue from the Integrations pane in the app or from your account on the web. Tokens are custodied server-side so the app never holds one, and any connection can be cut from either place.
“When am I free Thursday?” checks your actual calendar. A reply about a delivery date reads the thread before it drafts. Reads run on their own; anything that writes or sends stops at a confirm card and waits for you.
The iOS companion and the Cue keyboard. Dictate and draft in your voice inside any app on iPhone, in the same voices your Mac learned, kept in sync through the same account.
The account dashboard shows what you have spent this cycle against what your plan allows. Metering happens on every model call, so the number is the same one billing reads.
The multi-step runs Cue already does on demand, now on triggers: a morning digest of what needs a reply, a Friday summary drafted before you ask. Every run still stops at a draft.
A record of what Cue actually read, per connection, so the read-only promise is auditable rather than asserted. Scope and history in one view, on the web and in the app.
The browser demo taught us people want Cue where the Mac app isn't. We're exploring an extension that brings dictation and one-tap replies to any tab, backed by the same account.
A roadmap is also a list of refusals. These aren’t behind, delayed, or under review. They’re out, by architecture.
No roadmap item will ever press send for you. There is no code path for it, and there won't be.
Connectors ask to read. Anything that acts on your behalf is opt-in, gated, and confirmed per run.
Drafts, screens, and messages stay on your Mac. Growth never comes from warehousing your words.
The order above moves when users make a case. Make yours.