---
title: Change what a run is doing
description: Stop a run, let a message wait its turn, send it to the run already working, or ask for something else instead — and know which one keeps the work already done.
sidebar:
  icon: compass
  order: 2
---

When you send an AI prompt, the project starts a **run**. Three controls
change what happens next, and they sit where you already type — the composer at
the bottom of the conversation.

## The controls

| What you do | When you use it | The run's work |
| --- | --- | --- |
| Send while a run is working | Add to what you already asked | Kept — yours starts after |
| **Send now** | Correct the run that is working | **Kept** |
| **Stop** | End the run that is working | **Not kept** |
| Send again after stopping | Ask for something else | Not kept; a fresh run starts |

## Sending while a run is working

Send normally and your message waits its turn. The composer says so before you
send, and your message appears as a queued item directly above the input,
showing your own words.

A queued message has its own fixed view of the conversation and starts when the
working run finishes. Queueing never approves an action or answers a question
the agent asked.

Your message is in the conversation from the moment you send it, so the
conversation marks the queued item as waiting: only the run that is working
reads as working.

You can drop a queued item you no longer want with **Stop** on that item; it
never started, so nothing was spent on it. Stopping the run that is working
instead lets the next queued item start.

## Send now

If you do not want to wait, choose **Send now** on the queued item. Your message
is handed to the run that is already working, which picks it up at its next step
and **keeps everything it has done so far**. The queued item disappears, so your
words are never worked on twice.

Send now appears only on your own queued items, and only while a run of yours is
working. It is one run from start to finish, so it draws on one budget.

Your message stays exactly where you sent it in the conversation. Only which run
reads it changes.

## Stop

While your run is working, the composer's send button becomes **Stop**. It turns
back into Send the moment you start typing, so you never stop a run when you
meant to send.

Stopping keeps nothing the run was working on. Anything it already did outside
Auttendo — a message sent, a record written — is not undone.

## Asking for something else

After you stop a run, the composer asks what you would like it to do instead.
Type a new AI prompt in the same input and send it. That starts a **fresh run**,
recorded as following on from the run you stopped.

It does not pick up the stopped run's work. When you want that work kept, use
**Send now** instead of stopping.

## Who can do what

Only the person who started a run can send to it or stop it. Everyone in the
conversation sees the run's state and the messages, so the conversation still
reads as one story — they just do not get the controls.