Agent Is Unaware of Existing Terminal Processes

Bug Reports
1

When I have my terminal open in the bottom of the application, and say I’m running npm run dev on port 3000. If I ask Cursor to fix an issue and it decides to run the dev server, it never considers that I’m already running it and then goes ahead to start a new one on port 3001. Then later it runs another one on port 3002.

Why not just look at the existing terminal processes?

1 Like
2

Furthermore, in a few hours session, I would say Cursor ignore about 10-15% of his own terminal he opened. The prompt just continues with the terminal trying to finish slowly scrolling up. The tool looks confused sometimes in that regard