No remote extention when setting up Cloud Agent

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I go to the Cloud Agent Setup UI in composer, I get a “No remote extension installed to resolve background-composer”. I know there are connection issues (e.g. with AWS) but this feels like it might be a configuration issue ?
I’ll be trying again regularly just in case.

This is my cursor version :
Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Steps to Reproduce

1/ Start the Cloud Agent Setuo UI via the command palette
2/ Wait a few seconds

Expected Behavior

I am unable to start the Cloud Agent Setu

Screenshots / Screen Recordings

CleanShot 2026-01-17 at 07.50.48@2x.png
CleanShot 2026-01-17 at [email protected]2732×1660 373 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

GPT 5.2 Codex

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
3

Hey, thanks for the report. This is a known issue with the Cloud Agent infrastructure. The exact same error was already reported here: Cloud Agents Setup: "No remote extension installed to resolve background-composer" error during Machine Snapshot creation

It’s related to the exec-daemon and the remote extension setup. The team is aware, but there’s no ETA for a fix yet.

You can try these workarounds (not guaranteed, but they helped some users):

  • Wait 10 to 15 minutes, then try again
  • Disable VPN or proxy if you’re using one
  • Check your network: Settings > Network > Run Diagnostics
  • Try again at a different time of day (there may be regional AWS issues)
  • Instead of Manual Snapshot, try using a Dockerfile

I added your report to the existing issues to help with visibility. Let me know if any workaround helps.

4

The workarounds doesn’t seem to work correctly. Are there some Dockerfile examples to try to recreate it for my use case?

6

I wonder if this is a problem with AWS in Europe ? I’m in Paris

8

I’m getting the same error with a Dockerfile. I tried this 1-2 hours ago as well, and got the same error

10

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.