Remote Cloud Server Issues

Support Help
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Not sure what this means? the Remote server flickers back and forth many times a second. saying either “Starting Remote Server…” or “Reconnecting”.

I’ve tried desktop cloud agents via Cursor app and also cursor.com cloud agents and both fail.

I tried to look up Cloud Agent usage but there is nothing on this topic in docs.

I can’t connect to “remote” desktop or browse any files in the cloud agents regardless of repos.

Please help and advise.

thank you

image

image
image320×137 2.03 KB

image
image443×174 2.35 KB

image

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hi @shibz Thank you for the post. Three separate things are going on:

  • The banner is the root of it. Your Ultra plan’s included usage for this billing cycle is used up and on-demand usage isn’t enabled, so new Cloud Agent runs are being declined rather than charged. You can turn on on-demand usage (and set a monthly spend limit) from the Spending tab at cursor.com/dashboard/spending, or wait for your cycle to roll over. Details: Spend limits
  • Cloud Desktop and Terminal are expected to fail here. Those views connect to the machine the agent runs on, and the machine shuts down once the agent finishes. They’ll only work on an agent that’s currently running, which is why it happens regardless of repo.
  • The flickering indicator isn’t anything you misconfigured. When the connection can’t reach an agent’s machine, it retries immediately and repaints each time, so it snaps between “Starting Remote Server” and “Reconnecting” instead of settling.

Let me know any follow-up questions!

8

ok thank you for explaining.

Just a few more details/follow ups:

  1. I only got the “You’ve used all the included Cloude Agent usage” when working in Environments Cloud Agents page - nowhere else does this banner materialize (pain trying to diagnose this)

  2. I still have usage available, why not use this?

    image
    image1135×421 11.7 KB

  3. Cloud Agents still work, just the remote “streaming” is not working - (hopefully we don’t lose access to cloud by sharing this)

  4. Cursor just announced major price reductions in Cloud Agents - so remaining usage in “Cursor Models” should be used (IMHO).
    Cursor on X: "Cloud agents are now 20-30% more token efficient, and 80% more efficient on runs with computer use. We've improved how they handle MCPs, skills, and computer use, so you can delegate more ambitious tasks and get back demos while staying within budget." / X

  5. Do “Cursor Models” use “Other models” usage when using Cloud Agents?

Thanks for your prompt feedback!