Neura Market Logo

Steer an Active Run Without Changing Queue Mode

Learn how to use the /steer command to send guidance to an active run regardless of queue settings. This page explains the difference between /steer and /queue steer for runtime control.

Read this when

  • Using /steer or /tell while an agent is already running
  • Comparing /steer with /queue modes
  • Deciding whether to steer the current run or an ACP session

/steer initially attempts to send guidance to an already active run. This is meant for "tweak this run while it's still in progress" situations. If the active runtime cannot accept steering, OpenClaw falls back to sending the message as a standard prompt rather than discarding it.

Current session

Apply the top-level /steer to direct guidance at the active run for the current session:

/steer prefer the smaller patch and keep the tests focused
/tell summarize before making the next tool call

Behavior:

  • Only addresses the active run for the present session.
  • Functions regardless of the session's /queue setting.
  • Begins a normal turn with the same message if the session is idle or the active run cannot accept steering.
  • Follows the active runtime's steering path, so the model receives the guidance at the next supported runtime boundary.

Steer vs queue

/queue steer causes regular inbound messages to attempt steering the active run whenever they arrive during an active run. /steer <message> is an explicit command that forces that command's message into the active run at the next supported runtime boundary, regardless of the stored /queue setting. When that injection is unavailable, the command prefix is removed and <message> proceeds as a standard prompt.

The explicit /steer (and /tell) command is supported through Gateway. In openclaw chat or openclaw tui --local, choose /queue steer and send the guidance as a regular message; the embedded runtime applies the same steering policy without forwarding a Gateway command.

Use:

  • /steer <message> when you want to guide the active run immediately.
  • /queue steer when you want future normal messages to steer active runs by default.
  • /queue collect or /queue followup when future normal messages should wait for a later turn instead of steering the active run.
  • /queue interrupt when the newest message should replace the active run instead of steering it.

For queue modes and steering boundaries, see Command queue and Steering queue.

Sub-agents

Top-level /steer targets the active run of the current session. Sub-agents report back to their parent or requester session; /subagents is provided for visibility only.

ACP sessions

Use /acp steer when the target is an ACP harness session:

/acp steer --session agent:main:acp:codex tighten the repro

Refer to ACP agents for ACP session selection and runtime behavior.