One-tap AI rephrase of the whole text field, with undo
efko DEV ·
From Discord (forum post "Auto AI support", 9 Sep 2026, by E1ement):
Can we have an option to auto input the AI rephrase all the content of the text field? Currently we have to select the AI option, then select the text, then click rephrase, then again click if we want to use it. A single click button to do all this and an undo button next to it would be so helpful. This would also get rid of the autocorrect issues in many cases.
Unmutual added:
Or a long click on the AI button for the options (including undo), with the single click rewriting all. Keeps the number of buttons down!
Request
- Single tap on the AI button: take the entire content of the text field, rephrase it and put the result straight back into the field (no select text → rephrase → apply steps).
- Undo right next to it to restore the original text.
- Alternative layout (Unmutual): single tap = rewrite all, long press = the other AI options incl. undo, so the toolbar doesn't gain more buttons.
Current flow (4 steps)
- Open the AI tool
- Select the text
- Tap Rephrase
- Tap again to apply the result
Expected
- Tap the AI button → whole field is rephrased in place
- Undo available with one tap
Discussion
Sign in to comment or vote.
@Unmutual this is coming in build 427, as a gesture instead of a new button. Swipe down on the spacebar and the whole text in the field gets rewritten by AI right there, no panel, no select/rephrase/apply steps. If you have something selected, only the selection gets rewritten.
While it runs, the suggestion bar shows what it's doing and a tap there cancels it. When it's done the bar says "Rewritten, tap here to restore the original text". That undo stays until you type the next key, 30 seconds max.
It's off by default. In Settings under Gestures, "Swipe down on the spacebar" is now a choice: Nothing / Hide keyboard / AI rewrite (Pro, same as the hide option). Below it you pick the AI action: last used, or always Rephrase, Fix grammar, More formal or More casual.
It needs the suggestion bar visible, otherwise there's nowhere to show the undo. And if the field changes while the AI is working, I don't touch anything and offer to copy the result instead, so it can't mangle half a message.
That sounds amazing. Can’t wait to try it
This seems a little glitchy for me at the moment. Undo isn’t consistently showing and when it does and I select it, I’m sometimes getting an error with an option to paste.
Heading out for a bit but will get some logs up later
Please use the button above to send me a proposal for a status change - I'll notice sooner that it's not OK :)
An example of undo not showing
Yes, I've seen the same thing, sometimes the button just doesn't appear.
@Unmutual @Garux the video showed it exactly. The rewrite went through, but the suggestion bar refreshed right after and wiped the undo note before you could see it. Fixed for build 428: the "Rewritten, tap here to restore" note now stays until your next keystroke or 30 seconds, whichever comes first.
The error with the copy option is a separate thing and I couldn't pin it down yet. Your log doesn't record what happens on undo, so 428 now logs why a restore gets refused. If it shows up again in 428, send me a diagnostics export right after and I'll see which case it is.
@efko So that worked fine. 🙂 I’m getting an error when trying to use AI here though. Might be a website issue? Video attached.
Take a screenshot for me of how you have rephrase set up - in my opinion you have FIX there - and there's nothing to do there ;) Try changing it to Formal..
@efko Nah it’s not that. It happens regardless of what I type here. I had it on rephrase. Changed to formal with the same outcome.
Using the same text in the messages app works fine.
Diagnostics attached.
Try it in another application, if it doesn't work send me the diagnostic file.
Ok. It works fine in the Reddit app and on Reddit safari. Same error occurs on avforums.com though.
Video and diagnostics attached
@Unmutual it's not the website and not your AI setting. Before the rewrite even starts the keyboard has to read the whole field, and in these rich text editors (the tracker's comment box, the XenForo one on avforums) it can't confirm where the text starts or ends. So it stops and leaves your text alone, that's the "Couldn't read the whole field" note. Reddit uses a different editor and reads fine. Your avforums log also shows one rewrite that did go through in the same box, so it depends on the state of the field, not on the site.
Your diagnostics don't say at which point the read gives up, so build 429 logs exactly that. If you hit it again on 429, send me a diagnostics export right after.
Will do. It’s highly reproducible so should be easy enough to log.
@efko here’s the diagnostics after using the space bar swipe on avforums
@Unmutual your 429 export pinned it. The keyboard walks the cursor to the start of the field and then checks one step further to make sure it really is the start. In the avforums editor that extra step makes the page stop reporting any text on either side of the cursor, and the keyboard took that as an empty field. So it ended up with 0 characters and the "Couldn't read the whole field" note.
Fixed for build 430: when the text vanishes on both sides after that check, the keyboard steps back and confirms where it was instead of assuming the field is empty. Undo, Replace in the translator and the copy/cut whole field gestures read the field the same way, so they get the fix too.
One case stays on the safe side on purpose. If there are two or more empty lines in a row above the cursor in an editor like this, it will still refuse rather than risk rewriting only part of the text. If the note shows up on 430 anywhere else, send me a diagnostics export right after.
Sorry. Same issue in 430. Confirmed here and on avforums.
Log attached
@Unmutual on 430 your whole text was actually read, but in these editors the keyboard can't confirm where the field starts, and it still treated that as "couldn't read the whole field". Fixed for build 436: it now rewrites exactly the text it read, after checking the cursor is really at its end. If there are two or more empty lines above your text, only the part below them gets rewritten and the note asks you to check it.
This is fixed.