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

> Update a session comment — Replaces the content of an internal note and stamps it as edited. Only the agent who authored the note may edit it.

# Update comment

Replaces the content of an existing internal note and stamps it as edited.

Only the note's **author** may edit it: `agent_id` must match the agent the note is attributed to, otherwise the request is rejected with a `403`. A note that has been deleted can no longer be edited.

<Note>
  `agent_id` identifies who the edit is attributed to — it is not a credential. An API key is scoped to the organization, not to one agent, so treat this rule as a safeguard against editing the wrong agent's note rather than as a permission boundary between your own agents.
</Note>

```json theme={"dark"}
{
  "content": "Correction: the refund was issued on the 14th, not the 12th.",
  "agent_id": 42
}
```

The note is resolved against the session in the path, so a `comment_uuid` belonging to a different session returns a `404` rather than editing the wrong conversation.

## Attachments

`attachments` is a full replacement of the note's file list, not a patch:

| You send               | Result                                        |
| ---------------------- | --------------------------------------------- |
| No `attachments` field | Existing files are kept as they are           |
| `"attachments": []`    | All files are removed from the note           |
| `"attachments": [...]` | The list you send replaces the existing files |

So editing only the wording is safe — omit the field and the files stay put. To drop a single file, send the list of the ones you want to keep.