---
title: Correct a run without losing its work
description: Send a queued message to the run that is already working, stop from the composer, and ask for something else by typing it.
type: changelog
date: 2026-09-01
changelog:
  category: Conversations
---

Changing what a run is doing no longer means throwing its work away.

- **Send now** is new. Send normally while a run is working, then choose **Send
  now** on the queued item above the composer. Your message goes to the run that
  is already working, which keeps everything it has done.
- **Queued messages** now appear directly above the input, showing your own
  words, instead of only as a line in the activity panel — and each can be
  stopped there without waiting for it to start. In the conversation, a queued
  item reads as waiting rather than working, for everyone in it.
- **Stop** moved onto the composer's send button while your run is working, and
  turns back into Send as soon as you type. Stopping now asks what you would
  like it to do instead, and that next message starts a fresh run linked to the
  one you stopped.
- The old **Stop and redirect** button and its separate composer are gone. You
  can still do everything it did, from the input you already use.

Read [Change what a run is doing](/steering-a-run) for when to use each control.