Skip to content

[Feature]: Use Cursor's official "agent" command as the default instead of "cursor-agent" #41185

Description

@iskw9973

Problem or use case

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.
image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions