Where does the bug appear (feature/product)?
Cursor CLI
Describe the Bug
cursor-agent repeatedly locks up in two ways that have been hitting me for months
(since at least June 2026), still on latest CLI:
- CPU peg (“pegged”) — process sticks at ~100% on one core, no children, no output.
Often after tools finish. SIGTERM ignored; needskill -9. Stack samples show hot
Array.filter+RegExp.testwith merkle/ignore matching over large trees. - Silent mid-turn freeze — agent just stops. Diagnosed once as HTTP/2 stream drop; I
setnetwork.useHttp1ForAgent: trueon 2026-11-05. Pegs still happen.
I have had to build external kill tooling (wedged-cursor-agents.ts: CPU≥80%, etime≥5m,
no children → SIGKILL) because the CLI does not recover. A CPU watcher is not an
acceptable product fix.
Steps to Reproduce
Intermittent, but highly repeatable over weeks: - Run interactive
cursor-agentin Ghostty (or headless via a long-lived worker /
twist run q) on a non-trivial repo. - Work normally for a while (tools, edits, commits). Large generated trees (e.g.
cdk.outwith 100k+ files) make the peg class much worse; it also happens on ordinary
repos. - Eventually the session stops progressing.
psshowscursor-agentat ~100% CPU with
no children, or the process is idle with no further output. - Attempt soft kill: SIGTERM often ignored. Need SIGKILL.
- Orphaned/stale agents can remain and leave the machine already hot for the next
launch.
Steps to Reproduce
Intermittent, but highly repeatable over weeks:
- Run interactive
cursor-agentin Ghostty (or headless via a long-lived worker /
twist run q) on a non-trivial repo. - Work normally for a while (tools, edits, commits). Large generated trees (e.g.
cdk.outwith 100k+ files) make the peg class much worse; it also happens on ordinary
repos. - Eventually the session stops progressing.
psshowscursor-agentat ~100% CPU with
no children, or the process is idle with no further output. - Attempt soft kill: SIGTERM often ignored. Need SIGKILL.
- Orphaned/stale agents can remain and leave the machine already hot for the next
launch.
Expected Behavior
Agent completes, errors clearly, or times out and exits. No sustained single-core 100%
spin. SIGTERM terminates the process. Indexing/ignore matching cannot busy-loop forever.
Transport failures surface and fail/retry the turn.
Actual Behavior
Pegged cores and silent freezes. Mid-task work lost. External kill scripts required to
keep CLI usable. Today died mid JobRunr YAML commit on a Java monorepo.
Screenshots / Screen Recordings
Can attach Activity Monitor / ps snapshot and a process sample on next peg. Prior Oct 9
peg: ~100% for ~27 minutes; SIGTERM ignored; sample showed Array.filter +
RegExp.test + merkle thrash.
Operating System
MacOS
Version Information
Version Information
CLI Version 2026.11.11-b912975
Latest 2026.11.11-b912975 (up to date)
Model Auto
Subscription Tier Enterprise
OS darwin (arm64)
For AI issues: add Request ID with privacy disabled
Cant its corporate account.
Additional Information
Config already applied without solving it:
approvalMode: unrestrictedsandbox.mode: disablednetwork.useHttp1ForAgent: true(since 2026-11-05)- per-repo / shared
.cursorignorefor fat trees
Related public threads: - Regression - cpu spikes to 100% and agent hangs
- High CPU usage on Cursor CLI
Asks:
- Fix pegged-core ignore/merkle thrash with an internal timeout.
- Fix silent mid-turn freezes even with HTTP/1 forced.
- Make SIGTERM reliably kill stuck agents.
- Tell me what dump you want on the next live peg (sample / spindump / agent log).
Does this stop you from using Cursor
Yes - Cursor is unusable