JetBrains Remote Development can't login cursor acp

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

hey,Dean Rie, I came across this post about the issue where JetBrains Remote Development can’t log into Cursor ACP. I wanted to ask—it’s been 24 days—has this problem improved, or are there any alternative solutions?

Steps to Reproduce

Install Cursor ACP in WebStorm
Open AI Chat
Set agent to Cursor
Send a message
Receive authentication required prompt
Push Cursor Login button

Operating System

Linux

Version Information

Version Information
Goland2026.1 EAP
Build #JBC-261.21849.27, built on February 25, 2026
Built from the branch: 261.21849
Source revision: 9a75b7067a259
Licensed to WebStorm EAP user:
Expiration date: March 27, 2026
Runtime version: 25.0.2+10-b329.66 amd64137.0.17-261-b62
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.X11.XToolkit
Linux 6.17.0-14-generic
Ubuntu 25.10; glibc: 2.42; desktop: GNOME (GNOME Shell 49.0)
Exception reporter ID: 15122531d2f089e-3921-4baf-81b1-f28fa8e602d8
Controller in Remote Development
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 1912M
Cores: 8
Registry:
ide.experimental.ui=true
Non-Bundled Plugins:
com.intellij.plugins.macoskeymap (252.16512.17)
Key Promoter X (2024.2.2)
org.jetbrains.plugins.terminal (261.21849.37)
com.intellij.plugins.mnemonicKeymap (2026.1.1)
com.jetbrains.sh (261.21849.37)
com.intellij.ml.llm (261.21849.27)
String Manipulation (9.16.0)
Current Desktop: ubuntu:GNOME

Does this stop you from using Cursor

Yes - Cursor is unusable

@deanrie rie pls help me

This is a known limitation. ACP doesn’t currently support login in JetBrains Remote Development environments because the cursor-agent runs on the remote host, where it can’t open a browser to complete the authentication flow. That’s why the login button fails immediately.

There’s no fix yet. Our team is aware of the issue and the plan is to support a browserless login flow (where the agent prints a URL you can open manually), but it hasn’t been implemented.

In the meantime, you can try SSH’ing into the remote host and running agent login in the terminal. If the CLI detects it can’t open a browser, it should print a URL you can open in your local browser instead. Once authenticated via the CLI, the ACP session in JetBrains should pick up the credentials. This workaround isn’t guaranteed, but it’s worth trying.

If Remote Development isn’t strictly required, using WebStorm locally would let you log in normally.