Queue follow-up messages while Joule is working

You can add follow-up instructions while Joule is still working. Ampere queues the follow-up so it can run after the active turn reaches a safe point.

Use queued follow-ups when you know the next instruction, but do not want to interrupt the current work.

Add a follow-up

While Joule is working, type the next instruction in the composer and send it. The composer may show that the message is queued rather than immediately running.

Good queued follow-ups are specific and build on the current work:

• "After this draft, make a shorter LinkedIn version."
• "When the report is done, save the final summary as a project asset."
• "After the tool result returns, turn it into a three-bullet recommendation."

Keep queued messages focused

Avoid queueing several broad changes at once. If Joule is still gathering data, too many queued instructions can conflict with each other.

Use one follow-up for the next clear step. Add more after you see the result.

Understand billing and execution

Queued follow-ups may start new assistant work after the active turn finishes. That work can use credits like other Joule messages or tool-backed actions.

If the organization runs out of credits, becomes debt-locked, or loses entitlement before the queued turn starts, the follow-up may be blocked or need to be resent after billing is resolved.

Stop instead when the direction is wrong

Queue a follow-up when the current work is useful and you want the next step. Stop or cancel when the current work is wrong and should not continue.

If you stop the active turn, review the chat state before assuming a queued follow-up still makes sense.

Review the final sequence

After Joule finishes, read both the original response and the queued follow-up result. Confirm that the second instruction used the right context and did not rely on partial or stale output.