Cursor-agent 2026.01.09-6d4aaf8 broken on mac x64

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Starting today (2026.01.09), cursor-agent stopped working on my mac with the error below.

The error persists after installing from scratch.

The installer output says:

Detected darwin/x64

But there seems to be an arm64 binary in the distribution - pty.node.

The cursor IDE still works for me.
I asked it about this error (model: claude-4.5-opus-high) and this is the reply (abbreviated):

Looking at this error, the problem is an architecture mismatch. Let me break it down:
The Issue
The error message says:
mach-o file, but is an incompatible architecture (have ‘arm64’, need ‘x86_64h’ or ‘x86_64’)
This means:
The pty.node binary in the new cursor-agent version (2026.01.09-6d4aaf8) is compiled for ARM64 (Apple Silicon)
But the process trying to load it is running in x86_64 mode (Intel/Rosetta)
Why It Worked Yesterday
Yesterday you were likely using an older version of cursor-agent. Today, a new version (2026.01.09-6d4aaf8) was auto-updated, and there’s a mismatch between the architecture of the agent binary and how your Cursor app is running.
…
Next Steps
…
If you intentionally need Cursor to run under Rosetta for some reason, then the cursor-agent binaries need to match (x86_64). In that case, this might be a bug in the cursor-agent distribution that should be reported to the Cursor team.

Full error:

avners@avners03-mac ~ % cursor-agent --version > ~/ai/error.log
/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:9589
throw new Error(‘node-loader:\n’ + error);
^

Error: node-loader:
Error: dlopen(/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/pty.node, 0x0001): tried: ‘/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/pty.node’ (mach-o file, but is an incompatible architecture (have ‘arm64’, need ‘x86_64h’ or ‘x86_64’)), ‘/System/Volumes/Preboot/Cryptexes/OS/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/pty.node’ (no such file), ‘/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/pty.node’ (mach-o file, but is an incompatible architecture (have ‘arm64’, need ‘x86_64h’ or ‘x86_64’))
at ../../node_modules/.pnpm/@[email protected]/node_modules/@lydell/node-pty-darwin-arm64/pty.node (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:9589:9)
at webpack_require (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:529596:42)
at ../../node_modules/.pnpm/@[email protected]_patch_hash=8cc7c6b3b59e47c0436b0f2bbb89cec1ced0f8ac0beadc41a2d07016bef0ea46/node_modules/@lydell/node-pty/unixTerminal.js (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:9918:11)
at webpack_require (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:529596:42)
at ../../node_modules/.pnpm/@[email protected]_patch_hash=8cc7c6b3b59e47c0436b0f2bbb89cec1ced0f8ac0beadc41a2d07016bef0ea46/node_modules/@lydell/node-pty/index.js (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:9664:21)
at webpack_require (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:529596:42)
at ./src/bridge/bridge.ts (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:451312:16)
at webpack_require (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:529596:42)
at /Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:497717:75
at webpack_require.a (/Users/avners/.local/share/cursor-agent/versions/2026.01.09-6d4aaf8/index.js:529662:13)

Node.js v24.5.0

Steps to Reproduce

  1. Install cursor-agent on mac with an intel processor
  2. Run the command cursor-agent --version

Expected Behavior

curosr-agent should print its version

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

cursor-agent 2026.01.09-6d4aaf8

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey there.

We’ve had a few reports of this already. I’ve moved your thread into

Thanks!