Cursor iOS Bugs

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Bugs:

  1. When running from Plan → Agent/Build, it doesn’t give the option to change models.

  2. I tried drafting a big plan draft and checked other parts in the app, and it removed the entire chat.

  3. MCP Linear ↔ Cursor not authenticated.

  4. Cancelling Agent mode in cursor after plan mode stops it from giving a prompt to start again.

Steps to Reproduce

  1. Use plan mode in frontier model and try to change to composer 2.5

  2. After entering a chat and it responds, try to enter your response. Then go to other part of Cursor iOS pages, and then go back.

  3. Connect Linear MCP or authroize Linear to connect with Cursor on desktop/website. Then try to use Linear’s commands like, “Implement or plan ABC-123”

  4. Use plan mode in frontier model and try to change to composer 2.5. Then press stop button.

Expected Behavior

Possible solutions:
1)
a) Have similar UI/UX to desktop version to change model type
b) Allow cursor iOS settings to allow default build/agent model. (e.g. I want to use Composer 2.5)

  1. Keep draft text in cache

  2. Linear MCP works across desktop and iOS

  3. Same behavior as Cursor Desktop

Operating System

MacOS

Version Information

Cursor iOS v1.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @ZoellaB!

Thanks for the feedback.

We’re already tracking both of these. Thanks for the report!

Can you share a screenshot of what you’re seeing? We had to push a fix this morning to show MCP servers in-app. Can you try again?

I can’t reproduce this. Could you share a screenshot or a brief screen recording?

Thanks!

Hi Colin, thanks for the prompt response. here are as follows

  1. https://youtube.com/shorts/r7J8oynRvQ0


4) https://youtube.com/shorts/YANudB5R65U

For 4), it seems to come back after a couple of minutes and exiting the app

Re: Linear, there’s a difference between setting up the Linear integration (that lets you tag Linear from Cloud Agents) and having the MCP server be available for Cloud Agents!

For that, I suggest configuring the MCP server from https://cursor.com/agents

Then you can manage your connected MCP servers from the context pane in the iOS app.

I can’t reproduce this on v1.1.0, which should be released soon! Please give it a try once it’s available.

Seems like it has been configured already, maybe I need to try turning it off and on again? Or it might be issue with 3rd party models?

In website:

In Cursor iOS:

I don’t know if a cursor background agent saw this and fixed this straight away, but it seems to have been fixed now and I’m now able to connect it via iOS and website.