# Remote SSH Agent unusable on Ceph HPC after cursor\_agent\_host — hung Planning / agent\_host\_bridge\_unavailable (was fast before) **URL:** \ **Category:** Bug Reports\ **Tags:** chat, performance, ssh\ **Created:** [October 8, 2026, 12:26pm UTC](https://forum.cursor.com/t/remote-ssh-agent-unusable-on-ceph-hpc-after-cursor-agent-host-hung-planning-agent-host-bridge-unavailable-was-fast-before/174073 "2026-10-08T12:26:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Milad\_Dadgar](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Milad\_Dadgar](https://forum.cursor.com/u/Milad_Dadgar)\ **Post date:** [October 8, 2026, 12:26pm UTC](https://forum.cursor.com/t/remote-ssh-agent-unusable-on-ceph-hpc-after-cursor-agent-host-hung-planning-agent-host-bridge-unavailable-was-fast-before/174073/1 "2026-10-08T12:26:58Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug After the cursor\_agent\_host rollout, Agent over Remote SSH became unusable/extremely slow on my HPC compute node. Same SSH config + same Ceph project used to be fast. Local (non-SSH) Agent still works. Symptoms over Remote SSH: - Stuck on “Planning next moves” - Connection Error - agent\_host\_bridge\_unavailable: “Timed out waiting for the agent host bridge to register” - When it works, TTFT often 30–60+ seconds, then degrades after a few messages Editor/terminal/files still work. Only Agent is broken/slow. Request IDs: - 74b460ac-1cd1-4503-93be-9f44df6b8c07 (agent\_host\_bridge\_unavailable) - Remote SSH successes with very high TTFT (~59s, ~67s) in same environment Remote: Debian 5.10, node g105 via ProxyJump, /home on Ceph. Sandbox preflight fails (no Landlock V3 / no bwrap). curl [https://api2.cursor.sh](https://api2.cursor.sh) from remote returns HTTP/2 200. Please disable cursor\_agent\_host for my account or restore the previous local-client Agent path for Remote SSH on Ceph/HPC. ### Steps to Reproduce 1. On Mac Cursor 3.23.23, connect Remote-SSH to HPC compute node (ProxyJump login node). 2. Open a project under Ceph home (e.g. ~/projects). 3. Wait until Running Extensions finishes (remote agent extensions may take 15–20s or hang on Activating). 4. Open Agent and send a short prompt (“hi”). 5. Observe: stuck on Planning next moves / Connection Error / agent\_host\_bridge\_unavailable, OR reply only after 30–60+ seconds. 6. Send a few more messages: sometimes works briefly, then becomes stuck/slow again. 7. Compare: same Agent prompt in a local (non-SSH) window works quickly. ### Expected Behavior Agent over Remote SSH should work like before the cursor\_agent\_host change: fast and reliable, with AI traffic via the local Cursor client, even when the remote home is on Ceph and the kernel lacks Landlock V3/bwrap. Editor-only Remote SSH already works; Agent should not hang or take ~1 minute for first token. ### Screenshots / Screen Recordings ![Screenshot 2026-10-07 at 15.38.27.png](https://us1.discourse-cdn.com/cursor1/original/3X/6/7/67a65b96664792c42e3e6ba36bf11bea61f06d58.png) ![Screenshot 2026-10-07 at 23.06.17.png](https://us1.discourse-cdn.com/cursor1/original/3X/4/3/435f063bfe6b62ed46877318d7d5b19663c96caa.png) ### Operating System MacOS ### Version Information Version: 3.23.23 VSCode Version: 1.128.0 Commit: 2dac2428994fe34f12658d9ecad1541b98db2c00 Date: 2026-10-05T01:43:43.807Z Electron: (see Help → About if needed) OS: Darwin arm64 25.6.0 (macOS) CLI: n/a (issue is Desktop IDE Remote-SSH Agent) ### For AI issues: which model did you use? Default / Auto (reproduced across models; not model-specific). Local Agent works; Remote SSH Agent fails/slows. ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [October 8, 2026, 1:34pm UTC](https://forum.cursor.com/t/remote-ssh-agent-unusable-on-ceph-hpc-after-cursor-agent-host-hung-planning-agent-host-bridge-unavailable-was-fast-before/174073/5 "2026-10-08T13:34:20Z")
Hey, thanks for the detailed report and the request ID. I can see both screenshots with the errors `agent_host_bridge_unavailable` and high TTFT. What changed is that on newer versions, Agent runs inside Cursor server on the remote machine, not in the local app. From your logs, the model responds in a couple of seconds, but each request waits a long time on the remote side before it gets sent. Both errors in the screenshots point to the agent component on the remote side not starting within the allowed time. This is not something wrong with your setup, and it matches well with home being on a network file system like Ceph, since both Cursor server and its data live in `~/.cursor-server`. There are 2 options here, you can try either one or both. 1. Check the Ceph hypothesis by running Cursor server from node-local disk: - Close the Remote SSH window in Cursor. - SSH into g105 from a normal terminal and run: `pkill -u "$USER" -f .cursor-server` - Run: `mv ~/.cursor-server ~/.cursor-server.bak` - Pick a directory on the node-local disk, not Ceph, for example `/tmp/$USER` or the cluster’s local scratch, then run: `mkdir -p /tmp/$USER/cursor-server && ln -s /tmp/$USER/cursor-server ~/.cursor-server` - Reconnect to g105 over Remote SSH and wait for the remote extensions to finish loading. - Open a new Agent chat and send `hi`. Does the reply come back quickly? This only works while you connect to the same node. To roll it back, run: `rm ~/.cursor-server && mv ~/.cursor-server.bak ~/.cursor-server`. 1. Go back to the previous agent setup: - I can switch your account back to the older local-client path for Remote SSH. After that, fully quit Cursor with `Cmd+Q` and open it again so the change applies, then reopen the SSH window. Let me know if you want me to do that. In either case, these diagnostics would help a lot: - The output of `df -T ~ /tmp` and `uptime` on g105 - A screenshot of Command Palette \> `Developer: Show Running Extensions` in the SSH window, so we can see how many remote extensions are activating Let me know how it goes. ---
**Author:** ![Milad\_Dadgar](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Milad\_Dadgar](https://forum.cursor.com/u/Milad_Dadgar)\ **Post date:** [October 8, 2026, 2:15pm UTC](https://forum.cursor.com/t/remote-ssh-agent-unusable-on-ceph-hpc-after-cursor-agent-host-hung-planning-agent-host-bridge-unavailable-was-fast-before/174073/7 "2026-10-08T14:15:01Z")
> [@deanrie](#): > > - `uptime` Thanks! that matches what I’m seeing. I already tried option 1 (symlink ~/.cursor-server → /tmp/… on local ext4). It helped a bit with extension activation, but Agent is still slow/intermittent (high TTFT, sometimes Planning forever / bridge timeout). **Please switch my account back to the older local-client path for Remote SSH (option 2).** Diagnostics: df -T ~ /tmp Filesystem Type 1K-blocks Used Available Use% Mounted on …:/home ceph … 84% /home /dev/mapper/g105–vg-root ext4 … 62% / uptime 15:03:24 up 108 days, 5:44, 5 users, load average: 0.44, 0.45, 0.28 Also attaching Developer: Show Running Extensions from the SSH window. ![Screenshot 2026-10-08 at 15.01.50](https://us1.discourse-cdn.com/cursor1/original/3X/d/e/de69abac455ff8649f83ed81d5d9b64f667336b4.png) ![Screenshot 2026-10-08 at 15.02.19](https://us1.discourse-cdn.com/cursor1/original/3X/9/7/975d7feb65b6a5a4f87214e8896c8dd7adea7c47.png) Thanks, Milad Dadgar ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [October 8, 2026, 3:21pm UTC](https://forum.cursor.com/t/remote-ssh-agent-unusable-on-ceph-hpc-after-cursor-agent-host-hung-planning-agent-host-bridge-unavailable-was-fast-before/174073/8 "2026-10-08T15:21:45Z")
Thanks for digging into this. It helped narrow things down: - Node `g105` is basically idle with a load average of 0.44, so this doesn’t look like a load issue on that machine. - Even after moving `~/.cursor-server` to local ext4, the remote extensions still take 6 to 11 seconds to activate (`cursor-agent-host` ~6.8s, Emmet ~11s, retrieval ~10.5s). So the symlink only helped partly. Ceph makes it worse, but it isn’t the only factor. This doesn’t look like something wrong in your setup. I’ve passed it to the team along with your timing data and the request to restore the previous local-client path for Remote SSH. I’ll update you here once I hear back.