Cloud Desktop inaccessible — Claude Sonnet usage limit despite Grok 4.6 selected

Describe the Bug

Hello Cursor Support Team,

I need assistance with a persistent Cloud Desktop issue that is blocking my website development.

I use Cursor Cloud Agents exclusively through Chrome, without the desktop application.

Problem:

The Desktop panel displays:

“The agent’s machine may not be running. Send a message to restart.”

The agent reports that its cloud machine is running and the website is available internally, but the interactive Desktop cannot connect.

I am using Grok 4.6 High Fast. However, the agent’s diagnostic output indicates that Desktop operations are being routed to a Claude 4.5 Sonnet subagent whose usage limit has been exhausted.

I have already tried reconnecting, restarting the session, and creating a new agent using the recovered Git branch. The issue persists.

Technical details:

  • Repository: respaldo-videos/ayco-ascen-website
  • Branch: backup-ayco-recuperado-20261116
  • Agent ID: bc-d62c4e91-f5ed-4a10-bb9e-1330384d689e
  • Run ID: run-a6892111-4444-4f95-8ab8-0081f9090e9f
  • Selected model: Grok 4.6 High Fast

Requested resolution:

  1. Restore access to the interactive Cloud Desktop without requiring additional Claude Sonnet usage.
  2. Investigate why Desktop operations appear to invoke Claude Sonnet when Grok is selected.
  3. Alternatively, enable an authenticated HTTPS preview of my existing Next.js application directly in Chrome.
  4. Preserve the cloud environment, repository and all recovered development work.

This is preventing me from continuing an existing website project. I need a functional browser-based workflow without installing the Cursor desktop application.

Please investigate and provide a concrete resolution.

Thank you.

Steps to Reproduce

  1. Open cursor.com/agents in Google Chrome.
  2. Open an existing Cloud Agent connected to a Next.js website repository.
  3. Select Grok 4.6 High Fast as the agent model.
  4. Open the Desktop tab to access the interactive cloud machine.
  5. The Desktop displays ‘The agent’s machine may not be running’ or ‘Failed to connect’.
  6. Ask the agent to restore the Desktop. The agent reports that Desktop operations invoke Claude 4.5 Sonnet, whose usage limit is exhausted.
  7. Create a new Cloud Agent using the same repository and recovered branch. The Desktop issue persists.

Operating System

Other

Version Information

Cursor Cloud Agents (web version), accessed through Google Chrome on Windows 11. Agent model: Grok 4.6 High Fast. Desktop subagent reports Claude 4.5 Sonnet usage limit. Agent ID: bc-d62c4e91-f5ed-4a10-bb9e-1330384d689e.

For AI issues: which model did you use?

Grok 4.6 High Fast.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @RESPALDO_VIDEOS, the Desktop tab doesn’t use Claude or any other model, so the Sonnet limit isn’t what’s stopping it. That message shows when the agent’s machine is asleep, which happens about 15 minutes after the agent finishes a turn. Send the agent a short message, open Desktop while it’s working or right after, then take control and open your site in the browser inside that desktop.

The Sonnet usage comes from something else: when the agent tests the UI on its own, that helper always runs on Claude Sonnet, whatever model you picked, and it counts against Other Models. This is a known issue the team is aware of, discussed in this thread. For now, ask the agent to start the dev server and leave the testing to you.

A direct preview link in Chrome isn’t available on the web version, so Desktop is the way to see the running site.

Your work is safe as long as it’s committed and pushed to your branch, so have the agent do that before you step away.

If Desktop still won’t connect within a minute or two of the agent replying, tell me what time it happened and I’ll take a closer look.