Your Cue.
Your Chrome.
Cue can research, navigate, and fill forms in the browser where you’re already signed in, when you ask it to.
Chrome Web Store availability: coming soon. The public listing is not available yet. Existing early-access users can continue using their Cue-provided extension. We’ll link the verified store listing here once it is published.
Connect your browser
- Enable the Cue extension in Chrome on your computer.
- Open your Cue instance in the same Chrome profile and sign in. Signing in to the Cue desktop app does not sign you in to Chrome.
- Open Cue from Chrome’s Extensions menu. Check that its instance URL matches the Cue you’re chatting with, then choose Connect.
- Wait until the popup says Connected. Ask Cue to use your Chrome browser.
Enabled, but Cue can’t reach it?
Enabled means Chrome allows the extension to run; Connected means it has a live link to your assistant. Open the popup to see the actual connection status. If it asks you to sign in, open your Cue instance in Chrome and reconnect. If you use multiple Chrome profiles or Cue instances, check both.
A refreshed extension reuses its limited pairing credential during reconnects until expiry. Once it expires, sign in and reconnect. A stalled connection automatically retries. Choose Disconnect to stop browser access.
Chrome’s internal settings pages and the Chrome Web Store restrict extension control. Test on an ordinary website. Another debugging extension or open developer tools can also interfere with a tab.
What the extension accesses
At your assistant’s request, the extension can read tab information and page content, capture page screenshots, and act on websites through Chrome’s debugging API. Results go to your connected Cue instance and may be processed by the AI providers configured for it. Depending on the pages you ask Cue to use, this content can include personal identifiers, health information, financial and payment information, authentication information, personal communications, and location information. Access is limited to what is needed for the requested browser task.
For remote pairing, it reads the signed-in session from your matching Cue tab and exchanges it at that instance over HTTPS for a limited relay credential. It stores that limited credential and its expiry locally; it does not persist the original sign-in token. Optional feedback includes diagnostic information and recent operations, which may include browsing information.
Review Cue’s privacy policy and contact support for help. Requires Chrome 120 or later on a desktop computer; unavailable in Chrome on iPhone.