Steer work and answer questions
Add guidance during execution and resolve decisions in the conversation.
Keep guidance in the session so the agent can use it with the existing task history. Be explicit about whether you are correcting the approach, narrowing scope, or introducing another requirement.
Read the visual explanation
While the agent works, a clarification pauses the decision. Your answer stays with the session and work continues with that context.
Send guidance while work runs
Write the new instruction in the composer and send it. For example:
Keep the public API unchanged. Use a private helper for the new logic,
and keep this pull request limited to the search bug.Uno can accept input while execution is active. Delivery and application are separate: read the next response and inspect the result to verify the instruction took effect. A follow-up to an idle session starts another turn.
Answer a clarification
When the agent presents questions, choose an option or enter a custom answer. The questionnaire shows one required question at a time and keeps your answers together. Review the submitted result in the conversation.
A batch can remain partially answered. Work waiting on that batch resumes after all required questions are resolved. If the question no longer applies, explain the changed requirement instead of selecting an inaccurate option.
The same clarification can be answered from its supported entry point, including a linked Slack thread. Answers stay with the originating work. See Slack for reply syntax and thread behavior.
Stop work when needed
Use the cancellation action if the execution should stop. A message such as “actually wait” is guidance and is not equivalent to pressing Cancel. Cancellation does not roll back changes that already happened.
After a correction, read progress and review the changes. If input appears stuck, inspect recovery guidance before resending the same request.