Steer a managed crew: send its manager a message.
Records the message at once with who sent it (steer.received) and re-engages the manager, which answers with one decision Koidog checks and applies in a single step: change the order in which tasks that have not started are picked up, add tasks (within limits.review.maxAddedTasks), drop tasks that have not finished, and change the instructions or dependencies of tasks that have not started, with an explanation of the impact.
POST/api/v1/crews/{id}/steer
Scopecrews
The answer carries the recorded steer (state pending); its outcome is on the crew's steering.steers and on the events steer.started, steer.applied and steer.not_applied. Builders already working carry on unless the decision drops their task. The message has the founder's authority over priorities only: it cannot raise the budget, the time limit, the VM or agent counts, change placement, models or the review bounds, or ask for a merge, a deployment or a deletion. A decision that does not check out goes back to the manager within the crew's maxRetries; after that the steer ends not_applied and the crew carries on unchanged. Answers 409 conflict for a direct crew, a crew that has ended, a plan waiting for the founder's approval (answer the approval instead), while an earlier steer is still pending, and once the crew's limits.review.steers (default 10) are used. While the manager is still writing its first plan the message goes straight to that run and no steer is returned. When an API key calls it, the timeline records who did what and the outcome. No query parameters.
Path parameters.
idstringrequired
The crew's id.
Headers.
Idempotency-Keystring
Makes a retry safe: the same key with the same request returns the first answer and does nothing else.
Body.
textstringrequired
The message for the manager. 1 to 4000 characters.
Response.
200 OK: a JSON object. The example has placeholder values.
- 422 validation_failed
- The body does not match its schema; each problem is in
details.