Cursor iOS Agents Live Activity shows Waiting while agent is actively working

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

On Cursor iOS, the Agents Live Activity / lock-screen summary can show an agent as Waiting (e.g. summary “1 working · 1 waiting”) even though opening that agent shows it is actively working with nothing for the user to wait on.

Example agent (consistently mislabeled Waiting while always Working when opened):

Agent name shown on lock screen: “OW: sync fleet cloud-agent templates”

Hypothesis from reporter: status may flip to Waiting because follow-up messages were queued, even though the run itself is still executing and the agent UI shows Working with no pending user action.

Steps to Reproduce

  1. On Cursor iOS 1.9.0 (39064), start or keep a Cloud/Background Agent running (example: https://cursor.com/agents/bc-01a0c596-287c-7142-a625-019878d41f61).
  2. Optionally queue one or more follow-up messages while it is running.
  3. Leave the app / look at the lock-screen Agents Live Activity (or the “N working · M waiting” summary).
  4. Observe the agent listed as Waiting (duration keeps increasing).
  5. Tap into the same agent — it shows Working and there is nothing to wait on.

Expected Behavior

Live Activity / Agents summary status should match the agent’s real state. If the agent is executing work, it should show Working (or equivalent), not Waiting. Queued follow-ups should not mislabel an actively running agent as Waiting unless the product truly needs user input.

Screenshots / Screen Recordings

Operating System

iOS

Version Information

Cursor iOS app: 1.9.0 (39064)
IDE/CLI: n/a (reproduced on Cursor iOS Agents Live Activity)

For AI issues: which model did you use?

n/a — UI status bug, not model output

For AI issues: add Request ID with privacy disabled

Request ID: unknown — UI status mismatch; no Copy Request ID from Live Activity
Background Agent id: bc-01a0c596-287c-7142-a625-019878d41f61
Share Data on for this ID: unknown

Additional Information

  • Search found no existing Bug Report for iOS Agents Live Activity incorrectly showing Waiting while the agent is Working. Closest adjacent (different product): Grok Bot delegated agents running while parent appears idle — not this surface.
  • Gap: exact iOS version not captured.
  • Somewhere else: Cursor iOS app — Agents Live Activity / lock screen

Related links (adjacent only; no exact duplicate found):

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @jsolly,

That’s not intended and it’s not anything on your end. Going forward, when a plan is ready, tap the Build button to kick off the work instead of typing “go ahead” - continuing a plan by typing can leave the agent stuck in the “waiting” bucket on the lock screen even while it’s actually running. We’ve let the team know.

One thing from your screenshot: the amber “waiting” dot is actually on Central furnace system, while OW: sync fleet cloud-agent templates is showing the working indicator. Could you open Central furnace system and confirm it’s also Working with nothing pending - and were both started in Plan mode and continued by typing rather than tapping Build? That’d confirm what I’m seeing.

Thanks @mohitjain — checked both.

You’re right on the screenshot: the amber Waiting indicator was on Central furnace system; OW: sync fleet cloud-agent templates was showing Working.

Central furnace system

  • It was Plan mode, and I continued with a typed message (not Build) — that matches what you described.
  • It’s Done/archived now, so I can’t re-open the live Waiting state from Sep 21. At the time I was tapping in, there was nothing pending for me (no approval / no user action), which is why Waiting felt wrong even if the bucketing was on this agent rather than OW.
  • URL: https://cursor.com/agents/bc-01a0c596-287c-7142-a625-019878d41f61

OW: sync fleet cloud-agent templates

  • Also Done/archived now.
  • In what’s left of the transcript I didn’t find a Plan card / Build continuation (page renderer was flaky scrolling history); there was at least one typed follow-up.
  • Correction on IDs: the agent link in the OP (bc-01a0c596-…) actually resolves to Central furnace system. OW’s id is bc-968bf696-eba6-5104-acca-2954bdab2b67 → https://cursor.com/agents/bc-968bf696-eba6-5104-acca-2954bdab2b67

I’ll use Build when a plan is ready going forward. Appreciate the workaround and the heads-up to the team.