Cursor's Remote-SSH agent becomes unresponsive at every session start due

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Title: Remote-SSH session: agent unresponsive due to RequestStore#acceptReply desync from cold-start

Environment

  • Cursor (Mac client, version: <paste from Cursor → About>)
  • Remote target: Linux VDI via Remote-SSH
  • cursor-server build: d5b2fc092e16007956c9e5047f76097b9e626ca0
  • Remote OS: Ubuntu (kernel 5.15), 12 cores, 64 GiB RAM
  • Workspace: large monorepo (~644k files), opened directly (no multi-root)

Bug

Every Remote-SSH cursor-server session begins with a burst of warnings in
~/.cursor-server/data/logs//remoteagent.log:

[warning] RequestStore#acceptReply was called without receiving a matching request 1
[warning] RequestStore#acceptReply was called without receiving a matching request 2
… (typically 50-300+ within the first 1-15 seconds of session start)

This persists across sessions and indicates the cursor-server’s RPC layer is receiving replies for requests it has no
record of issuing (or has already cancelled). The AI agent (anysphere.cursor-agent-worker) loads successfully but
becomes unresponsive — chat messages don’t get replies, tool calls hang, and the editor sometimes can’t take keystrokes.
After this, the “Extension host terminated unexpectedly 3 times within the last 5 minutes” popup eventually appears.

Steps to reproduce

  1. Open Cursor (Mac), connect to a remote SSH host with a large monorepo workspace.
  2. Open ~/.cursor-server/data/logs//remoteagent.log on the remote.
  3. Observe RequestStore#acceptReply warnings within seconds of session start.
  4. Try to use the AI agent — chat is silently unresponsive.

What I tried (none of which fixed the RequestStore desync)

  • Reload Window
  • Kill extensionHost / multiplex-server / all cursor-server procs and reconnect
  • Aggressive files.watcherExclude (driving inotify watches from 156k → ~30k)
  • Full rm -rf ~/.cursor-server and let it redeploy from a fresh Mac client launch
  • Reinstall Cursor on the Mac (same desktop version → same cursor-server build)
  • Remove a failing --install-extension entry from remote.SSH.defaultExtensions on the Mac. This eliminated Failed
    Installing Extensions errors in the log, but the RequestStore#acceptReply desync still happens at session start
    regardless.

