Migrating agent chats from one host to another is broken

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the Agents window (not the IDE, but couldn’t find the feature/product for this), the functionality to migrate an agent chat from one host to another (e.g. one remote ssh machine to another) is broken.

It allows to do it, but it hangs on loading without any kind of progress or error thrown.

Steps to Reproduce

Have a chat in one machine, go to cursor agents window, then right click on chat, Move to → another machine.

Then this hangs forever and does nothing

Expected Behavior

Should properly migrate the chat

Operating System

MacOS

Version Information

Version: 3.13.25 (Universal)
VS Code Extension API: 1.128.0
Commit: 31e8d61c448c7472e371505838a0fe34083dad50
Date: 2026-07-28T06:17:45.069Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. Moving between two remote hosts in the Agents Window is a different flow than moving cloud↔local, so I need a bit more info to understand where it gets stuck.

A few questions:

  1. If you connect to the destination machine as a new agent target directly in the Agents Window (no move, just add a new agent on that machine), does it connect normally and quickly? This helps tell if the SSH connection to the destination is hanging, or if it gets stuck on the next step.
  2. Do you ever see any error at all (like “Failed to migrate agent”), or does the spinner just run forever with no text?
  3. Do you have any uncommitted or unpushed changes on the source machine in the branch for this chat?

Small note: moving a chat between two different machines pulls code through the shared origin remote. The agent branch gets fetched and checked out on the destination machine. So if your work on the source machine isn’t pushed to the remote, it might not make it to the destination.

Once you’ve got the info above, send it over and I’ll take the next step. I’ll also reply in the thread if there’s an update.