Unable to configure new remote environment

[Jake.Capra]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I am trying to configure a new remote environment for remote agents. When I get to the “Create a Machine Snapshot” step, I run into an error:

Failed to connect to the remote extension host server (Error: [internal] Pod exists but exec-daemon is unreachable after 8 retries)

I’ve tried this a few times and keep getting this error

Steps to Reproduce

1. In Cursor, invoke the Cursor: Restart Cloud Agent Environment Setup task from the command palette
2. Continue to the “Create a Machine Snapshot” step and try to do something (like prompt to install dependencies)

At step 2, I get connection errors and can never get past this.

Expected Behavior

I am able to set up a remote environment without running into connection issues.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (Universal)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
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: add Request ID with privacy disabled

d53a8672-b8eb-417d-9319-b12ba7f6e1bb

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. The error “Pod exists but exec-daemon is unreachable after 8 retries” means there’s a connectivity issue to the remote Background Agent - the pod is created, but the daemon inside isn’t reachable.

Thanks for the Request ID - I’ll pass it to the engineers.

Similar reports: Cloud Agents failing with "environment error"

This is a known infrastructure issue under investigation (related to the exec-daemon in remote environments). In the meantime, please try:

• Wait 10-15 minutes and retry the setup - these are often temporary infra hiccups
• Check internet stability and try without VPN/proxy
• Enable debug logs: Settings > Application > Log Level > Debug, then retry and copy the logs

Please follow the updates in the linked thread.

[Jake.Capra]

Wait 10-15 minutes and retry the setup - these are often temporary infra hiccups

I tried again and ran into to same error

Enable debug logs: Settings > Application > Log Level > Debug, then retry and copy the logs

I could not find this.

I’ll check out the other thread as well.

[httpiga (Nicola)]

I’m having the same issue too

[Jake.Capra]

I am still running into this problem.

Reuqest ID: default: “pod-3fmcmagqaja4pgyoyq65gdpgia”

[kkra]

I have been running into this issue as well for the past 24h. Tried different networks and settings. No luck!