Interpreter isn’t working
1 Like
Bump:
It says it’s going to execute a command and then it doesn’t do anything.
1 Like
It might be helpful to include system info and and check for any error messages or error logs.
Copy/paste system info from:
Cursor > Help > About
Open developer tools via:
Cursor > Help > Toggle Developer Tools
and then click Console and see if there are any related errors when using interpreter mode.
On Windows, you can find logs here:
C:\Users\<your-user-name>\AppData\Roaming\Cursor\logs
This is the parent folder of the folder that is opened when doing:
-
Ctrl+Shift+P(to open command palette in Cursor) -
Typing and selecting
Developer: Open Logs Folder
And any crashes can be reported via these steps:
My Cursor has the same behaviour.
2 Likes
What do you mean by “interpreter”?
Probably ‘Interpreter Mode’ in Ctrl + L.
what does interpreter mode actually do.
I get the documentation, but curious if anyone’s had any real experience with it and can share some real user feedback.
I’m noticing more and more things about cursor that are prematurelly hyped or under tested, but as with most things online, not talked about much, so the reality is quite different.
e.g. cursor stops applying code, violates the cursorrules files, changes functional code against explicit instruction and creates sytax and formatting issues.
Its a EXCELLENT product - but as it’s new, in developing, flawed.
Rant over - so…interpreter
I’ve never been able to utilize the interpreter properly, it messed up files, batch editing didn’t work. I used it for converting English to terminal commands before I found out it can be done via the terminal prompt. So I do not regret much it was removed, because the utility I wanted to use it for wasn’t functional.