Sub-agent Worktree implementation seems to be stuck in a loop

Support Bug Reports
,
1

Screenshot 2026-09-01 at 8.04.27 PM
Screenshot 2026-09-01 at 8.04.27 PM933×1178 63.9 KB

As per my screenshot, my subagent were stuck in the loop for a very long period of time. I haven’t stopped the agents from running yet as I want to share the debugging information here with you.

6a79871b-e71f-4e98-8a75-93b4af52cb77

Any idea what would be the cause? I used Cursor Grok 4.5 and Composer 2.5 as my subagent for the development work.

let me know if you need more info.

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

8

Hey @Andy_Wong
Your subagents weren’t actually looping, one stalled on a file edit and then just sat idle (nothing was running or using usage in that window). It’s not anything on your end, and it’s an issue we’re already tracking.

If a subagent sits on the same status for more than a few minutes: open the agents panel and hit Stop All (or stop just the stuck one), then re-run the task. If it only looks stuck, Cmd/Ctrl+Shift+P → “Reload Window” resyncs it. Running the work in a normal foreground agent avoids this too.

10

Okay. Thanks @mohitjain

I got things resumed to work after stopping all and reload the window app.

All good on my end now :+1: