I have multiple monitor setup, and usually open composer on a second screen. I noticed that when I send something to composer from IDE or terminal, Cursor attempts to open Composer in IDE as well, despite of me having it open on the second screen. My Composer threads are usually very long, so it takes quite some time to open instance of Composer each time. And all this time workstation is frozen. Which is a problem by itself, but in general I can cope with this, but not in this case, which is absolutely unnecessary. Why would anyone require to open duplicate Composer instance in IDE, when there’s already a full-screen instance on another display?
Should be easy to fix I think, since there’s a duplex communication between Cursor windows anyway and IDE should be aware about Composer instance being open in a separate window.