Send follow-ups while the agent works

You don’t have to wait for the agent to finish before you write again. While it works, the message box offers two ways to send a follow-up: Queue and Send now.

Steps

  1. Type your follow-up

    While the agent is working, type in the message box as usual.

  2. Queue it or send it now

    While the agent works, the send button shows a clock: press Enter, or select it, to queue the message until the agent finishes its current work. To hand it to the agent as soon as it can take it, press ⌘Enter on a Mac or Ctrl+Enter on Windows and Linux, or select the arrow beside the send button and choose Send now. The same menu can hold a message until another conversation finishes; see Send a message when another conversation finishes.

    A conversation where the agent is working, with a follow-up typed in the message box. Highlighted: The send button, showing a clock (Queue), and the arrow beside it that opens its menu.A conversation where the agent is working, with a follow-up typed in the message box. Highlighted: The send button, showing a clock (Queue), and the arrow beside it that opens its menu.
  3. Manage queued messages

    Queued messages wait above the message box under Queued, numbered in order. Beside Queued, choose One at a time to give each message a turn of its own, or All at once to send everything queued in the agent’s next turn. Select the arrow beside a message to send it now, the same way as Send now, or select Send all to send all of them right away. Select the X to move a message back into the message box.

    Two queued messages above the message box under the Queued heading. Highlighted: The queued messages, with One at a time and All at once, Edit, Send all and each message’s arrow and X.Two queued messages above the message box under the Queued heading. Highlighted: The queued messages, with One at a time and All at once, Edit, Send all and each message’s arrow and X.
  4. Edit the queue

    Select Edit beside Send all to change queued messages where they wait. Each one becomes a box you can type in. Drag a message by its handle to move it, or press Option+↑ or Option+↓ on a Mac (Alt+↑ or Alt+↓ on Windows and Linux). Select the trash button to delete it. Drag images or files onto a message, or paste them into it, to attach them to that message. Select Done, or press Enter, to save every change at once. Cancel, or Escape, keeps the queue as it was.

    The queued messages being edited, each in a box with a drag handle and a trash button. Highlighted: The queue in Edit, with Cancel and Done.The queued messages being edited, each in a box with a drag handle and a trash button. Highlighted: The queue in Edit, with Cancel and Done.
  5. Manage pending messages

    A follow-up appears at the end of the conversation. Waiting to send means Enjoy is still holding it. Waiting for agent means it has been handed to the agent, which has not yet confirmed taking it in. To hand it to the agent right away, select Interrupt and send. The button reads Stop and send instead when Enjoy has to stop the agent’s work to send the message. When a message can be withdrawn, hover over it and select the trash button (tap it on iPhone).

    A sent follow-up at the end of the conversation, marked Waiting for agent. Highlighted: Stop and send.A sent follow-up at the end of the conversation, marked Waiting for agent. Highlighted: Stop and send.

