Debugging project interface issues with Cursor using Java

Discussion
1

Hello everyone,

Recently, I’ve encountered some troublesome issues with Cursor in actual development, and I’d like to discuss them with you to find better solutions. I really appreciate your help.

The issues I find troublesome:

  1. When entering commands in COMPOSER to test an interface, Cursor compiles the project. However, before executing the compile command, I have to manually click once for Cursor to proceed. Is there a way to let Cursor execute the command directly without my confirmation?

  2. I start the project, copy the interface parameters from the AI-generated test cases into Postman, and manually send a request. If the interface fails, I check the error message in the console, manually copy it into COMPOSER chat, let it generate a fix, restart the project, and retry the request. Is there a more automated way, such as having COMPOSER automatically handle the errors without requiring my confirmation?

I even considered finding an official Cursor API that could retrieve console error messages and send them to COMPOSER chat for automatic processing. However, I feel like such an API might not exist.

2

Hey! I believe I have the solutions to both these issues:

  1. You can enable YOLO mode in cursor settings after which you won’t have to click on accept for each tool call that is made in the composer, and it will run the whole thing automatically

  2. I made a VSCode extension exactly for this thing a few days ago: x.com

Although it only supports browser logs and screenshot for now, I’ll be adding support for terminal logs soon so keep an eye on it

Hope it helped. Do lmk if you have any more questions!

3

Wow! This is really cool. Thank you!

1 Like
4

glad to hear you liked it :smile:

Here’s the GitHub if you wanna look at the open source repo: GitHub - saketsarin/composer-web: Cursor extension that forwards frontend errors and screenshots to composer in one-click, making development seamless for you