iOS: Opening a file after an agent edit takes 15+ seconds

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

On Cursor for iOS, after an agent edits a file, opening / loading that file (or reviewing the change) takes more than 15 seconds. The chat often shows “Worked 15s”, and loading the edited file afterward is unacceptably slow for mobile use.

This is especially noticeable on larger diffs (e.g. Review +278 -0).

Steps to Reproduce

  1. Open Cursor on iOS.
  2. Ask an agent to edit one or more files (non-trivial change preferred).
  3. Wait until the agent finishes (UI may show something like “Worked 15s”).
  4. Open the edited file or use Review on the change set.
  5. Observe load time — typically 15+ seconds.

Expected Behavior

Edited files should open quickly (a few seconds at most) after the agent finishes, so iterating on mobile is usable.

Operating System

Other

Version Information

Cursor for iOS (iPhone)
App version: see Profile → scroll to bottom (happy to add exact build if needed)
iOS: current device OS

Additional Information

Screenshots from Cursor iOS show “Worked 15s” in the agent response chrome, and Review +278 -0 for a large edit set where the delay was felt.

Related: filing separately about iOS PR create / Auto-merge failures. Happy to attach PNGs in a follow-up reply.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hi @Netanel Thanks for the forum post, and sorry this is getting in the way of iterating on mobile.

What you’re describing isn’t intended, and it’s not caused by anything in your setup. This is a known issue we’re tracking on the iOS review / file-load path: after an agent finishes a larger edit set, opening the changed files (or Review) can take a long time while the app loads the full change set. Larger diffs make it more noticeable.

One small clarification: the “Worked 15s” pill in chat is the agent’s work duration, not the time it takes to open the file afterward. The slow open/review load is separate, and that’s the issue we’re tracking.

For large changes you may find it more convenient to open the diff on the Cursor web interface on desktop, but I understand this is not an ideal workaround. I’ll keep you posted with any updates.

8

Thanks :folded_hands: