Multi-repo Plan Build hanging

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am trying to build a plan in the Agent window that touches two repos. Every time I’ve tried it (I did some last night also) it thinks for a minute then just sits there, hung on “Planning next moves”. It is two remote (ssh) repos, btw, though I’ve never had any problems with Cursor on these individually before.

My latest attempt:

request ID: f5c984a7-f3e5-4b2f-bdf0-62e9e2a15717

has been sitting for 20 minutes.

Other uses (separate project, single repo) don’t seem to have any problems.

Steps to Reproduce

just by trying to build the plan.

Expected Behavior

I would expect the agent to not hang on “planning next moves..”

Operating System

MacOS

Version Information

Version: 3.17.8 (Universal)
VS Code Extension API: 1.128.0
Commit: 2fdd31c9f33f7fbe501f2d57772dc5bf64b63620
Date: 2026-08-20T02:18:12.724Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Auto, but I have similar behavior selecting Grok 4.6 directly

For AI issues: add Request ID with privacy disabled

f5c984a7-f3e5-4b2f-bdf0-62e9e2a15717

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @jawaidbazyar2, thanks for the report and the request ID. We traced it: planning runs fine until the agent goes to write the plan out, then wedges. This isn’t your setup, and it matches an issue we’re tracking with multi-root workspaces over Remote SSH, which I’ve passed along.

For now, opening a window with just one of the repos avoids the hang (I know that doesn’t cover the cross-repo plan, but it keeps you unblocked). One thing that’d help: are the two repos on the same SSH host or two different hosts? A single window only connects to one host, so two hosts in one workspace isn’t supported today and could itself explain this.

8

thank you for your response! I ended up breaking the plan into two pieces based on repo and that got it through as well.