Where does the bug appear (feature/product)? Cursor IDE Describe the Bug When using Worktree agents, the agent will sporadically launch a new workspace, switch to it, and continue the work there, and it can’t go back to edit the original workspace. This can spiral out of control and end up with a …

Other report: Agent stuck in "Planning...", "Generating..." - #21 by Vidar_Halvorsen

It’s so messy that Cursor not even launched a new session to continue the work from the original worktree, but it grabbed an existing dangling commit, with some totally unrelated work in it, and continued doing the original worktree’s work there, mixing everything up. [image]

Hey, thanks for the report. This is a known issue. Worktree agents sometimes unexpectedly create new workspaces or switch to unrelated branches or commits mid-session. I can see both screenshots, including the one where the agent picked up an existing “dangling” commit from unrelated work and mixed…

Which model are you using when this happens? GPT-5.3 Codex Do you start the worktree agent manually (via the dropdown), or does the agent decide to use worktree on its own? I start the initial worktree agent manually. The subsequent worktrees are started by the agent itself, and when …

Which model are you using when this happens? Thanks for the info - GPT-5.3 Codex, noted. I start the initial worktree agent manually. The subsequent worktrees are started by the agent itself, and when I’ve asked it why it did, it tells me “Cursor made him do it”. Got it. That’s the core of th…

So the short answer is: There’s no way for me to spawn a new agent in a separate and isolated environment right now, even though I’m paying $600 a month for this. (aka I’m screwed).

I get it, this is really inconvenient, especially on Ultra. You mentioned Cloud Agents also aren’t working. Can you share more details on what exactly is happening there? If it’s a different bug, we might be able to fix that faster and at least get you back to an isolated workflow via cloud. Also …

[image] deanrie: Can you share more details on what exactly is happening there? I’ve been sharing details for 4 months already: Cloud agent can't connect via api3.cursor.sh This frustration that you’re seeing wasn’t born from one day to the other… try a different model (Claude Sonnet 4.6) …

I took another look at your thread about the cloud agent. You provided everything we need, curl requests, console logs, and a video. The issue is clear, and it’s on our side. This task is in our backlog. I’ll reply here when there’s real news.

[image] dny_ex: Cloud agent can’t connect via api3.cursor.sh You said the same thing 4 months ago: Cloud agent can't connect via api3.cursor.sh - #8 by deanrie ……..

Worktree agents fork automatically into separate workspaces

Support Bug Reports

dny_ex March 22, 2026, 8:54pm 19

Any update on this?

1 month without Worktree agents and 5 months without Cloud Agents: Cloud agent can't connect via api3.cursor.sh - #28 by dny_ex

Topic		Replies	Views
Agent stuck in "Planning...", "Generating..." Bug Reports chat , performance	17	154	March 15, 2026
Cloud Agent API is not pushing to the right branch Bug Reports cloud-agents , composer	14	234	April 25, 2026
New /worktree unnecessarily clutters agent output Bug Reports worktrees	3	43	April 29, 2026
Cursor 3: Worktrees & Best-of-N Release Discussions worktrees , subagents	33	3176	April 22, 2026
Lost edits / work - IDE agent worktree and canonical (project)path diverge Bug Reports worktrees	5	88	April 21, 2026

Worktree agents fork automatically into separate workspaces

Related topics