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)
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:
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.
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.
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.
Hey @cdtl22, @Wilbur_Pollinador. Over the last few months we’ve shipped a bunch of CLI performance improvements, especially around startup CPU usage and hangs during indexing, including cases with .git and containers. The current stable CLI release is 2026.08.11-e8db854, which is several versions newer than the one you reported on.
Please try the latest version:
curl https://cursor.com/install -fsS | bash
agent about
If CPU still spikes to 100% or the agent still hangs on the current version, please start a new thread with fresh details like the version from agent about, your OS, your exact container setup, and steps to reproduce so we can take a clean look. I’m going to close this thread for now.