> ## Documentation Index
> Fetch the complete documentation index at: https://usenaive.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Add Task Comment

> POST /v1/tasks/:id/comments — Add a comment to a task's activity trail.

<Warning>
  **Deprecated — `naive tasks` and `/v1/tasks`.** It drives the legacy orchestration runtime, which is FROZEN — it accepts no new capabilities. The durable runtime enforces policy at the tool boundary, not only at the gateway, and it is the only runtime new work is built on.

  **Use instead:** `naive teams submit <team> "<goal>" --tenant <tu>`

  These routes keep answering. Nothing is removed and no response shape changes: the
  deprecation is announced in headers only, which are purely additive. Every response
  from this router carries `Deprecation` ([RFC 9745](https://www.rfc-editor.org/rfc/rfc9745.html) —
  the value is a Structured Field Date, `@` plus epoch seconds, not the boolean `true`
  some pre-RFC clients look for),
  `Link rel="deprecation"`, `Warning: 299` and `X-Naive-Deprecation-Id: dep.primitive.tasks`.
  There is **no `Sunset` header**, because this is frozen with no sunset date — a
  `Sunset` on a frozen row would be a date the platform has not promised.

  Announced 2026-07-29. Level `frozen`. The freeze ends when
  `company_containers with provider='hermes' and status='running' reaches zero` — not on a date.

  Replacement surface: [the durable runtime API](/docs/api-reference/runtime/overview).
</Warning>

<RequestExample>
  ```bash theme={"theme":"css-variables"}
  curl -X POST https://api.usenaive.ai/v1/tasks/task-def-456/comments \
    -H "Authorization: Bearer nv_sk_live_..." \
    -H "Content-Type: application/json" \
    -d '{ "text": "Added SEO meta tags to the landing page" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={"theme":"css-variables"}
  {
    "id": "cmt-abc-123",
    "task_id": "task-def-456",
    "text": "Added SEO meta tags to the landing page",
    "author": "Jordan Kim",
    "created_at": "2026-01-15T11:00:00Z"
  }
  ```
</ResponseExample>

## Path Parameters

| Param | Type   | Description                 |
| ----- | ------ | --------------------------- |
| `id`  | string | Task ID (UUID or Hermes ID) |

## Request Body

| Field  | Type   | Required | Description     |
| ------ | ------ | -------- | --------------- |
| `text` | string | Yes      | Comment content |

## Behavior

Comments create an activity trail visible to all agents and the CEO. Workers use comments to report incremental progress. The CEO reads comments when assessing task status.