Cursor agent freezes while globbing?

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I paste in a ~4 line prompt, and ask Cursor CLI agent -f to make a plan, then as I tab to a different terminal tab, it freezes animations on the globbing step and shows me the next dialog box, having done nothing. I have to do the query again a few min later once no progress is made.

Steps to Reproduce

Not sure, this only happened 1-2 times to me, you’ll probably need logs.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

2026.02.13-41ac335

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

It also freezes on generating, then I try to screenshot (cmd shift 4) and it resets the query. This doesn’t happen with any other agentic coding tool. Not sure why this is happening, maybe related to Ghostty?

Hey, thanks for the report. I can see in the screenshot that the globbing step is hanging.

A few questions to narrow it down:

  1. Can you confirm you’re using Ghostty? If yes, does this also happen in another terminal, like Terminal.app or iTerm2?
  2. How big is the project, roughly how many files? I’m wondering if the glob patterns are hitting a very large directory tree.
  3. About the second issue, Cmd+Shift+4 resetting the request, that’s interesting. Does any focus change, like clicking another window, also reset it, or is it specific to the screenshot hotkey?

If you can run the same request in another terminal emulator, that’ll help us tell if this is Ghostty-specific. Let me know what you find.

  1. Using Ghostty, haven’t tried other terminals. I could.
  2. • 1,178 files total (everything except .git/)
    • 80 files if you exclude build/cache directories (.gradle/, .gradle-local/, build/, app/build/)
  3. I don’t think it has anything to do with the screenshot hotkey, I think that was coincidence. I think it’s about focus change?

Is there any request ID or trace I can ask Cursor to provide you?

Thanks for the info.

1 178 files shouldn’t be a problem for globbing, so it’s probably not related to the folder size.

The focus-change idea makes sense, let’s test it. Can you try the same workflow in Terminal.app or iTerm2? That’ll show whether this is specific to Ghostty or a general CLI agent issue.

Also, since you mentioned it, the request ID would be helpful. Next time it hangs, you can grab it from the CLI output, that’ll give us more data.

One more thing: when the request “resets” after changing focus, does the CLI show any error message, or does it quietly restart from scratch?