Skip to content

Commit 2d0622b

Browse files
fix(server): explicit steer in a turn gap queues instead of failing
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 27d7943 commit 2d0622b

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

‎apps/server/src/orchestration-v2/CommandPolicy.ts‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -159,14 +159,11 @@ function resolveDeliveryIntent(
159159
run.status === "waiting",
160160
);
161161
if (activeRun === undefined) return { type: "start_immediately" };
162-
if (deliveryIntent === "steer") {
163-
return { type: "steer_active", targetRunId: activeRun.id };
164-
}
165162
if (deliveryIntent === "restart") {
166163
return { type: "restart_active", targetRunId: activeRun.id };
167164
}
168165
// A run can be active before its provider turn starts or after it finishes.
169-
// Queue automatic input in those gaps so steering cannot reject the message.
166+
// Queue input in those gaps so steering cannot reject the message.
170167
if (
171168
activeRun.status === "preparing" ||
172169
activeRun.status === "starting" ||
@@ -176,6 +173,9 @@ function resolveDeliveryIntent(
176173
) {
177174
return { type: "queue_after_active" };
178175
}
176+
if (deliveryIntent === "steer") {
177+
return { type: "steer_active", targetRunId: activeRun.id };
178+
}
179179

180180
const providerThread = projection.providerThreads.find(
181181
(candidate) => candidate.id === activeRun.providerThreadId,

0 commit comments

Comments
 (0)