Agents Window hides live Remote Control agent until Search — visible on web/iOS

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

A running Remote Control agent shows on cursor.com/agents and in the Cursor iOS app, and tools execute on this Mac, but it does not appear in the Agents Window sidebar under the repo until I use Search. Scrolling the project list does not reveal it. Search for the agent name then surfaces it and it stays in the list.

Worked correctly yesterday (agent listed without Search). Today the sidebar only showed other agents (e.g. “Temp PID tuning test”) until Search.

Steps to Reproduce

Mac: Agents Window, Remote Control ON, /remote-control on a local agent in a GitHub repo.
Confirm agent appears on web + iOS.
On Mac, open Agents Window → expand that repo.
Observe: Remote Control agent missing from list (scroll does nothing).
Agents Window → Search → type agent name → agent appears.

Expected Behavior

Live Remote Control agents for that workspace appear in the sidebar without Search, same as web/iOS.

Operating System

MacOS

Version Information

3.13.25 (Universal)
(your about box need format work)

For AI issues: which model did you use?

composer 2.5, Grok 4.5.

For AI issues: add Request ID with privacy disabled

bcId: bc-c6ecf4ea-d0a0-466f-8ccf-c803ef353a0f

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey there!

When the Agents Window sidebar is set to Group by → Repository, Remote Control agents started this way don’t always land under the repo card, so they can sit in a separate section until you Search. Two quick ways to surface it:

  • In the Agents Window sidebar, switch Group by from Repository to Workspace - the agent then shows under its workspace section.
  • Or, as you found, Search for it and select it, and it stays put in the list.

Whether it lands under the repo card can depend on how the session was started, so this isn’t a sign of lost data - Group by Workspace will show it consistently.

This isn’t intended behavior and it’s an issue we’re tracking. No timeline to share yet, but I’ll follow up here if there’s an update.