Default Cursor binary to `cursor-agent` to avoid Grok agent collision

[Aditya190803]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

1. Install both Grok CLI and Cursor Agent CLI on the same machine.
2. Ensure Grok's agent binary appears earlier on PATH than Cursor's CLI. For example:
   • which agent resolves to Grok (e.g. /home/adi/.grok/bin/agent)
   • which cursor-agent resolves to Cursor (e.g. /home/adi/.local/bin/cursor-agent)
3. Enable the Cursor provider in T3 settings with the default binary path:

   "cursor": {
     "enabled": true,
     "binaryPath": "agent"
   }

4. Start the dev server (bun dev) and let provider discovery run on startup.

Expected behavior

Cursor provider discovery should invoke the Cursor CLI and complete ACP model discovery successfully. cursor-agent about and cursor-agent acp work when run directly.

Actual behavior

T3 runs agent acp for Cursor discovery, which resolves to Grok's agent binary instead of Cursor's. Startup logs show:

Cursor ACP model discovery failed { errorTag: 'AcpTransportError' }

Cursor provider checks fail even though the Cursor CLI is installed and working under cursor-agent.

Impact

Major degradation or frequent failure

Version or commit

main @ db323df (also reproduced on feat/provider-usage-limits)

Environment

Linux (CachyOS), Bun, Cursor provider enabled with default binaryPath: "agent", Grok CLI installed

Logs or stack traces

Cursor ACP model discovery failed { errorTag: 'AcpTransportError' }

Screenshots, recordings, or supporting files

No response

Workaround

In T3 Settings, set Cursor binary path to cursor-agent (or the full path to the Cursor binary, e.g. /home/adi/.local/bin/cursor-agent).

Happy to open a separate PR if useful. Suggested fix: default Cursor to cursor-agent and optionally map legacy "agent" to cursor-agent for existing configs.

[Aditya190803]

Could a maintainer add the bug and needs-triage labels? This was filed via CLI rather than the bug report web form, so the template labels were not applied automatically. I do not have permission to add labels on this repo.