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