Do not interrupt an agent that is going well. Queue the next thing.

You are watching an agent work and you think of the next thing you want it to do. It is two minutes into a task and going well. Interrupting it now to say the next thing is a bad trade - it loses its place, and you lose the minutes it takes to find it again. Holding the thought until it finishes means you have to be there, and remember, at the moment it finishes.

There is a third option, and it is the habit that makes several agents at once bearable: write the instruction now, queue it, and send it when you are ready.

Write it while you think of it

The prompt bar under the terminal in DevThrottle is a separate box that lives outside the terminal. Typing into it reaches nothing until you send, so you can write slowly, change your mind, or dictate - and the agent carries on undisturbed.

Press Ctrl+Shift+Enter, or click Queue beside the box. The box empties, the button turns red and starts counting - Queue (1) - and your instruction appears in the queue panel on the right of the window, attached to that session.

The queue does not send anything by itself

This is the part that decides whether the habit works for you. DevThrottle does not watch for the agent to finish and feed it the next item. The queue is a list of instructions you have written and not yet delivered - a notepad with an order to it, pinned to the right session.

That is a choice, and a sound one. An agent that has stopped has either finished cleanly or stopped to ask you something, and from outside those look the same. Firing the next instruction into the second case would answer a question with unrelated text, and the agent would do its best to make sense of it.

Then send it on purpose

• Reorder before you send. Each queued item has arrows to move it up or down, Edit to reword it in the larger editor, and X to drop it. The order you thought of things in is rarely the order you want them done in.
• Pop, read, send. When the session goes quiet, click Pop on the item you want. Its text comes back into the prompt bar and leaves the queue. Read it once - the agent's last turn may well have changed what you want to say - then send it with Ctrl+Enter. That gap between popping and sending is the point: it is where an instruction written twenty minutes ago gets checked against what happened since.
• Pop adds, it does not replace. Popped text is appended to whatever is already in the prompt bar, so send or clear what you are holding first, or the two run together into one message.
• Clear means all of it. Clear at the top of the panel empties the queue at once, with no confirmation and no undo. Use X on single items unless you mean every one.

It outlives the window

The queue belongs to the session, not to the screen. Queued instructions are saved with the session and are still there after you restart DevThrottle, so the thing you thought of last thing at night is waiting in the morning, next to the session it was for.

The same queue is in the Cockpit in your browser, where each item carries a Send button of its own that submits it in one press. The phone does not have the queue; there, you answer and steer, and the lining up happens at a keyboard.

The habit, step by step, is in Line up the next instruction. Every prompt-bar control and shortcut is on the embedded terminal page.