# Agent Execution Timed Out in Agents Window (Windows) - new chats fail, only Open IDE works **URL:** \ **Category:** Bug Reports\ **Tags:** canvas, windows, agents-window, chat\ **Created:** [August 31, 2026, 9:47am UTC](https://forum.cursor.com/t/agent-execution-timed-out-in-agents-window-windows-new-chats-fail-only-open-ide-works/170053 "2026-08-31T09:47:13Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [August 31, 2026, 11:17am UTC](https://forum.cursor.com/t/agent-execution-timed-out-in-agents-window-windows-new-chats-fail-only-open-ide-works/170053/11 "2026-08-31T11:17:35Z")
Hi @zhuyoujun, thanks for the detailed report. I checked the logs associated with your account, and the component that runs agents inside the Agents Window is hanging during startup. Every startup attempt is being routed through a local proxy at `127.0.0.1:7897` (port 7897 usually belongs to a proxy client such as Clash, Clash Verge, or Mihomo), and that proxy is resetting the connections. Each attempt stalls for roughly 30 seconds before failing which matches the timeout you’re seeing exactly. Open IDE works because that window spins up a fresh instance of the component, so it’s a workaround rather than a real fix. Two things to try: 1. Fully quit Cursor (end `Cursor.exe` in Task Manager), then launch it once with `--no-proxy-server`. If agents work in the Agents Window, the proxy is confirmed as the cause. 2. Either make sure your proxy client is running, listening on port 7897, and not resetting local connections (if you use TUN mode, try disabling it) or, if you don’t need the proxy, disable it and clear any reference to it from Cursor settings. These two threads cover the same situation in more detail: > [@Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897DHe: \[internal\] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897at Dlk (](https://forum.cursor.com/t/failed-to-establish-a-socket-connection-to-proxies-proxy-127-0-0-1-internal-failed-to-establish-a-socket-connection-to-proxies-proxy-127-0-0-1-7897at-dlk/169389/5): > > Hey, thanks for the report. This error means Cursor is trying to route traffic through a proxy on your machine at 127.0.0.1:7897 (usually a proxy client like Clash), but nothing is responding on that port. Most likely the proxy client was running in the morning, then it got closed or changed its port. What to try: If you’re intentionally using a proxy, make sure the client is running and still listening on port 7897. If the port changed, update it in Cursor settings via http.proxy and also in… > [@Timeout waiting for EverythingProvider](https://forum.cursor.com/t/timeout-waiting-for-everythingprovider/156748/14): > > Hey, from the screenshot it looks like it’s the same error again: Timeout waiting for EverythingProvider. That means the extension host still isn’t starting, and a SOCKS5 proxy in settings.json by itself doesn’t cause this. Something else is likely intercepting loopback again. Port 7897 is a typical mixed port for Clash or Mihomo. If you installed Clash, Clash Meta, or Mihomo again, or if v2rayN or sing-box are still set to auto start, it’s very likely TUN is still enabled in the background. Th… --- _[View the full topic](https://forum.cursor.com/t/agent-execution-timed-out-in-agents-window-windows-new-chats-fail-only-open-ide-works/170053)._