We have some scripts that rely on the output of cursor --version
. When my colleagues were running cursor --version, they were getting the desired and expected 3 line version format
1.6.27
d750e54bba5cffada6d7b3d18e5688ba5e944ad0
arm64
However when I was running cursor --version
I was getting
2025.09.12-4852336
A bit of investigation with AI led me to cursor-agent
, if I run ~/.local/bin/cursor-agent --version
it would print out 2025.09.12-4852336
only.
So I moved this symlink with mv ~/.local/bin/cursor-agent ~/.local/bin/cursor-agent.bak
and then retried cursor --version
. When I did this, a brief prompt flashed on the terminal saying cursor-agent couldn’t be found and it is installing. And after that, cursor --version
now prints
1.6.27
d750e54bba5cffada6d7b3d18e5688ba5e944ad0
arm64
as expected.
So my question is: is cursor
cli relying on the existence of cursor-agent? and it is expected that it would use cursor-agent version instead of its own version? What is this cursor-agent and when is it used / hijacking the cursor version?