Unarchived cloud agents disappear from the Agents sidebar after a couple of days of inactivity

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have a few hundred cloud agents on one repo. Most are archived runs created through the API on a schedule; about 30 are unarchived.

On desktop, once an unarchived agent sits idle for a couple of days, it drops out of the Agents sidebar. More does not bring it back, and searching the exact title does not find it either. The agent still exists if I open it by URL.

It looks like the sidebar only shows the most recent 100 agents, including archived ones, sorted by last activity, and does not load anything older. With a lot of archived API history, older unarchived agents fall off the list.

I hit this with an unarchived agent that had been idle since July 11. It was missing from the sidebar and Search. After I posted a follow-up in that thread, it showed up again right away.

cursor.com/agents does not have this problem once API is enabled under Filter > Source. The web list seems to leave archived agents out of that same window, so my unarchived set still fits.

Related iOS note: agents I archived a few minutes earlier still showed up with the Archived filter off.

Steps to Reproduce

  1. Have well over 100 cloud agents on a repo, mostly archived API runs, plus some unarchived ones.
  2. Leave one unarchived agent idle for a few days.
  3. Open the Agents sidebar: it is gone. Click More: still gone. Search the exact title: no Agents hit.
  4. Open the agent by direct URL: it still exists and is active.

Expected Behavior

Unarchived agents should stay reachable in the desktop app, either by paging the list or by not counting archived agents against the same window.

This looks similar to the limited-window sidebar issue discussed here: Cloud Agents do not show in Agents' recent Agents sidebar

Related: Cloud Agents do not show in Agents' recent Agents sidebar

Operating System

MacOS

Version Information

Version: 3.12.17, commit 0fb762053c34788bb7760d5673f8a6d4c8589d50, build date 2026-07-17

macOS 26.5.2 (also seeing the limited list on the current iOS app)

For AI issues: which model did you use?

n/a (Agents sidebar / list UI issue)

For AI issues: add Request ID with privacy disabled

Example unarchived agent that dropped out until a follow-up bumped activity: bc-3c97ba20-4df8-49c9-a00c-628609f9b7e5

Additional Information

Also seeing a limited recent list on Cursor for iOS.
Web dashboard (cursor.com/agents) looks fine once API is enabled under Filter > Source.
Pinning and the web dashboard work around it on desktop.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hi @rcbeall17 Thanks for the forum post! Your read on what’s happening is spot on.

The desktop Agents sidebar currently loads only a limited window of your most recently active agents and does not page beyond it. Archived agents count against that same window, so with a large backlog of archived API runs, an unarchived agent that has been idle for a while can slip past the end of it. Once that happens it also drops out of the sidebar’s search, since that search only looks at agents already loaded. That is also why posting a follow-up brought it back instantly: the new activity pushed it back into the loaded window.

This is a known limitation, and we are tracking it internally. The direction is proper paging and full search in the desktop sidebar, so heavy users are not cut off at the window boundary. I do not have a timeline yet, but your report is a great, concrete reproduction that I’ve added to our internal tracking.

A few things that should keep those agents reachable in the meantime (most of these you’re already aware of):

  • Pin the unarchived agents you want to keep in view. Pinned agents stay in the sidebar even when they would otherwise fall outside the window. You already noted this works, and it is the most reliable workaround today.
  • Use cursor.com/agents with API enabled under Filter > Source. As you found, the web list excludes archived runs by default and pages through the full set.
  • Opening an agent by its direct URL always works, since the agent itself is unaffected - this is purely a list and window issue.