I’m encountering an issue with the Cursor Agent/CLI on my Raspberry Pi 5 (ARM64).
The installer completes successfully, but running cursor-agent results in the following error:
/home/XXX/.local/bin/cursor-agent: line 11: /home/XXX/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/node: cannot execute: required file not found
Same with agent.
The file seems to exists: file /home/XXX/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/node returns:
/home/XXX/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/node: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=2dea07b258a04d58186d4f0943c77d33f3a79e9b, for GNU/Linux 3.7.0, with debug_info, not stripped, too many notes (256)
I have a very vanilla Raspberry Pi 5 setup: Raspbian 12 bookworm, kernet 6.12.47+rpt-rpi-v8, aarch64. The installer successfully detected the architecture (Detected linux/arm64)
My node version is v18.20.4, but I installed it in order to solve this (spoiler, it didn’t) since I’m using node in containers.
Could you please help resolve this issue, maybe there is a compatibility issue with the architecture? Let me know if you need further details.
Thank you!
Best regards,
Olivier
Steps to Reproduce
SSH connection to a raspberry pi 5 with raspbian.
Installing Cursor: curl https://cursor.com/install -fsS | bash
Trying to run cursor: cursor-agent
Expected Behavior
Cursor agent is returning an error instead of running.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
I believe this is a dependency error specific to the dynamic loader, even though the binary file itself is present and correct for ARM64. When an executable throws “cannot execute: required file not found,” it usually indicates that the dynamic linker cannot locate one of the core shared libraries required by the bundled node binary. I suggest running ldd on that specific node path (e.g., ldd /home/XXX/.local/share/cursor-agent/versions/…/node) to identify which library is missing, as you may need to manually install standard runtime packages like libstdc++6 on your Bookworm installation. This often resolves issues where pre-compiled binaries are missing common library references.
Hello @Rao_Athar, thank you very much for your reply!
Indeed, it seems that you are on point.
I’m struggling with some libgcc some libraries are missing and due to some unmet dependencies I’m having issues to install them.
I’ll take some time to try to fix that and I’ll come back if I’m stuck.
Thanks again!
No worries at all, Oruas! Glad to hear the suggestion was helpful.
For those libgcc and unmet dependencies, I suggest trying sudo apt --fix-broken install first—it often clears up those configuration blocks that prevent new installs. Also, it’s worth double-checking that your Raspberry Pi OS is actually the 64-bit version (uname -m should show aarch64), as 32-bit environments can be very finicky with these specific Node binaries.
Let us know how it goes after the ‘fix-broken’ command, we are here to help!