Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Agents are unable to read files. During thinking, composer 2.5 told me that “Execution backend unavailable.” Steps to Reproduce Ask anything to agent that include reading files from codebase. Screenshots / Screen Recordings …

I have the same problem… My agents aren’t able to read files in a project anymore… It says that the “Execution backend” is unavailable. I tried to update and upgrade my WSL Linux distro, rebooted several times, I’m out of options… After investigating by asking the agent what errors it gets, it sa…

same here, some times it works by reseting the IDE, mas sometimes don’t

Even after switching off nightly + manually reinstalling 3.6.31, agents are unable to navigate through the project. Agent answer on what is broken: What the errors mean Every tool call is returning: Execution backend unavailable That includes Read, Grep, Glob, and even a simple pwd. When that h…

This is a known issue where the extension host becomes unresponsive, which blocks all agent tool calls. Our team is actively working on it. Since you’ve already tried switching from Nightly to Stable and reinstalling, here are some more targeted steps: 1. Check for a leftover out folder in cursor-…

So I’ve tried every solutions you’ve suggested and none of them worked. In order here is the results: No leftover out folder. PS C:\Users\Admin> dir "C:\Program Files\cursor\resources\app\extensions\cursor-socket" Répertoire : C:\Program Files\cursor\resources\app\extensions\cursor-socket Mode …

I have the same problem. For me, the `cursor-agent-worker` extension shows a “Reload Window” button, but even after I press it and the window reloads, the button stays there and the agent still can’t use the tools. Pretty annoying. I just started using Cursor yesterday and subscribed to Pro today. …

A root cause for the “only one project is broken, others work fine” variant — a stale \\wsl.localhost (UNC) workspace identity Posting in case it helps others with the project-specific flavor of this (one WSL project throws “Execution backend unavailable” on every tool call — Read/Grep/Glob/shell —…

Thanks for the logs, they actually pinpoint what’s happening. Your WSL connection itself is fine: Cursor connects to your Debian WSL server and detects the kernel. The problem is one layer up. The agent’s execution session never finishes attaching, so it times out after 30s, retries, and every tool…

I was facing this issue from last few days but after clearing complete AppData\Roaming\Cursor\User\workspaceStorage now all tools and terminal commands are working.

File-read backend unavailable

Support Bug Reports

Elton_Nicolau (Elton Nicolau) June 17, 2026, 2:06am 15

I found a workaround by connecting to WSL through SSH, not by wsl default connection

Execution backend unavailable

Topic		Replies	Views
Intermittent "Execution backend unavailable" errors blocking all tool use Bug Reports terminal , wsl	13	257	August 10, 2026
Agent tools fail on WSL workspace opened via \\wsl.localhost\ — path resolves to C:\home\..., Glob times out, Shell intermittent (Cursor 3.9.16) Bug Reports terminal , extensions , wsl	2	71	July 11, 2026
Execution backend unavailable Bug Reports wsl	77	3093	August 3, 2026
Agents freeze at grepping and subagents Bug Reports performance , subagents , multitask	12	469	May 4, 2026
Can't connect to WSL anymore Bug Reports wsl , windows	10	1177	April 23, 2026

File-read backend unavailable

Related topics