Skip to content

[Bug]: High CPU usage when app is open (macOS) #2646

Closed

Description

@Jacxk

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

Issue occurs after a few seconds of having the app open.

Expected behavior

Normal CPU usage while using.

Actual behavior

A few processes like kernel_task and syspolicyd CPU usage spikes and makes the Macbook run so hot that it turns on the fans.

Impact

Major degradation or frequent failure

Version or commit

0.0.23 (3c32bc8)

Environment

macOS 14.8.3 (23J220)

Logs or stack traces

Screenshots, recordings, or supporting files

Screenshot 2026-05-11 at 11.12.17 AM.png
Screenshot 2026-05-11 at 11.11.50 AM.png
Screenshot 2026-05-11 at 11.13.33 AM.png

Workaround

No response

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on May 11, 2026
  2. Amer-Alic commented on May 12, 2026

    @Amer-Alic

    Same issue here. 30GB+ of system usage crashing my mac

  3. neominik commented on May 12, 2026

    @neominik
    Contributor

    Also see very high battery drain when T3 code (v0.0.23) is open.
    Mostly seems to come from constantly spawning CPU-intensive node processes, not sure what they are doing.
    Image

  4. corbanvilla commented on May 12, 2026

    @corbanvilla

    Same issue here.

  5. corbanvilla commented on May 12, 2026

    @corbanvilla

    Codex thinks it's to do with the new cursor agent... Seems plausible:

    I captured a live process snapshot while T3 Code Alpha was open. The high CPU did not appear to be primarily from the Electron renderer. T3’s bundled server process was spawning multiple Cursor ACP
      agents:
    
      /Applications/T3 Code (Alpha).app/.../apps/server/dist/bin.mjs --bootstrap-fd 3
        -> /Users/.../.local/bin/agent --use-system-ca .../cursor-agent/versions/2026.05.05-84a231c/index.js acp
    
      At capture time, several very new agent ... acp children were using roughly 35-84% CPU each. One hot Cursor ACP child had also spawned:
    
      .../cursor-agent/versions/2026.05.05-84a231c/rg --files --follow --max-depth 16 --no-messages
    
      This makes the issue look like repeated Cursor provider status/model discovery or capability enrichment spawning ACP sessions and triggering filesystem crawls. That would also explain macOS system
      processes like syspolicyd, securityd, Spotlight/mdworker, and kernel_task showing activity, since the child process is walking files.
    
      Potentially relevant code paths from the repo:
    
      - apps/server/src/provider/Layers/CursorProvider.ts
          - checkCursorProviderStatus calls discoverCursorModelsViaAcp
          - enrichCursorSnapshot calls discoverCursorModelCapabilitiesViaAcp
          - CURSOR_ACP_MODEL_DISCOVERY_CONCURRENCY = 4
          - per-model capability probes retry up to 3 times
      - apps/server/src/provider/makeManagedServerProvider.ts
          - runs initial and periodic provider refreshes
      - apps/server/src/provider/Layers/ProviderRegistry.ts
          - force-refreshes newly added/rebuilt provider instances at startup
    
      Recent commits that may be related:
    
      - aa219be7 - port desktop app to Effect
      - 08e6d4cf - Multi-Provider support
      - 3c32bc8 - v0.0.23 release commit
    
  6. venkat2305 commented on May 12, 2026

    @venkat2305
    Image

    I’m facing the same issue on M4 MacBook.

  7. juliusmarminge commented on May 13, 2026

    @juliusmarminge
    Member

    this should fix the high burst of cursor probes: #2428

    new api in the agent cli they added for us so haven't gotten the go-ahead that it's released to GA yet though hence it's sitting and waiting to be merged...

    also looking into how to reduce the background processes when idle

  8. jhack0x commented on May 20, 2026

    @jhack0x

    @corbanvilla @juliusmarminge Thanks, you're lifesavers! My M1 stopped overheating and draining the battery by simply disabling Cursor in Settings > Providers

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

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions