Tool CLIENT_SIDE_TOOL_V2_RUN_TERMINAL_COMMAND is not supported in this client

Discussion
1

I used to be able to run terminal command in the composer, but now I cannot, showing:

Tool CLIENT_SIDE_TOOL_V2_RUN_TERMINAL_COMMAND is not supported in this client

as shown in the screenshot:

Reload Cursor window cannot fix it.
However, if I open a new Composer, I can run the terminal commands prompt by LLM as able to run again even in the newly available YOLO mode.

So it’s not a big problem, but something that the Cursor team should look into to see why is it happening.

Version: 0.44.3
VSCode Version: 1.93.1
Commit: 4cabe4501c19546ecce8b6afbf17d76b743bf410
Date: 2024-12-18T20:45:11.019Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.2.0

1 Like
2

same here

3

Could you share a request id for when this happens:

cmd+shift+p > report ai action > select the composer action > copy

Make sure privacy mode is (temporarily) disabled before the request in order for us to see error logs.

4

thank you. same here, for me the agent terminal commands stopped working with the update, and it shows this error:

Tool CLIENT_SIDE_TOOL_V2_RUN_TERMINAL_COMMAND is not supported in this client

here is the request id you requested from when I ran it with privacy mode temporarily disabled:
a4d1aec1-1bdd-4c54-af32-db5fddc8e317

and thank you very much @Terry for the advice to open a new Composer, that fixes it

1 Like
5

And here we go… another update, another day of issues reporting

Same here. Tool CLIENT_SIDE_TOOL_V2_RUN_TERMINAL_COMMAND is not supported in this client

e001dc92-1472-445c-bebb-8305d83dc45f

By the way, all was working at the minute before I update cursor…

1 Like
6

I have the same issue. Action id: 40c06502-a906-4056-9f25-35c8602af857

7

Hey, it seems like the terminal command that the agent wanted to run might have had new lines in, which we block to ensure the AI doesn’t write something you don’t intend for it to run!

If you get this frequently, send over a screenshot with an example of the prompt that causes this, and we’ll look into it!