Add an instruction while work continues

3 minute read · Chats & Local Agents

You can add a detail while your agent is working. Keep the new instruction specific enough that the agent can tell whether it changes the current task or comes next.

• Add the next detail
• Keep changes understandable
• Choose a follow-up that helps the current work
• Manage the queue
• After stop, retry or restart

Add the next detail#

Send the follow-up in the active chat. For example: “Use the same article layout, but keep the search box visible on mobile.” Where the provider supports steering, Vortex can deliver it into the current turn. Otherwise it keeps the instruction for the next turn.

Watch the message’s delivery state. Pending, uncertain and next-turn states have different meanings; a message visible in the queue is not proof that the agent has read it. Remove a queued instruction before delivery when the UI offers that action.

Keep changes understandable#

Use one message for a related change rather than repeatedly sending the same request. If delivery is uncertain, inspect the state before retrying. An identical instruction sent again can mean a second task when it has a new identity.

Stopping cancels the current run and its approvals. Review any remaining queued work before continuing. Switching accounts must not deliver the old account’s messages to the new one.

See conversation organization and approvals.

Choose a follow-up that helps the current work#

While the agent is building a page, you might send: “Keep the signup optional and use the existing brand colors.” If the provider supports active steering, the instruction can enter the current turn. Otherwise Vortex retains it for the next turn. The queue should distinguish pending delivery, uncertain delivery and next-turn work.

Do not infer delivery from the text disappearing out of the composer. Read the queue/run state, especially after a network or provider interruption. If delivery is uncertain, avoid immediately sending the same instruction again. A repeated instruction can produce unnecessary changes even if the transport itself avoids a duplicate request.

Manage the queue#

Add follow-ups in priority order and keep them bounded. The pending queue holds up to eight messages; finish or remove pending items before adding more. Remove an item before delivery when the UI offers that action. Once a provider has accepted it, stopping the run is different from withdrawing an unsent message.

For a major change of direction, explain which earlier requirement is replaced. “Use a list instead of cards; keep the save form and database work” gives the agent a clear scope. An unrelated task is often easier to review in a separate chat.

After stop, retry or restart#

Inspect the recorded run state, retained reply and queue before continuing. Stopping invalidates pending approvals and should not be displayed as successful completion. A failed run can leave useful edits and output; review those rather than asking for a fresh project. Keep relevant history so the next instruction can build on the result. Use files and changes to inspect what happened before the interruption.