**Cloud Agents: Unidirectional Sync Failure & Cross-Platform Feature Disparity**

[Humberto_Garcia]

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

There is a major sync and feature consistency issue between Cloud Agents on Web and the Cursor Desktop App:

Unidirectional Sync: Cloud Agent sessions started from the web or mobile browser do not sync back to the Desktop app (they do not appear in the Desktop Agents panel). However, sessions started in the Desktop app sync properly to the Web.

Feature Disparity: Available options vary depending on where the task was started. For example, “Grind” mode is selectable on Web but missing on Desktop. Model switching works on mobile/web only if the task was initiated on Web, but not if initiated on Desktop.

Inconsistent UI States & Execution: Tasks show varying and confusing status setups (e.g., prompting to “Setup” a cloud environment even for running cloud tasks). Additionally, some agent chats silently fail later or lose accessibility to subagents.

Steps to Reproduce

Sync Test: Go to cursor cloud agents, desktop app, and mobile pwa on android and start a new Cloud Agent task.

Open the Cursor Desktop App and check the Agents/Cloud section → Notice the web task is missing.

Create a Cloud Agent inside the Cursor Desktop App → Check cursor → Notice it appears on the web.

Feature Parity Test: Compare available controls across Web and Desktop for identical tasks → Notice “Grind” mode is present on Web but missing on Desktop, and model switching options differ based on origin device.

Expected Behavior

Full bi-directional sync: Cloud Agents created on Web/Mobile should instantly appear and sync with the Desktop app.

Feature parity: Options like “Grind” mode, model selection, and subagent features should be identical regardless of where the task was launched.

Clear status indicators and reliable session persistence for subagents.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Desktop App: Latest version

Web UI: [cursor agents]

Version: 3.15.6
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
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.291
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Grok 4.5 High

Additional Information

When Cloud Agents and Grind mode work, they are incredibly fast and effective for executing long-horizon tasks planned via Claude Code or Fable. Fixing this cross-platform syncing and option discrepancy will drastically improve the workflow.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[kevinn (Kevin Neilson)]

Hi @Humberto_Garcia Thank you for the post. Regular Cloud Agents do sync both ways. A Cloud Agent started from cursor.com/agents without Long-running should show up in the desktop Agents panel, and agents you start on desktop should show on the web.

The mismatch in your screenshot is a different split. Long-running (also known as Grind) is a web research preview, and those sessions are managed at cursor.com/agents. They do not appear in the desktop Agents panel today, which is why a web-started Long-running task can look like it never synced. The rows labeled Setup are environment setup runs for the cloud VM, not a status glitch on an already-running agent.

Model options and Long-running itself also differ by surface right now for that same reason. Subagent work stays nested under the parent agent rather than showing as its own top-level chat.

If you start a regular Cloud Agent from the web (not Long-running) and it still does not show on desktop, that is something we would want to look at. In the Agents sidebar, search for the agent by name, and in the Source filter confirm Web is ticked. If you still feel like you’re missing things, the next thing to do would be to check your filters and make sure that you exposing cloud based agents in the Agents View.