Cursor-agent create-chat hangs indefinitely after outputting chat ID

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

The cursor-agent create-chat command successfully outputs a chat ID to stdout but the process never terminates. It must be manually killed (SIGTERM/SIGKILL).

Steps to Reproduce

CURSOR_API_KEY=‘<your_key>’ cursor-agent create-chat

Outputs: a486e926-54e5-4adb-b6da-e50f636aac7d

Process hangs - never exits

Expected Behavior

Process exits with code 0 after printing the chat ID.

Operating System

MacOS

Version Information

2026.02.27-e7d2ef6

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
Cursor Cloud Agent Not Shown in Agents Dashboard
3

Hey, thanks for the report.

I tried reproducing this, but create-chat exits normally on my end. A few things to check:

  • What does cursor-agent about show? The full output would help.
  • Do other quick commands like agent ls or agent status also hang, or is it just create-chat?
  • Are you running it inside another process like Docker, tmux, or a script, or directly in a terminal?

This will help narrow down whether it’s environment-specific.

1 Like
4

CLI Version 2026.02.27-e7d2ef6
Model Claude 4.5 Opus
OS darwin (arm64)
Terminal vscode
Shell zsh

agent ls and agent status also hang

5

If I use 2026.02.13-41ac335 version works fine

6

Useful info: the fact that it works fine on 2026.02.13 but breaks on 2026.02.27 clearly points to a regression.

This matches a similar report where --print was also hanging. I passed it to the team along with your bisect, no specific ETA yet.

As a temporary workaround, you can wrap the call with timeout, for example:

timeout 30 cursor-agent create-chat

Or roll back to 2026.02.13 since everything works there.

Let me know if anything changes.

9

Hey thanks for the response but i was trying to download a previous version of cursor cli but i cant download directly. Do you have specific download option ???

10

How to roll back cursor-agent to a previous version:

Previous versions are stored locally at:

~/.local/share/cursor-agent/versions/

List available versions:

ls ~/.local/share/cursor-agent/versions/

There are two symlinks you need to update (both in ~/.local/bin/):

# Check which symlinks exist
ls -la ~/.local/bin/cursor-agent ~/.local/bin/agent 2>/dev/null

Point both of them to an older version:

ln -sf ~/.local/share/cursor-agent/versions/<VERSION_FOLDER>/cursor-agent ~/.local/bin/cursor-agent
ln -sf ~/.local/share/cursor-agent/versions/<VERSION_FOLDER>/cursor-agent ~/.local/bin/agent

For example, to roll back to the build from February 13:

ln -sf ~/.local/share/cursor-agent/versions/2026.02.13-41ac335/cursor-agent ~/.local/bin/cursor-agent
ln -sf ~/.local/share/cursor-agent/versions/2026.02.13-41ac335/cursor-agent ~/.local/bin/agent

If you already have a terminal open, clear the zsh path cache:

hash -r

Verify:

agent --version
cursor-agent --version
11

Is there a way to install an older version from CI/CD jobs?

12

At the moment, there’s no official way to install a specific version using the installer. The CLI updates itself when it starts.

We know about the hanging bug, and I’ve shared the details with the team.

13

Fwiw I hit the same CLI hanging issue and gave up on the CLI for now. Switched to the Cloud Agents REST API directly instead, which doesn’t have this problem.

I also wrapped it in a terminal dashboard if anyone wants to skip building their own API client: GitHub - ofershap/agents-control-tower: Launch, watch, and command your Cursor agents from one terminal · GitHub

npx agents-control-tower - polls the API every 5s, shows all your cloud agents, lets you launch/stop/delete from the keyboard.

Works around the CLI regression since it never touches cursor-agent. recommending u to chk it out