Attached

  • remoteagent.log from a freshly-started session (please include this — path:
    ~/.cursor-server/data/logs//remoteagent.log)
  • Output of the launch args: ps -ef | grep “cursor-server --start-server”

Steps to Reproduce

  1. Open Cursor (Mac), connect to a remote SSH host with a large monorepo workspace.
  2. Open ~/.cursor-server/data/logs//remoteagent.log on the remote.
  3. Observe RequestStore#acceptReply warnings within seconds of session start.
  4. Try to use the AI agent — chat is silently unresponsive.

Operating System

MacOS

Version Information

Version: 3.5.17 (Universal)
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z

Additional Information

RequestStore#acceptReply

I see Cursor’s Remote-SSH agent becomes unresponsive at every session start due to a burst of RequestStore#acceptReply was
called without receiving a matching request warnings in remoteagent.log, which persists across full server reinstall and
reconnect.

Does this stop you from using Cursor

Yes - Cursor is unusable

4

This is the log:


2026-05-20 22:24:27.948 [info] Installing extensions...
2026-05-20 22:24:27.948 [info] Extension host agent started.
2026-05-20 22:24:27.953 [info] Started initializing default profile extensions in extensions installation folder. file:///home/nbozinovic/.cursor-server/extensions
2026-05-20 22:24:28.030 [info] Completed initializing default profile extensions in extensions installation folder. file:///home/nbozinovic/.cursor-server/extensions
2026-05-20 22:24:28.379 [info] [127.0.0.1][059b8e5b][ManagementConnection] New connection established.
2026-05-20 22:24:28.397 [info] [127.0.0.1][c8ed54e8][ExtensionHostConnection] New connection established.
2026-05-20 22:24:28.408 [info] Getting extensions control
2026-05-20 22:24:29.314 [info] [127.0.0.1][c8ed54e8][ExtensionHostConnection] <2908261> Launched Extension Host Process.
2026-05-20 22:24:29.379 [warning] RequestStore#acceptReply was called without receiving a matching request 1
2026-05-20 22:24:29.379 [warning] RequestStore#acceptReply was called without receiving a matching request 2
2026-05-20 22:24:29.379 [warning] RequestStore#acceptReply was called without receiving a matching request 3
2026-05-20 22:24:29.379 [warning] RequestStore#acceptReply was called without receiving a matching request 4
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 5
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 6
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 7
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 8
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 9
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 10
2026-05-20 22:24:29.380 [warning] RequestStore#acceptReply was called without receiving a matching request 11
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 12
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 13
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 14
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 15
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 16
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 17
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 18
2026-05-20 22:24:29.381 [warning] RequestStore#acceptReply was called without receiving a matching request 19
2026-05-20 22:24:29.382 [warning] RequestStore#acceptReply was called without receiving a matching request 20
2026-05-20 22:24:29.382 [warning] RequestStore#acceptReply was called without receiving a matching request 21
2026-05-20 22:24:29.382 [warning] RequestStore#acceptReply was called without receiving a matching request 22
2026-05-20 22:24:29.382 [warning] RequestStore#acceptReply was called without receiving a matching request 23
2026-05-20 22:24:29.382 [warning] RequestStore#acceptReply was called without receiving a matching request 24
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 25
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 26
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 27
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 28
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 29
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 30
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 31
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 32
2026-05-20 22:24:30.312 [warning] RequestStore#acceptReply was called without receiving a matching request 33
2026-05-20 22:24:30.313 [warning] RequestStore#acceptReply was called without receiving a matching request 34
2026-05-20 22:24:30.313 [warning] RequestStore#acceptReply was called without receiving a matching request 35
2026-05-20 22:24:30.313 [warning] RequestStore#acceptReply was called without receiving a matching request 36
2026-05-20 22:24:30.405 [info] Installing extension 'llvm-vs-code-extensions.vscode-clangd'...
2026-05-20 22:24:30.405 [info] Getting Manifest... llvm-vs-code-extensions.vscode-clangd
2026-05-20 22:24:30.663 [info] Installing extension: llvm-vs-code-extensions.vscode-clangd {"isMachineScoped":false,"installPreReleaseVersion":false,"isApplicationScoped":true,"isBuiltin":false,"installGivenVersion":false,"installOnlyNewlyAddedFromExtensionPack":true,"profileLocation":{"$mid":1,"fsPath":"/home/nbozinovic/.cursor-server/extensions/extensions.json","external":"file:///home/nbozinovic/.cursor-server/extensions/extensions.json","path":"/home/nbozinovic/.cursor-server/extensions/extensions.json","scheme":"file"},"productVersion":{"version":"3.5.17","date":"2026-05-20T02:43:31.559Z","vscodeVersion":"1.105.1"}}
2026-05-20 22:24:30.680 [info] Started downloading extension: llvm-vs-code-extensions.vscode-clangd 0.4.0 file:///home/nbozinovic/.cursor-server/data/CachedExtensionVSIXs/llvm-vs-code-extensions.vscode-clangd-0.4.0-universal
2026-05-20 22:24:31.025 [info] Extracted extension to file:///home/nbozinovic/.cursor-server/extensions/llvm-vs-code-extensions.vscode-clangd-0.4.0-universal: llvm-vs-code-extensions.vscode-clangd
2026-05-20 22:24:31.029 [info] Renamed to /home/nbozinovic/.cursor-server/extensions/llvm-vs-code-extensions.vscode-clangd-0.4.0-universal
2026-05-20 22:24:31.037 [info] Extension installed successfully: llvm-vs-code-extensions.vscode-clangd file:///home/nbozinovic/.cursor-server/extensions/extensions.json
2026-05-20 22:24:31.037 [info] Extension 'llvm-vs-code-extensions.vscode-clangd' v0.4.0 was successfully installed.
2026-05-20 22:24:32.324 [warning] RequestStore#acceptReply was called without receiving a matching request 37
2026-05-20 22:24:32.324 [warning] RequestStore#acceptReply was called without receiving a matching request 38
2026-05-20 22:24:32.324 [warning] RequestStore#acceptReply was called without receiving a matching request 39
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 40
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 41
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 42
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 43
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 44
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 45
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 46
2026-05-20 22:24:32.325 [warning] RequestStore#acceptReply was called without receiving a matching request 47
2026-05-20 22:24:32.326 [warning] RequestStore#acceptReply was called without receiving a matching request 48
2026-05-20 22:24:35.338 [info] [CursorProclistService] Config enabled feature (subsample every 10s)
2026-05-20 22:24:40.910 [info] [127.0.0.1][059b8e5b][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
2026-05-20 22:24:40.963 [info] [127.0.0.1][c8ed54e8][ExtensionHostConnection] <2908261> Extension Host Process exited with code: 0, signal: null.
2026-05-20 22:24:40.963 [info] Cancelling previous shutdown timeout
2026-05-20 22:24:40.964 [info] Last EH closed, waiting before shutting down
2026-05-20 22:24:44.457 [info] [127.0.0.1][5279de7e][ManagementConnection] New connection established.
2026-05-20 22:24:44.515 [info] [127.0.0.1][688fbbff][ExtensionHostConnection] New connection established.
2026-05-20 22:24:44.521 [info] [127.0.0.1][688fbbff][ExtensionHostConnection] <2910899> Launched Extension Host Process.
2026-05-20 22:24:44.720 [warning] RequestStore#acceptReply was called without receiving a matching request 49
2026-05-20 22:24:44.720 [warning] RequestStore#acceptReply was called without receiving a matching request 50
2026-05-20 22:24:44.720 [warning] RequestStore#acceptReply was called without receiving a matching request 51
2026-05-20 22:24:44.720 [warning] RequestStore#acceptReply was called without receiving a matching request 52
2026-05-20 22:24:44.720 [warning] RequestStore#acceptReply was called without receiving a matching request 53
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 54
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 55
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 56
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 57
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 58
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 59
2026-05-20 22:24:44.721 [warning] RequestStore#acceptReply was called without receiving a matching request 60
2026-05-20 22:24:56.432 [info] [CursorProclistService] Config enabled feature (subsample every 10s)
5

This si AI summary:

“Agent stops responding in Remote-SSH sessions to my Linux VDI. Logs show a burst of RequestStore#acceptReply was
▎ called without receiving a matching request warnings at session start (50-300+ in the first second). Don’t know if
▎ these are the root cause or a parallel symptom. Persists across full ~/.cursor-server nuke and Mac Cursor reinstall.”

9

This is a known issue we’re actively investigating.

Our engineering team is working on improvements to extension host startup resilience, especially for large workspaces over SSH.

A few things to try in the meantime:

  1. Reload Window immediately after connecting (sometimes the second startup succeeds where the first times out)

  2. Clean restart of cursor-server: run pkill -f .cursor-server on the remote, then reconnect from the Mac

  3. Reduce inotify pressure further: you mentioned driving watches from 156k to ~30k, but for a 644k-file monorepo, try adding more aggressive files.watcherExclude patterns for directories you don’t actively edit (build outputs, node_modules, vendor, generated code). This reduces work during startup

  4. Check remote machine load during startup: if other processes are competing for CPU/memory during the first 30-60 seconds, it can push the extension host past the timeout

Could you also share:

  • Does the issue happen 100% of the time, or is it intermittent?

  • Are there any antivirus/EDR agents running on the remote Linux VDI that might be scanning files during startup?

If the issue persists, please try switching to the Early Access release track (Cursor Settings > Application > Release Track) — this will get you builds with the latest stability improvements sooner.

You may also find this related thread helpful, where another user on the same version reported a similar SSH-specific agent timeout.

10

I downgraded cursor for now, hearing this will be fixed in 3.5.24+.