Steering queue

Steering queue 문서는 OpenClaw 공식 문서(concepts/queue-steering)를 한국어로 정리한 가이드입니다. How active-run steering queues messages at runtime boundaries 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

How active-run steering queues messages at runtime boundaries

한국어 가이드 범위: concepts/queue-steering 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Runtime boundary
Modes
Burst example
Scope
Debounce
관련 문서

상세 내용

본문

When a normal prompt arrives while a session run is already streaming and the queue mode is steer (the default, no config needed), OpenClaw tries to send that prompt into the active runtime. OpenClaw and the native Codex app-server harness implement the delivery details differently.

Runtime boundary

Steering does not interrupt a tool call that is already running. OpenClaw checks for queued steering messages at model boundaries:

Modes

Mode	Active-run behavior	Later behavior
`steer`	Steers the prompt into the active runtime when it can.	Waits for the active run to finish if steering is unavailable.
`followup`	Does not steer.	Runs queued messages later after the active run ends.
`collect`	Does not steer.	Coalesces compatible queued messages into one later turn after the debounce window.
`interrupt`	Aborts the active run instead of steering it.	Starts the newest message after aborting.

Burst example

If four users send messages while the agent is executing a tool call:

주요 항목:

With default behavior, the active runtime receives all four messages in arrival order before its next model decision. OpenClaw drains them at the next model boundary; Codex receives them as one batched turn/steer.
With /queue collect, OpenClaw does not steer. It waits until the active run ends, then creates a followup turn with compatible queued messages after the debounce window.
With /queue interrupt, OpenClaw aborts the active run and starts the newest message instead of steering.

Scope

Steering always targets the current active session run. It does not create a new session, change the active run's tool policy, or split messages by sender. In multi-user channels, inbound prompts already include sender and route context, so the next model call can see who sent each message.

Debounce

The built-in queue debounce applies to queued followup and collect delivery. In steer mode with the native Codex harness, it also sets the quiet window before sending batched turn/steer. For OpenClaw, active steering itself does not use the debounce timer because OpenClaw naturally batches messages until the next model boundary.

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/concepts/queue-steering
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

Steering queue

핵심 요약

How active-run steering queues messages at runtime boundaries

한국어 가이드 범위: concepts/queue-steering 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Runtime boundary
Modes
Burst example
Scope
Debounce
관련 문서

상세 내용

본문

Runtime boundary

Steering does not interrupt a tool call that is already running. OpenClaw checks for queued steering messages at model boundaries:

Modes

Mode	Active-run behavior	Later behavior
`steer`	Steers the prompt into the active runtime when it can.	Waits for the active run to finish if steering is unavailable.
`followup`	Does not steer.	Runs queued messages later after the active run ends.
`collect`	Does not steer.	Coalesces compatible queued messages into one later turn after the debounce window.
`interrupt`	Aborts the active run instead of steering it.	Starts the newest message after aborting.

Burst example

If four users send messages while the agent is executing a tool call:

주요 항목:

With default behavior, the active runtime receives all four messages in arrival order before its next model decision. OpenClaw drains them at the next model boundary; Codex receives them as one batched turn/steer.
With /queue collect, OpenClaw does not steer. It waits until the active run ends, then creates a followup turn with compatible queued messages after the debounce window.
With /queue interrupt, OpenClaw aborts the active run and starts the newest message instead of steering.

Scope

Debounce

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/concepts/queue-steering
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

Steering queue

핵심 요약

문서 구성

상세 내용

본문

Runtime boundary

Modes

Burst example

Scope

Debounce

관련 문서

실습 체크리스트

관련 링크

관련 가이드

Steering queue

핵심 요약

문서 구성

상세 내용

본문

Runtime boundary

Modes

Burst example

Scope

Debounce

관련 문서

실습 체크리스트

관련 링크

관련 가이드