Cuevue Desktop for Mac (Prerelease)

Cuevue Desktop opens your Cuevue workspace in its own Mac app. Your account, spaces and permissions are shared with Cuevue in your browser. Cuesync, which puts files in Finder, is a separate app.

Requirements and installation#

The first Mac release targets Apple Silicon (M1 or later) and macOS 15 Sequoia or later, with a Cuevue account and an internet connection. Intel Macs and Windows are not supported by this candidate.

If Cuevue has supplied you with a private candidate, check its build-specific installation instructions. Before replacing an older build, finish and sync pending work and quit normally. Keep the previous installer until the new build is confirmed. Preserve the app's local data and any separate Cuesync installation.

Open the supplied DMG and drag Cuevue Desktop into Applications.
Open Cuevue Desktop.app from Applications. Keep any separate Cuesync app installed if you use Finder sync.
Follow macOS's normal first-open prompt. If macOS blocks the app or reports a damaged download, contact support with the exact message. Do not disable Gatekeeper or delete your app data to get past it.

Public availability will be listed on the downloads page when Desktop is released. Until then, use the private build provided by Cuevue or continue in your browser.

Use the app's sign-in page for email and password or Google sign-in. Google opens your default browser; complete the account choice and consent there, then allow it to open Cuevue Desktop when prompted.

Use an existing browser passkey#

Native Touch ID sign-in inside the candidate is not available. To use a passkey you already use with Cuevue:

On the Desktop login page, choose Sign in with a passkey. This opens your default browser. The Sign in with your browser (including passkeys) link starts the same handoff.
Sign in in your browser using the usual passkey or account sign-in options.
Check the displayed account. Choose Sign in with another account if it is the wrong one, or Continue as your displayed account to approve.
Click Open Cuevue Desktop and approve your browser's app-opening prompt. Complete this last step within one minute; if it expires, start again from the Desktop login page.

Browser sign-in creates a separate Desktop session. Older email sign-in or password-reset links may need to be requested again afterward. It does not sign your browser out.

If the browser does not open and Desktop reports that sign-in could not start, close any other Cuevue popup windows and try again. If it still fails, contact support.

Return to the Desktop waiting page and cancel before trying again. Keep the app running while completing sign-in; quitting cancels the pending request. A request left waiting for ten minutes expires and needs to be restarted.

If your browser cannot open Cuevue Desktop, check that the app is in Applications and that you allowed the opening prompt. If the app reports that this sign-in option is unavailable or needs an update, contact the prerelease team. Do not share the full sign-in or callback URL when reporting a problem.

Connect Google services#

Signing in with Google and connecting Google services are separate choices. Open Settings → Integrations to connect the Calendar, Drive, Gmail or YouTube options available to your account and role.

Consent opens in your browser. Check the Google account and requested service permissions, finish consent, and allow the return to Desktop. Verify that the expected account appears as connected in Settings. If you cancel or the return expires, start the connection again from Settings.

Connecting Google Drive here does not install Cuesync or enable Finder sync. For Finder access, follow the Cuesync guide.

Closing, quitting and unfinished work#

The red window close button hides Cuevue Desktop. Click its Dock icon to bring the window back. Hiding keeps the app running, but backgrounding can pause a recording; check the recorder's status when you return.

Cuevue → Quit Cuevue or Command-Q quits the app. Quit, reload and update restart ask for confirmation. Finish recordings, complete uploads and wait for changes to sync before continuing. Choose Cancel to keep working. A page may show an additional unsaved-work warning after the app's confirmation.

These prompts cannot guarantee that every unfinished change has been detected. Force Quit, a crash or power loss can interrupt work, and closing a panel or moving to another page may not trigger the same warning. Keep unsent voice notes and other drafts open until saved or submitted.

An upload marked Uploaded · not attached still needs to be assigned through its creation dialog. If that dialog is no longer available, use that entry's Discard action and drop the original file again. Discarding an unattached upload does not delete your original file from your Mac.

Microphone and camera permissions#

macOS asks for microphone or camera access when you first use a feature that needs it. Allow the requested device to record. For details on recording controls, see Editing, Clips & Recording.

If you denied access:

Open System Settings → Privacy & Security.
Open Microphone or Camera and enable Cuevue Desktop.
Return to Cuevue and retry. If macOS asks you to quit and reopen the app, finish or save other work first.

If the app is not listed, try starting the relevant recording feature once to request access. A busy or missing device is a separate problem: check the selected input and close another app using it. Contact support if access still fails.

Connection problems and recovery#

Cuevue Desktop loads the online Cuevue service. If it cannot connect, check your internet connection and choose Retry Cuevue on the recovery page. A saved-on-device message means a change is waiting locally; wait for server sync before assuming another device can see it.

Recovery keeps your local profile, but cannot restore work that existed only in memory. Do not clear app data or reinstall as a first troubleshooting step while changes or recordings are pending. Report the issue so support can help preserve that work.

Updates#

Use Cuevue → Check for Updates… in a release-configured build. An available update asks before downloading, then offers Later or Restart and Install. Choose Later while recording, uploading or editing; return to Check for Updates when you are ready.

Candidate and stable builds use separate update channels. A candidate does not automatically become a stable build. No public Desktop update feed has launched, so an unavailable update check during private testing does not mean you should remove the app or its profile. Ask the prerelease team which build to use.

If an update was prepared after you approved installation but a later unsaved-work prompt stopped the restart, it may install on your next normal Quit. Finish pending work before quitting. A failed update check leaves your current app available; check your connection and retry later.

Testing an invited prerelease#

Use the build version, test space and sample media provided by the prerelease team. Keep client work and private recordings out of the test.

Confirm the version in About matches the supplied build instructions.
Sign in and check the intended account and test workspace. If a passkey click produces no prompt, record whether it happened in Desktop or your browser, then use another supported sign-in method and report the failed attempt.
Complete the assigned recording, upload and review exercises with disposable sample content. Play the saved upload or sent test comment; a local unsent preview does not establish that it uploaded.
Finish and sync all test work before quitting and reopening. If an unfinished-work warning appears, choose Cancel and finish the work first.

The prerelease team tracks results separately for each supplied build. Follow its assigned test sequence and report blocked steps as well as failures.

Get help#

Use Report a bug from the account menu, or contact support. Include:

Your Cuevue Desktop version from the app's About window, your macOS version and whether your Mac has Apple Silicon.
What you were doing, the steps to reproduce it, and the message shown.
Whether you were using Desktop or your browser, and whether a recording, upload or unsynced change is still pending. For sign-in problems, include the browser/password manager names and versions and whether any prompt appeared.

Review screenshots before sending them. Leave out passwords, sign-in links, full callback URLs and private media. Support does not need your password to investigate a Desktop problem.