Documentation Index
Fetch the complete documentation index at: https://docs2.openclaw.ai/llms.txt
Use this file to discover all available pages before exploring further.
/steer first tries to send guidance to an already-active run. It is for
“adjust this run while it is still working” moments. If the current runtime
cannot accept steering, OpenClaw sends the message as a normal prompt instead
of dropping it.
Current session
Use top-level/steer to target the active run for the current session:
- Targets only the current session’s active run.
- Works independently of the session’s
/queuemode. - Starts a normal turn with the same message when the session is idle or the active run cannot accept steering.
- Uses the active runtime’s steering path, so the model sees the guidance at the next supported runtime boundary.
Steer vs queue
/queue steer makes normal inbound messages try to steer the active run when
they arrive while a run is active. /steer <message> is an explicit command
that tries to inject that command’s message into the active run at the next
supported runtime boundary, regardless of the stored /queue setting. When
that injection is not available, the command prefix is stripped and <message>
continues as a normal prompt.
Use:
/steer <message>when you want to guide the active run right now./queue steerwhen you want future normal messages to steer active runs by default./queue collector/queue followupwhen future normal messages should wait for a later turn instead of steering the active run./queue interruptwhen the newest message should replace the active run instead of steering it.
Sub-agents
Top-level/steer targets the current session’s active run. Sub-agents report
back to their parent/requester session; /subagents is for visibility only.
ACP sessions
Use/acp steer when the target is an ACP harness session: