Cloud agents triggered by Automations are not visible in the iOS app

[hdmdhr (Daniel)]

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

In the Cursor iOS app, cloud agents that are triggered via “Automations” do not appear in the app’s history or agent list. This happens even when the filter “Customize > Source” is explicitly set to “All”. The agents run successfully, but there is no way to view them on mobile.

P.S. When setting up an automation, if select an environment instead of a repository, then I cannot specify a branch. Is this by design or another bug?

Steps to Reproduce

Set up an Automation that triggers a Cloud Agent.

Wait for the Automation to trigger and verify the Cloud Agent runs successfully (e.g., check via the web dashboard or desktop IDE).

Open the Cursor iOS app.

Go to the Agent/Chat history view.

Ensure “Customize > Source” is set to “All”.

Notice that the automated cloud agent is completely missing from the list.

Expected Behavior

Cloud agents triggered by Automations should be visible in the iOS app’s history when the source filter is set to “All”, mirroring the behavior on the desktop or web platforms.

Screenshots / Screen Recordings

Operating System

Other

Version Information

CURSOR v1.6.1 (39021)

For AI issues: which model did you use?

Grok 4.6

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Colin]

Hey @hdmdhr!

Thanks for the report. This is a known issue with Cursor for iOS. We’re already tracking this issue, and I’ve added your report. It was already reported over here. iOS inbox: Automations source filter shows “No matching agents” despite active automation runs - #6 by kevinn We can update this thread when there’s news.

As a workaround, you can open a specific run via cursor.com/agents/<id> on your phone and it should open in the app. cursor.com/agents also works in mobile Safari.

@hdmdhr

P.S. When setting up an automation, if select an environment instead of a repository, then I cannot specify a branch. Is this by design or another bug?

Choosing a branch for an environment-based automation isn’t supported right now. If you need to specify the branch, you’ll have to pick the repository directly. Git triggers should already fire on the event’s ref. If you’ve got a use case where that isn’t enough, please share it! It helps with prioritization.