Cursor CLI is entirely broken via SSH

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Cursor CLI does not work via SSH session anymore, at all.

Steps to Reproduce

  1. SSH into computer
  2. cursor-agent login
  3. Follow link in browser, approve login
  4. See this at terminal:
Failed to store authentication tokens: Security command failed: Security process exited with code: 36

Repeat same process on the computer directly without ssh, and login works fine.

  1. SSH into computer
  2. cursor-agent --api-key ...
  3. CLI will exit with code 1 immediately with no output

Expected Behavior

It should be possible to use cursor when SSHing into computer.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

$ cursor --version
2025.11.06-8fe8a63

Does this stop you from using Cursor

Yes - Cursor is unusable

3

I’ve managed to work around this by starting a terminal session in tmux/zellij on the computer locally, and then joining it from the ssh session. If the terminal session is created first by the ssh in, cursor can’t seem to access auth.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.