After closing the Cursor IDE on Linux Mint 23 (latest version), I still see many Cursor-related processes running in the Task Manager/System Monitor. Is this expected behavior, or is it a bug?
To me it’s clearly a bug, but maybe I’m wrong…
Steps to Reproduce
Close the IDE
Expected Behavior
Obviously no Cursor related tasks in the Task Manager
Hey, thanks for the report and the screenshots. I can see a list of cursorsandbox processes that stay around after you close the IDE.
Let me split what’s expected vs what isn’t:
While Cursor is running, seeing multiple cursorsandbox processes is expected. They’re used by the agent terminal, the sandbox for shell commands, and they can stay alive between commands.
But they should not remain after you fully quit the IDE. This isn’t caused by anything in your setup.
Good news is these leftover processes are idle, almost 0% CPU and a couple MiB each, so they aren’t doing any harm, and it’s safe to kill them manually:
pkill -f cursorsandbox
In the past, on some Linux builds they couldn’t be killed and you’d see Permission denied due to AppArmor. That’s been fixed in recent versions, so the command above should work without sudo.
I’ve already passed on the fact that they don’t get cleaned up on exit and we’re tracking it. I can’t share a timeline yet, but I’ll post here if there’s an update. If the processes come back after pkill while Cursor isn’t running, let me know, that’s a different case.
