After Laureo accepts a message, it saves the message, its context snapshot, and a run before work begins. Closing the Assistant, navigating to another page, reloading, losing your connection, closing the browser, or switching devices only detaches that viewer. The same run continues on Laureo's servers.

Reopen the conversation to replay its saved activity from the last event you saw. Laureo does not restart the request or guess which recent run you meant.

Work in other conversations collapses to a single line above the message box, so the chat you are reading is never sharing its space with a list of runs you are not looking at. It reads:

• "Working in 1 other chat" or "Working in 3 other chats"
• "2 waiting on you in other chats" when one of them needs a decision
• nothing at all when there is nothing running elsewhere

Pressing the line opens the list. Each row shows the conversation and its state as a word, with one control beside it: Open, or Stop while it is running. A long list ends with See all in Assistant work. On a phone the list opens as a bottom sheet.

States you will see on a row:

• Queued: accepted, waiting its turn to start.
• Working: the run is in progress.
• Needs approval or Needs input: the run is waiting on you.
• Finishing: confirming an effect that has already been accepted.
• Stopping: you selected Stop and the run is winding down.

The list holds unfinished work only. A run that has completed, failed or been stopped leaves the list, and how it ended reaches you through your notifications instead.

Anything blocked on your approval also appears in the assistant chip in the corner of the app, wherever you are. See Finding what is waiting on you.

The same run is never described in more than one place at once: the conversation it belongs to owns its live progress, this line owns the count of everything else, and the chip owns the decisions.

• A chat is ready. The notification is titled with the conversation, and its body carries the first line of the answer, so you often do not have to open anything. Opening it takes you to the answer itself inside the conversation, not just to the top of the thread.
• A run failed. Named as a failure, with no preview, and it opens the conversation.
• A run finished with an issue. When a run ended against a limit rather than an error, the notification body is the same sentence the conversation shows, so the two never disagree.
• Something needs your approval. Titled with the action, such as "Approve: Create booking page", and it goes on your to-do list rather than only the bell, because the run is stopped until you decide.

Two things are deliberately silent. A run you stopped yourself sends nothing, because you already know how it ended. An approval notice is not sent while you are already watching that run, because you can see the card.

Waiting is not a failure and is not a cancellation. A proposal stays paused for you to answer. If nothing answers it for 48 hours, the run is closed rather than holding the conversation open forever, with "This proposal expired before it was approved. Ask again if you still want it." Sending a new message picks the conversation back up.

If a conversation is already working, Send queues your message instead of interrupting. A strip appears directly above the message box reading "{n} waiting to send", with the queued messages listed under it. Until Laureo claims one you can Edit it, move it Up or Down, or Remove it. Queued messages start in the order shown, once the active run finishes. The strip is about this conversation only, and it is separate from the line counting work in other chats. A conversation holds up to 100 waiting messages, which is also how many the strip shows, so nothing you queue is hidden from you.

Composer drafts are versioned and saved for your organization, account, and conversation. They clear only after the server accepts the command. If another tab changed the same draft, Laureo asks you to resolve the version conflict instead of silently overwriting it.

If draft storage is temporarily unavailable, the message box stays usable and keeps what you type in the current tab. Sending still clears the text only after the server accepts the command.