Using the wrong tool /bin/bash in Windows env

[Snax1210]

When using the plug-in, the /bin/bash tool is automatically called, causing a loop.

Related logs:

ENOENT: no such file or directory, uv_spawn '/bin/bash'

[Snax1210]

By the way, this problem consumes very extra tokens and even triggers usage limits when performing complex tasks

[Nomadcxx]

Hey mate, thanks for the report.

I found the issue: our bash / shell tool was falling back to /bin/bash, which obviously breaks on Windows and can cause the loop/token burn you were seeing.

I've pushed a fix and published it as @rama_nigg/open-cursor@2.4.1.

Could you update and give it another go? If it still happens, send through the latest logs and I'll take another look. If the issue is not resolved, I'll re-open this one.

[Snax1210]

This issue caused me to consume 300 million tokens in half an hour, but I will try it

[Snax1210]

This problem has been solved, but I found that there will be two times for each output. If the agent creates a subagent based on the output, it will cause redundant work. This may be another reason for consuming a lot of extra tokens. @Nomadcxx

[Snax1210]

I created a PR to fix this #71