# 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.
> https://koi.dog/docs/api/crews/steer-crew/

`POST /api/v1/crews/{id}/steer` · Scope: `crews`

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.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | `string` | yes | The crew's id. |

## Headers.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Idempotency-Key` | `string` | no | Makes a retry safe: the same key with the same request returns the first answer and does nothing else. |

## Body.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `text` | `string` | yes | 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`.

## Request.

```sh
curl -X POST "https://app.koi.dog/api/v1/crews/$ID/steer" \
    -H "Authorization: Bearer $KOIDOG_API_KEY" \
    -H "Idempotency-Key: $(uuidgen)" \
    -H "Content-Type: application/json" \
    -d '{
      "text": "Keep the old settings page working while you change it."
    }'
```

```js
const res = await fetch(`https://app.koi.dog/api/v1/crews/${process.env.ID}/steer`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.KOIDOG_API_KEY}`,
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    text: "Keep the old settings page working while you change it.",
  }),
});
console.log(await res.json());
```

```python
import os
import uuid

import requests

r = requests.post(
    f"https://app.koi.dog/api/v1/crews/{os.environ['ID']}/steer",
    headers={
        "Authorization": f"Bearer {os.environ['KOIDOG_API_KEY']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "text": "Keep the old settings page working while you change it.",
    },
)
r.raise_for_status()
print(r.json())
```

## Response example.

```json
{
  "ok": true,
  …
}
```
