[Bug]: Cursor Provider Use All Process When Enabled

[griiettner]

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

I was waiting for so long the release of Cursor integration, because on my corporate laptop I have access only to Cursor and Cursor CLI. Today I went to try, but unfortunately I could no use.

As soon I put the switch to on, the computer almost froze and I went to check and I could see cursor processes taking a lot of resource. Took me a while to get back to T3 settings. When I disable it, everything went back to normal.

Expected behavior

To be able to use Cursor Provaider

Actual behavior

When It is on, it takes too much process and the computar almost freezes

Impact

Blocks work completely

Version or commit

0.0.22

Environment

macOS Tahoe 26.4.1

Logs or stack traces

I can not take it, because it is on a corporate laptop.

Screenshots, recordings, or supporting files

No response

Workaround

I could not find any workaround

[AspectHeat]

I am having the same issue on Linux, my cursor provider, it spawned 5 child processes all calling cursor on the same file. Each process consumed ~78% CPU individually (~390% total), ran for over 41 minutes without completing, and could not be stopped by killing the parent, they had to be force-killed with SIGKILL.

Version:
0.0.23

Actual behavior:

• T3 Code server (PID 3105) spawned 5 processes: /bin/sh ~/.local/share/../bin/cursor
• Each child ran at ~78% CPU with state R (actively running, not blocked)
• Processes persisted for 41+ minutes with no sign of completing or failing
• When parent process (3105) was killed, the 5 children became orphans and continued running at full CPU — required kill -9 to terminate
• System effects: CPU reached 74°C, fans hit 5000 RPM, battery drained despite USB-C charger connected (system power draw exceeded charger supply)