[Bug]: Can't connect to Cursor

Before submitting

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

Area

apps/desktop

Steps to reproduce

Suspected issue:
T3 calls cursor/list_available_models, but current Cursor ACP exposes models through session/new.

T3 Code 0.0.33, latest available
Cursor CLI: 2026.03.20-44cb435
Binary: /Users/macuser/.local/bin/cursor-agent
cursor-agent status: authenticated
cursor-agent models: works

Direct ACP:
initialize -> authenticate(cursor_login) -> session/new: succeeds, returns 32 models
cursor/list_available_models: JSON-RPC -32601 Method not found

T3 diagnostics:
checkCursorProviderStatus -> AcpRequestError
Trace: 68cc4c6a2e6537681316f69c09b160c5

Expected behavior

That it "see" / connect to the running and authenticated Cursor instance (Mac OS desktop).

Actual behavior

Cursor
Early Access

Needs attention

• Could not verify Cursor Agent authentication status. Cursor ACP model discovery failed. Cursor CLI setup may be incomplete; install or enable the Cursor CLI, restart T3 Code, and try again. See https://cursor.com/docs/cli/installation. Check server logs for ACP details.

Impact

Major degradation or frequent failure

Version or commit

0.0.33 (3b72d17cbca6)

Environment

mac OS Tahoe

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

None found

Start at the checkCursorProviderStatus path and trace the AcpRequestError using diagnostic trace 68cc4c6a2e6537681316f69c09b160c5. Compare the current cursor/list_available_models request with the reported session/new response from the Cursor ACP. Done means T3 Code can verify the authenticated Cursor instance and discover its models without the -32601 error.