Good to know

  • Queue is for things that can wait. With One at a time, when the agent finishes, Enjoy sends the first queued message as a new request, then the next one after that finishes, and so on. With All at once, Enjoy sends every queued message together as one request. A message that runs a skill still gets a turn of its own, and if the messages hold more than 8 images between them, the rest wait for the next turn.
  • Each conversation keeps its own choice, and new conversations start with One at a time. The iPhone app has the same choice above its queue.
  • Each queued message keeps the agent, model, effort, speed, and permissions selected in the message box when you queued it, and runs with them. So you can queue one message at High and the next at Low. With All at once, the messages go together at the settings of the last one. Once a queued message runs, its settings become the conversation’s. See Queued messages keep their own effort.
  • If the agent finishes with a question, queued follow-ups can still run. The conversation shows Working while it handles the follow-up, and the earlier question stays available to answer. After the queued work finishes, an unanswered question puts the conversation back in Needs input (Needs you on iPhone).
  • Send now is for corrections the agent should see soon. Claude Code, Codex, and Muse Code can take a sent message in during their current work. OpenCode, Grok Build, and Antigravity read it when their current work ends.
  • When Claude Code, Codex, or Muse Code takes in a sent message during its work, Enjoy asks it to briefly acknowledge the message before continuing. Messages it takes in together get one acknowledgement.
  • If the agent is waiting for you to allow a request or answer one of its own questions, sending a message declines it for you, so the agent can read your message instead of waiting. Queuing a message leaves the request waiting. See Approve or decline agent requests.
  • If you change the agent, model, or speed in the message box before sending, the message waits until the current work ends. So does a new effort or permission mode, except with Claude Code, which switches to them in the middle of its work and then takes the message in. A line in the conversation shows each change.
  • A sent message that has to wait shows with your queued messages, first in line, instead of at the end of the conversation. A sentence under it says why it can’t steer the current work, such as This message can’t steer the current conversation because it switches the model to Opus 5.5. It waits when it changes settings the agent can’t switch to mid-reply, when it runs a skill, or when the agent reads messages only when its current work ends. To send it anyway, select Interrupt and send now, which stops the agent and sends it. When only its settings hold it back, Steer with and the current settings, such as Steer with Sonnet 5.5 instead, sends it on the settings the agent is using, so it goes in right away. Before you send, Send now in the send button’s menu says when a message would wait.
  • Sent messages that wait for the current work to end go to the agent together, in its next turn. Messages sent with different settings go in separate turns.
  • A sent message goes ahead of anything in the queue.
  • To start on something else without waiting, fork the conversation. The fork gets a copy of the messages so far, and the agent here keeps working. See Fork a conversation.
  • A queued message that holds pasted text shows how many, such as 1 pasted text, instead of the text itself. Select Edit to see each one’s card. See Paste long text into a message.
  • Moving a queued message back adds it to the end of your current draft, with its attachments, so nothing you’ve typed is lost. The trash button deletes a pending message instead.
  • While you edit the queue, the agent keeps working. If it finishes before you select Done or Cancel, the queue shows Held while you edit and the next message waits for you. On your other devices, the queue shows Being edited.
  • A queued message you empty while editing is deleted when you select Done. A message’s workflows and skill stay as they were; to change those, move it back to the message box.
  • Claude Code can withdraw a sent message while it is still in Claude’s queue, without stopping the current work. Enjoy removes it only after Claude confirms cancellation. Codex and Muse Code don’t offer this per-message withdrawal after handoff. Messages held for OpenCode, Grok Build, or Antigravity can be deleted before Enjoy starts sending them.
  • Interrupt and send hands waiting messages to Claude Code without stopping it, as Send now does in Claude’s own terminal. A command or helper agent Claude is waiting for moves to the background and keeps running, and Claude reads your messages right away. A step that has only just started can take a few seconds to move. If Claude can’t move the step, it cuts that step short instead, but it keeps its session, its background commands and helpers, and the rest of the request.
  • Stop and send appears instead when Enjoy has to stop the agent first: with other agents, when a message is waiting with your queued messages, or when a message was not delivered. It stops the agent’s work, including any helper agents, then sends the messages as a new request.
  • In the conversation list, a clock with a number shows how many messages are queued or waiting.
  • A conversation can hold up to 1,000 queued messages.
  • In the iPhone app, the send button queues your message while the agent works. To hand it to the agent sooner, select the arrow beside the send button and choose Send now. Queued messages are numbered above the message box, with One at a time and All at once, Send all, and Edit. While you edit there, each message is a box to type in, with arrows to move it up or down and a trash button to delete it. Adding images or files to a queued message is on the computer app and the web app. A sent message that has to wait shows first in the iPhone’s queue too, saying why, with Steer with … instead, Interrupt and send now, and its trash button.

If something goes wrong

“Queue paused. Send a message or retry to continue.”

The conversation stopped or failed, so the messages queued before that aren’t being sent. Select Retry, or send a new message. A message you send or queue now goes right away, and once the agent finishes it, the queue continues. While a conversation waits for usage, everything queued waits until it resumes. See Stop an agent.

A waiting message says Not delivered or Delivery unconfirmed

Not delivered means the agent didn’t accept the message, for example because one of your own Claude Code hooks blocked it. Enjoy shows the reason, and the agent still finishes the rest of its work. Delivery unconfirmed means the connection ended before the agent confirmed it. Select Stop and send to send waiting messages again.

A pending message has no trash button

Enjoy cannot withdraw that message in its current state. It may already be in use by the agent, its provider may not support withdrawal after handoff, or its original connection may have ended. Stopping work does not undo a message the agent has already read.

“The agent could not confirm cancellation. The message was kept.”

The message may have left the agent’s queue before you selected trash. Enjoy keeps it visible because cancellation was not confirmed. A connection or cancellation error also keeps the message in place.

“A queued message was sent or removed while you were editing. Edit the queue again.”

Someone sent or removed one of the messages from another device while you were editing, so Enjoy didn’t save your changes. Select Cancel, then Edit again.

“This conversation’s queue is full. Send or remove queued messages first.”

The queue has 1,000 messages. Select Send all, or remove some with the X.

“Couldn’t send the queued messages in …”

Enjoy couldn’t save the conversation with its queued messages sent, so they stay queued. The end of the message says why. Your other conversations keep working. Enjoy tries again once something in this conversation changes, or you can select the arrow beside a message to send it now.

If the reason is “Document is too large”, the conversation has grown past the size Enjoy can save. Select Edit, copy each queued message, delete it with the trash button, and select Done. Then send what you copied in a new conversation.

See also

  1. 01Write and send a messageConversations · 6 min
  2. 02Send a message when another conversation finishesConversations · 3 min
  3. 03Stop an agentConversations · 2 min
  4. 04Fork a conversationConversations · 2 min
  5. 05Stay in the loop without watchingWorking well with Enjoy · 3 min

Did this help?

Service

If Enjoy doesn’t work as this manual describes, a person will help.