Cursor ios app mic-record/STT breaks chat composer and requires restart

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

When recording a message using the built in voice recorder. If the voice is more than a minute or so, it frequently loses the message and the chat composer disappears requiring restarting the app.

Happens frequently and very frustrating after having spoken for several minutes. Seems to have started happened in last week.

Steps to Reproduce

Record a voice message on a cloud agent

Expected Behavior

voice gets converted to text

Operating System

Other

Version Information

1.5.0 39006 on ios

For AI issues: which model did you use?

all

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey @tomcomp,

I’ve been looking into the long voice-recording path on iOS. A couple of things that can help in the moment:

  1. Prefer shorter chunks (under about a minute), then review/send before starting another.
  2. If the composer looks stuck, try dragging the handle up or dismissing the keyboard before force-quitting - that sometimes brings Send back without a full restart.

To dig further, could you share:

  1. iPhone model + iOS version (Settings → General → About)
  2. A short screen recording of a failed recording (composer state after you stop dictating) — how to record on iPhone
  3. Whether this is on a new agent composer or an existing chat follow-up

I’ll dig in once I have those.

Hi,
Shorter chunks is not really helpful because i’m explaining quite long vague requests often 3->7m which is having strong results.

Ive tried dragging/swiping in varous directions and sometimes I think I see the top of the composer at the very bottom but had no joy returning it.

ios 26.5.2
iphone 16 regular
happening definitely on follow-ups

will try to provide recording/screenshots later but it’s mostly an empty screen.

This isn’t intended behavior. It’s something we’ve seen before with long dictations, and it’s an issue we’re tracking - I’ll post here when I have an update.

Two things in the meantime:

  1. For long inputs, try your iPhone keyboard’s built-in dictation (the mic key on the on-screen keyboard) instead of the in-app record button - it streams text into the field as you talk, which tends to sidestep this.
  2. Heads-up that once it’s in that state, a restart clears whatever was in that reply box, so there’s unfortunately no way to recover that text afterward. Worth firing off shorter chunks until we have a fix.

If you can grab even a few seconds of screen recording right when it happens, that’d be a big help in pinning it down - no rush, and an “empty screen” clip is still useful.

Hi Mohit,

I have been encountering this bug quite often especially when using voice mode, most often I’m trying to view the content behind and scrolling since the message box has expanded so big that the content of the chat is barely visible.

I’m a web developer not an IOS developer but looks to me like the message box position when showing and hiding on longer messages is being pushed down further and further with each show/hide action.

Perhaps this is due to some calculation of the position of the message box based on the height of the message box content. Might be better if the box position is fixed on the bottom of the screen depending on the keyboard’s open/closed state I have attached two screen recordings in the what I found is that the issues starts when the the content is able to scroll in the message box, and worsens the taller the content is.

Hope this helps, feel free to let me know if you would like more info.

For reference:

  • IOS Version 26.5.2
  • iPhone 17 Pro Max
  • CURSOR V1.5.0 (39006)

Thanks for the video @lky1999 - that’s really helpful. What you’re describing isn’t intended behavior, and it’s an issue we’re tracking.

Two things that can help in the meantime: try dictating with the microphone on your iPhone’s built-in keyboard instead of the in-app record button - it writes into the same composer but tends to avoid the off-screen growth. And if the composer does drift off-screen, dismiss the keyboard first rather than force-quitting, since a restart clears whatever’s in the composer.

I’ll post here when there’s an update.

Thanks for looking into this, Mohit.

+1 — can confirm this on long iOS dictations: after a long recording the sheet/composer sometimes comes back blank and the text is lost. Opening the sheet first then using the mic is more reliable for me.

— Jason Robertson (via Cursor Grok 4.5 High)

Here are some screenshots from issues I’ve had.

Oddly I noticed that it also happens when using the mac’s built in dictation so I wonder if it’s not just voice but also long messages.

With the latest update, Ive found that if I use the topp left chrvon to get back to the top and navigaate around eventually i can get the chat composer to return.

I also have an annoying problem on the desktop app where when I dictate a long message and press the tick to finish but forget to submit, if I switch to another chat and return, it’s gone - this is very annoying!

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

When typing or using speech to text, if a user clicks out of the text box, then clicks back in, the text box goes invisible. Still interactable but invisible. Requiring an app close and reopen that deletes all text.

Steps to Reproduce

Press the voice to text button. Talk. Click off the text box, then click back on or select the voice to text button again. Repeat until text box goes invisible. Happens for me immediately.

Expected Behavior

I should be able to see the text box and edit the text.

Screenshots / Screen Recordings

Operating System

Other

Version Information

iPhone 15. This is super glitchy and off the screen so I can’t edit this properly without exiting out of the entire report window.

Additional Information

This page is a bit glitchy so I can’t return to cursor to get that information about my device model without it deleting everything in the chat.

I’m on an iPhone 15.

Does this stop you from using Cursor

Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor

I see this as well, and it happens both when I use the cursor dictation option as well as the iOS dictation option to type into the text box. Very frustrating to have no way to submit or recover everything you said/typed.

I’ve discovered that when broken, if you navigate to another conversation that has an open PR and click on the PR and then return to existing chat, the composer re-appears with the text you entered and you can copy/submit it.

Sometimes trying to edit causes it to break again.

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

When recording an audio message, after clicking the stop button to cut the recording, the message composer disappears. Sometimes just the keyboard shows, sometimes there’s nothing. Either way, the message disappears with no way to send.

Steps to Reproduce

With the composer collapsed, no keyboard visible, record a long message (1-2 min) and then click stop. Sometimes it succeeds, sometimes everything disappears.

Expected Behavior

Message box should never fully disappear.

Operating System

iOS

Version Information

Cursor v1.7.0 (39031)

Does this stop you from using Cursor

Yes - Cursor is unusable

But at least you could copy it and paste it first before it breaks further and not lose your work

Thanks everyone for the reports and the detail here. This is an issue we’re tracking,

Workaround that holds best for now: use your iPhone keyboard’s built-in dictation (the mic key) instead of the in-app record button, which streams text in as you talk so nothing’s lost on stop. And if the composer does vanish, before force-quitting try switching to another conversation and back. A few of you found it comes back with the text intact that way, whereas a full restart clears the draft (thanks @tomcomp for surfacing that one).

Improvements are in progress, I’ll post here when they land.

Switching to another conversation alone isn’t a very reliable method - if you switch to one with a PR and click on the PR and then return it is better.