> For the index of every page in Orbital's docs, read https://docs.runorbital.dev/llms.txt.

# Message a run

> Steer a working agent or answer its question from the composer

You can write to a [run](/runs/)'s agent while the run works, from the composer at the bottom of the run page. Your message either steers the step that is working or waits for the next turn.

## Send a message

1. **Open the run.**

   Choose the run on the **Runs** page or under **Recent runs**. The run page opens on the **Session** tab.

![A run page for a running run, with a Running badge and Quiet for 4h 49m beside the tabs, and the harness, model, workflow and branch in a footer at the bottom.](/screenshots/run-running.webp?v=216080729b)

*A running run shows how long its agent has been quiet.*

2. **Write in the composer.**

   The composer sits at the bottom of the **Session** tab.

3. **Send the message.**

   While a step is working, your message steers it. The composer then says "Message the agent". When no step is working, the message waits for the next turn. The composer then says "Message the agent for its next turn".

## Pause and chat

Turn on **Pause and chat** in [Settings > Experimental features](/reference/settings/#experimental-features), then choose **Default Run interaction**. In **Run actions > Run interaction**, select **Steer**, **Pause and chat**, or **Inherit** to clear an override. A change applies to the next new message without restarting Orbital.

In Pause and chat, sending a message durably holds the graph before stopping its work. A single interrupted agent keeps its Session; other work opens a conversation Session in the Run's recorded environment. Replies, Context edits and validated handoffs remain paused until approved Resume. Conversation never completes a step by itself.

You can send another message while the agent replies. Orbital records it immediately and steers the running Turn when the Harness supports it. Otherwise it keeps the message for the next conversational Turn in the same Session. Closing the page does not stop an accepted reply.

Once Resume is approved, Orbital finishes the active Turn and carries any messages still waiting into the resumed Workflow. It does not open another conversational Turn ahead of that Resume. Messages sent after approval are refused and retained in the composer for retry.

Changing mode or disabling the feature does not discard an existing conversation or resume the graph. Its messages and Resume approval remain available under the rules it accepted.

## Answer a question

When the agent asks a question, the run's standing becomes Question and the line under the composer says "Answer replies to the question. Return or Send will message the agent." Choose one of the options, or write your own answer and choose **Answer**.

![An agent's question with several options to choose from and a box for a free-text answer.](/screenshots/agent-question.webp?v=92fd44eff4)

*Pick an option, or write your own answer.*

The **Attention** page lists every run with a question waiting. See [See the runs that need you](/runs/watch-a-run/#see-the-runs-that-need-you).

## Related

- [Watch a run](/runs/watch-a-run/): find the run and read its Session tab.
- [Pause, stop or resolve a run](/runs/control-a-run/): the controls that sit beside the composer.
- [Gates and waits](/workflows/gates-and-waits/): steps where a run waits for you.
- [Chats](/chats/): talk to an agent without a workflow.