You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Use Cursor's official "agent" command as the default instead of "cursor-agent" #41185
Cursor's official command is agent. Orca's settings default and launch command are still cursor-agent, which Cursor now treats as a legacy alias.
Cursor's installer (https://cursor.com/install) creates agent and cursor-agent as symlinks to the same binary and labels them primary: agent, legacy: cursor-agent. It tells the user to run agent.
In Orca's agent settings, the Cursor row shows cursor-agent as the command, and Orca launches cursor-agent.
On a machine where cursor-agent is not on PATH, the launch fails.
Settings (Orca set to Japanese): the Cursor row shows cursor-agent.
Proposed solution
Show agent as the default, and at launch use the first command the host has: agent, then cursor-agent.
The lookup has to run on the host that launches the agent, including SSH and WSL hosts. Replacing the default string alone breaks hosts that only have cursor-agent.
Alternatives or additional context
Not in scope: Cursor.app-only installs, where only cursor is on PATH and the agent starts with cursor agent. That is #10189.
I have a small change ready for this and will open a PR once this issue exists.
Activity