Reference for the coordinator-owned steering path. Every correction signal is persisted, surfaced, decided by the coordinator, and then executed according to that decision.
For the implementation flow, see the deep dive. For operator behavior, see the experience guide.
| Method & path | Body | Returns | Notes |
|---|---|---|---|
POST /api/runs/{coordinatorRunId}/steer |
kind, optional target_child_run_id, instruction |
Steering directive view | Human steering entry point. pause is not supported. |
POST /api/runs/{coordinatorRunId}/assembly/review |
approved, request_changes, declined, feedback, optional target files |
Assembly review decision | Human review still posts to the review gate, but correction feedback is routed through unified steering. |
The separate Assembly Gate route was removed; correction feedback uses unified steering through the coordinator.
SteeringSignal is the internal normalized contract (apps/Agentweaver.Api/Coordinator/SteeringSignal.cs:29).
| Field | Values / type | Meaning |
|---|---|---|
CoordinatorRunId |
string | Coordinator run that owns the decision. |
Source |
human-review, rai, rubberduck, build-test, agent, coordinator, step |
Where the feedback came from. |
TargetScope |
{ kind, subtaskIds?, childRunId? } |
Run, work-plan, or subtask target. |
Feedback |
string | Reasoning context for the coordinator; not parsed for hidden routing. |
Severity |
advisory, request-changes, blocking |
How strong the signal is. |
Verb |
stop, send, redirect, amend, dispatch-fresh |
Delivery verb. |
TreeHash |
string or null | Aggregate tree hash the feedback was produced against. |
TargetFiles |
string array or null | Explicit hints only; never inferred from prose. |
CreatedBy |
string | User, agent, or gate id. |
| Decision | Meaning | Effect |
|---|---|---|
in_place_steer |
A: context-preserving correction | Resume the same child run/session/worktree with revision feedback. |
dispatch_fresh |
B: conscious fresh dispatch | Reset selected subtasks and launch fresh child runs. Always preceded by coordinator.steering_decision. |
proceed |
C: proceed or terminal | Continue to review or record a terminal/blocked result. |
advisory |
D: no-op | Surface the signal and take no corrective action. |
The in_place_steer vs dispatch_fresh choice hinges on a resumability probe. The in-api default (DefaultResumabilityProbe) treats a target as resumable when a target subtask still references a ChildRunId inside its retention window. At the assembly gate under pod-per-run, PodPerRunResumabilityProbe additionally treats subtasks that reached assemble_ready / completed as non-resumable (their AgentHost pod was released on suspend), so the decision resolves to dispatch_fresh — a fresh pod on the committed worktree branch — instead of resuming a reaped pod (apps/Agentweaver.Api/Coordinator/CoordinatorSteeringDecider.cs:706, issue #220). In pod-per-run + single-agent squads with no eligible rotation author, the first rejection therefore routes straight to human review rather than looping full-plan replans.
| Event | When it fires | Payload |
|---|---|---|
coordinator.steering_received |
A signal from any source is persisted and queued. | directiveId, source, severity, verb, targetScope, feedback, treeHash |
coordinator.steering_decision |
The coordinator records its A/B/C/D decision before executing the effect. | directiveId, decision, rationale, subtaskIds, attempt |
coordinator.steering |
Legacy directive lifecycle event for human steering. | directiveId, kind, targetChildRunId, status, instruction |
The web timeline renders dispatch_fresh as fresh dispatch, in_place_steer / in-place as steered in place, and advisory as advisory noted (apps/web/src/components/LifecycleEventCard.tsx:260).
| Case | Observable result | Recovery behavior |
|---|---|---|
| Transient in-place revision commit failure | The child stays on the same run/worktree while commit is retried. | AgentTurnExecutor retries CommitChanges up to 3 attempts before surfacing failure. |
| Persistent child executor failure during in-place revision | Child run terminalizes with run.failed reason child_executor_failed:{executor} and the corresponding workflow.step is failed. |
The coordinator preserves the steering instruction and emits a visible dispatch_fresh steering decision for failed targets. |
| Crash before revision launch or before first confirmed effect | The steering directive remains outstanding; it is not marked applied. |
Recovery re-drives unconfirmed targets. Confirmed child effects are skipped so successful children are not re-injected. |
| Successful in-place revision | Same child run/worktree re-enters assembly after reaching assemble_ready or completed. |
The directive is marked applied only when every target is assembly-eligible and every target child has a confirmed SteeringRevisionExecution marker. |
child_executor_failed:{executor} is terminal for coordinator child runs. It replaces the previous uninformative watch_stream_completed_without_terminal_event path for child executor throws, so operators see the executor that failed and the timeline gets a failed workflow.step.
| Bound | Default | Source |
|---|---|---|
| Per-subtask recovery attempts | 3 |
CoordinatorSteeringService.MaxRecoveryAttempts |
| Per-plan steering iterations | 6 |
CoordinatorSteeringDecider.DefaultMaxPlanSteeringIterations |
When a budget is exhausted, the decider chooses proceed and records the rationale. Assembly may surface this as assembly_blocked with reason steering_budget_exhausted.
| State / record | Purpose |
|---|---|
SteeringDirective |
Stores the signal, status, chosen action, attempt, source/severity/scope, and tree hash. |
assembly_steering work-plan status |
Decision-in-progress lease for assembly-originated feedback. |
SteeringRevisionExecution |
Attempt-specific marker proving an in-place revision effect ran. |
RecoveryAttempts on subtask |
Per-subtask loop bound. |
SteeringIterations on work plan |
Per-plan loop bound. |
A human redirect/amend/send sent to POST /api/runs/{id}/steer while the coordinator is parked at the assembly human-review gate (awaiting_review) is delivered straight into the review gate rather than the child-turn queue (#226): redirect/amend become a request-changes decision on the same path as POST /assembly/review (settling relayed), and send becomes an advisory note (settling applied). When the gate is armed on a different API replica the directive is durably persisted with the terminal status deferred for the owning pod's poller to drain, and the endpoint answers 202 Accepted. See resilient assembly review.