Skip to main content
PUT

Behavior

Each update is saved as a new revision. Sessions pinned to an earlier revision with name:N keep running that one. Sending the current spec changes nothing. The name can’t change. To change a few fields, patch the agent.

Headers

string
The ETag of the revision you based this change on, for example "3". If the agent has moved past it, the write fails with 412. Omit it, or send *, to write regardless.

Path parameters

string
required
The agent’s name, for example my-research-bot or myorg/web-helper.

Query parameters

string
A note stored on the new revision, such as why you made the change. Up to 500 characters. Shown by List revisions.

Request body

The full agent, with the same fields and rules as Create an agent. The name must equal the URL identifier. Omitted fields reset to their defaults: leaving out instructions, model, skills, or answer_format clears them.

Response

200 with the updated agent object, with its new revision in the ETag header.

Errors