Regression - cpu spikes to 100% and agent hangs

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

cpu spikes to from 6% to 100% using a simple prompt despite no other changes to environment (must be due to latest version - wasnt an issue before on 2026.03.20-7da3412)

Steps to Reproduce

agent --version                                            
2026.04.13-a9d7fb5

agent --model "auto" --stream-partial-output --output-format stream-json --print "hello there"                                              
{"type":"system","subtype":"init","apiKeySource":"env","cwd":"/","session_id":"1e
b13ef1-5811-48cf-aa9c-6ed8310729b4","model":"Auto","permissionMode":"default"}   
{"type":"user","message":{"role":"user","content":[{"type":"text","text":"hello t
here"}]},"session_id":"1eb13ef1-5811-48cf-aa9c-6ed8310729b4"}                    
^C                                                                               
Aborting operation...

Expected Behavior

cpu should not be at 100% and agent should not hang

Operating System

Linux

Version Information

2026.04.13-a9d7fb5

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

n/a

Does this stop you from using Cursor

Yes - Cursor is unusable

these regressions seems to come out when a new version is released. can we please test for breaking changes before rolling things out - seems to be occurring more frequently now

Hey, thanks for the report. This is a known CLI issue that shows up from time to time after updates. I’ve shared it with the team, including the regression details between 2026.03.20-7da3412 which works and 2026.04.13-a9d7fb5 which is broken. There’s no ETA for a fix yet, but your report will help with prioritization.

As a workaround, you can roll back to the previous working CLI version:

ln -sf ~/.local/share/cursor-agent/versions/2026.03.20-7da3412/cursor-agent ~/.local/bin/cursor-agent

The path may differ depending on how you installed it, so check which cursor-agent and ls ~/.local/share/cursor-agent/versions/.

Let me know if the rollback helped.

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

New version of cursor CLI (version 2026.04.13-a9d7fb5) becoming unresponsive running 100% cpu .
As soon as the CLI starts it launches multiple threads running index.js, all hitting 100% cpu. CLI is slow and agent is unable to answer simple questions.

Steps to Reproduce

Run a Podman (Docker) container with bind mount for .cursor directory.

#
# Run a Docker (Podman) container with bind mount for .cursor directory.
podman run \
    --rm \
    --tty \
    --interactive \
    ...
    --volume "${HOME}/.cursor:/root/.cursor:rw,Z" \
    ...
    ghcr.io/ivoa/calycopis/developer-tools:2026.04.12 \
        bash
#
# Download and run Cursor CLI inside the container.
curl https://cursor.com/install -fsS | bash

agent

Expected Behavior

Normal behaviour is Cursor CLI ready to respond to commands.
Been running Cursor CLI in Podman containers for couple of months, not had any problems until today.

Operating System

Linux

Version Information

CLI Version 2026.04.13-a9d7fb5
Model Opus 4.6 1M Thinking
Subscription Tier Pro+
OS linux (x64)

Additional Information

Cursor CLI is run inside a Podman container which is triggering SELinux alerts on the host system. “SELinux is preventing bwrap from mounton access on the directory /newroot/proc”.
We have been running Cursor CLI in containers for couple of months and haven’t seen these before, so might be related.

Does this stop you from using Cursor

Yes - Cursor is unusable

I’m running CLI in a new Docker container each time, so I don’t have previous versions in ~/.local.

Is there a way to download and run a specific version using the curl command ?

I would also like to know because I’m also running in docker and dont have access to prior versions

im not able to rollback to prior version because i’m using docker and it’s a brand new instance each time. is there a way to download a specific version? this completely blocks all workflows

Note to people experimenting with this - backup your ~/.cursor directory first.
I tried running an older version, 2026.03.20, by editing the download script before running it, and it worked, but the older version can’t read my session history.
Best to be safe - backup your ~/.cursor directory before experimenting.

hi wilbur, did you download this older version or is there a way to access this via their download cursor script for a specific version?

For what it is worth here is what I’ve tried. It installed the older version, but it couldn’t access my session history so it wasn’t that useful. Need to know the version number and hash code for the version you want.

#
# Download the Cursor install script.
curl https://cursor.com/install -o ~/install-cursor.sh

#
# Check what version this is installing
sed -n '
    /versions/ p
    ' ~/install-cursor.sh

>   TEMP_EXTRACT_DIR="$HOME/.local/share/cursor-agent/versions/.tmp-2026.04.13-a9d7fb5-$(date +%s)"
>   DOWNLOAD_URL="https://downloads.cursor.com/lab/2026.04.13-a9d7fb5/${OS}/${ARCH}/agent-cli-package.tar.gz"
>   FINAL_DIR="$HOME/.local/share/cursor-agent/versions/2026.04.13-a9d7fb5"
>   ln -s ~/.local/share/cursor-agent/versions/2026.04.13-a9d7fb5/cursor-agent ~/.local/bin/agent
>   ln -s ~/.local/share/cursor-agent/versions/2026.04.13-a9d7fb5/cursor-agent ~/.local/bin/cursor-agent

#
# Replace the version number.
sed -i '
    s/2026\.04\.13-a9d7fb5/2026.03.20-7da3412/
    ' ~/install-cursor.sh

sed -n '
    /7da3412/ p
    ' ~/install-cursor.sh

>   TEMP_EXTRACT_DIR="$HOME/.local/share/cursor-agent/versions/.tmp-2026.03.20-7da3412-$(date +%s)"
>   DOWNLOAD_URL="https://downloads.cursor.com/lab/2026.03.20-7da3412/${OS}/${ARCH}/agent-cli-package.tar.gz"
>   FINAL_DIR="$HOME/.local/share/cursor-agent/versions/2026.03.20-7da3412"
>   ln -s ~/.local/share/cursor-agent/versions/2026.03.20-7da3412/cursor-agent ~/.local/bin/agent
>   ln -s ~/.local/share/cursor-agent/versions/2026.03.20-7da3412/cursor-agent ~/.local/bin/cursor-agent

#
# Run the install script.
source ~/install-cursor.sh

agent about

>   About Cursor CLI
>   
>   CLI Version         2026.03.20-7da3412
>   Model               Opus 4.6 1M Thinking
>   OS                  linux (x64)
>   Terminal            unknown
>   Shell               unknown
>   User Email          Not logged in

Suggestion to the Cursor team - please leave the entries for a couple of previous versions commented out in the install script to make it easier for users to roll back when a problem occurs.

This would be useful

hi @deanrie is there a way to prevent/disable updates for the cli. assuming i have the old version, after i run a prompt it automatically updates to april 13 and the same issue happens all over again.

$ ls -ld $(which agent)
Mar 20 22:25 /home/asdf/.local/bin/agent → **/home/asdf/.local/share/cursor-agent/versions/2026.03.20-7da3412/cursor-agent

(this prompt runs successfully)**

–
after running a prompt, i see:

$ ls -ld $(which agent)
Apr 15 01:46 /home/asdf/.local/bin/agent → **/home/asdf/.local/share/cursor-agent/versions/2026.04.14-ee4b43a/cursor-agent

(this prompt fails)**

—

even if i update User/settings.json, the update still happens:

{
    "update.mode": "none"
}