Story
When I remember something important while the AI is still working, I want to add it without stopping, so the work done so far is kept and the result includes my change.
Leila, planning her sister's wedding in Marrakech, researching venues on her laptop.
- 01 Setting
Leila asks for 5 wedding venues for 60 people, under 80,000 dirhams.
- 02 Trigger
While it is still checking venues, she remembers: her grandmother uses a wheelchair.
- 03 Without it
She has to stop the research and start again. The 7 venues it already checked are lost.
- 04 With it
She types the change and taps Update. It says "Got it" and keeps the 7 it already checked.
- 05 Outcome
The answer lists 5 step-free venues and says it includes her update.
Live demo
This demo follows a script, so it plays the same every time - there is no real AI behind it. Change a setting to see the same moment play out differently.
What happens, step by step
| State | The person sees | The AI is | When | Screen reader |
|---|---|---|---|---|
| 1 | Her ask in the chat. | Starts work. | 0 s | - |
| 2 | "Checking venues · 3 of 12" with a bar. The composer (the box where she types) says "Add to the task", with Stop beside it. | Works. | minutes | “Researching” |
| 3 | Her change in the composer. Update appears next to Stop. | Keeps working. | - | - |
| 4 | Her message in the thread, "Added while working". In the work card: "Got it - only step-free venues. Keeping the 7 already checked." | Takes it in without stopping. | on tap | “Update added to the task” |
| 5 | "Checking step-free access". The count keeps going from where it was. | Works with the change. | - | - |
| 6 | If it can't be used now: her message in a drawer (a small panel that slides open), "Queued · runs after this task", with Edit and Remove. | Finishes the run first. | on tap | “Message queued” |
| 7 | The old way: "Sending stops the work". The count drops to 0 and 7 checked venues are lost. | Starts over. | on tap | “Stopped. Starting again” |
| 8 | 5 venues, marked "Includes your update · step-free only". | Idle. | when done | “Response complete” |
On each device
- phone
- The composer stays open while the AI works, with Stop and Update side by side, each at least 44 px. The update shows in the thread right under the ask.
- tablet
- As on the phone.
- desktop
- As on the phone. Enter sends the update into the running work; a second shortcut can queue it instead.
When to use it
- The work runs long enough that people think of something while it runs - research, reports, tasks for an agent (an AI that can take actions for you).
- Most of the work done so far is still useful after the change.
- People often add a limit or a detail, rather than change the whole ask.
- The answer takes a few seconds. Stopping and asking again costs little. Use Stop generation instead.
- The change throws out the whole ask. Start a new version instead. Use Regenerate, edit and branches instead.
- People should agree the plan before any work starts. Use Intent preview and plan instead.
The parts of the pattern
- AThe updateHer message in the thread, marked "Added while working".
- BGot it1 line that says what was taken in and what was kept.
- CProgress that keeps goingThe count carries on from where it was. Nothing resets.
- DStopStill there. Updating and stopping are 2 different buttons.
- EAdd to the taskThe composer's placeholder (the grey hint text in the box) while it works, so people know they can add to it.
Do and Avoid
Only step-free venues
Checking venues · 8 of 12
Got it. Keeping the 7 already checked.
Only step-free venues
Checking venues · 0 of 12
Stopped and started again. 7 venues lost.
Checking venues · 11 of 12
Queued · runs after this task: Only step-free venues
Only step-free venues
5 venues: Dar Amira, Riad Zitoun…
2 have steps at the door. Nothing says why.
Writing and accessibility
- Change the composer's placeholder while it works: "Add to the task".
- Name the button for what will happen: "Update" when it joins the work, "Queue" when it waits.
- Confirm in 1 line what was taken in and what was kept: "Got it - only step-free venues. Keeping the 7 already checked."
- Mark the answer: "Includes your update".
- People can still move keyboard focus to the composer while the AI works. Stop and Update are separate buttons with their own names.
- Announce "Update added to the task" or "Message queued" when it is sent.
- Don't move focus to the work card when the update is taken in.
- Queued messages are a list people can reach by keyboard, with Edit and Remove on each.
Seen in real products
- ChatGPTWeb and apps · Nov 2025"Update" lets people add context while GPT-5 Pro or Deep Research is still working, without stopping and restarting.TechRadar, Nov 2025 ↗
- ChatGPT WorkDesktop and mobile · Jul 2026While a task runs, people can follow progress, answer its questions and redirect it.OpenAI: ChatGPT for your most ambitious work (9 Jul 2026) ↗
- Replit AgentWeb and mobile · Nov 2026"Steer" sends a follow-up into the running turn; "Queue" saves it for the next turn. Queued messages wait in a drawer above the input, where they can be edited, reordered, deleted or steered now.Replit Docs: Steer and queue messages ↗
Each example comes from the product’s help pages, release notes or teardowns, with the month it was checked. Products change every month - tell us when 1 is out of date.
Check yourself
Seen this pattern done better, or a product that changed? Press Suggest next to any heading, or tell us about the whole page.