Ever since version 2.4 me and a few other people I work with are having trouble with the Agent getting stuck with “Waiting for extension host”, then after a few seconds it times out.
This only seems to be happening when connected with Remote-SSH to a jailed linux host. If connected to a normal shell it seems to work fine.
Steps to Reproduce
Install latest version of cursor
Add Remote-SSH extension
Connect to a jailed linux host
Send any input to the agent
Hey, thanks for the report. This looks like a known issue where the agent sandbox times out on restricted Linux environments that don’t support newer kernel features (specifically Landlock V3), instead of gracefully falling back.
A “jailed” Linux host is exactly the kind of setup where this can happen. A couple of questions to confirm:
What kind of jail is this? chroot, nsjail, a Docker container, or something else?
What’s the kernel version on the remote host? Run uname -r
Can you check if Landlock is supported? Run cat /sys/kernel/security/lsm and see if it lists landlock.
The team is aware of this specific Remote-SSH plus restricted Linux scenario. No ETA yet, but your report helps with prioritization.
As a temporary workaround, try switching to Ask mode instead of Agent mode. It doesn’t rely on the sandbox or extension host in the same way and might work for you while this is being tracked.
> uname -a > Linux fedora 6.18.13-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 19 19:54:01 UTC 2026 x86_64 GNU/Linux > cat /sys/kernel/security/lsm > lockdown,capability,yama,selinux,bpf,landlock,ipe,ima,evm
Cursor version: 2.6.11
I can also see that in Cursor settings → Rules, Skills, Subagents, everything is in “Loading Rules..”, “Loading Skills…”
I am running locally. I’ve tried disabling extensions, uninstalling Cursor and reinstalling, and removing ~/.config/Cursor/User/globalStorage/state.vscdb
and ~/.config/Cursor/User/workspaceStorage
And I keep ending up with “The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.”
I’ve installed via rpm. The appimage used to have jail problems and needed a bit of tinkering to work correctly; with previous versions the rpm way seems to have worked and I would much prefer that way.
I haven’t yet tried nuking whole ~/config/Cursor. Also worth nothing that while I am not currently running a VPN, I do occasionally run over a VPN - mentioning this just in case there could be some weird cache rot going on or whatnot.
If there’s any additional debug data I can provide, please let me know!
same problem, completely different environment. periodically find myself in “waiting for extension host” and there are no other network issues on my machine at all. sometimes it clears up quickly, sometimes cursor is unusable for hours. it eventually clears up with no action whatsoever on my part.
Hey, unfortunately I can’t share a specific timeline right now. The issue is tracked and on the team’s radar. Your case (chroot jail, kernel 5.4 without Landlock) is a clear example of the problem. I’ve bumped the priority based on your thread and similar reports.
The core issue is that since v2.4, the agent sandbox needs Landlock v3 support. When it’s missing (like in your chroot environment), it times out instead of falling back cleanly. That’s the bug.
For now, staying on v2.3.35 is the most reliable workaround. I know that’s not ideal, but it’s the only option until the fallback is implemented properly.
I’ll post an update here when there’s progress. Sorry I can’t give a better answer right now.
I am having issue already a week, is there any progress? I am fully blocked and can not use app already a week. Please can you also share an email where I can ask for compensation as I have paid version, and its already week I can not use it. Thanks in advance!
Hey @Grig_Vardanyan, you’re on v2.6.14, and that version had a bug with the cursor-socket extension on macOS arm64 that could prevent the extension host from starting at all. This is fixed in 2.6.18. Please update Cursor to the latest version at Cursor · Download and check if the issue is resolved.
About compensation, please email [email protected] and they’ll help with billing requests.