Update an agent

Accepts PUT or PATCH (identical partial-merge semantics). Partial-patches an agent — only the fields you send change. autonomy_type, entity_type, and trigger_type are immutable — trigger_type may be sent but must match the agent’s current value, and a differing value returns 400. Send updated ticket_conditions / time_entry_conditions to change the entity filter; the server rebuilds the FIND_ENTITIES action. actions is the pipeline AFTER FIND_ENTITIES (CHAINED_ACTIONS only) — patching actions on an AGENTIC agent or conditions on a CONVERSATIONAL agent returns 400. An actions patch MERGES per-action: each entry targets one existing action by id (or unique action_type) and its input_as_dict is merged key-by-key, so changing one setting preserves the rest; unreferenced actions are kept and unmatched entries are appended. There is no wholesale-replace mode — a PUT can never drop or reorder an action (do structural pipeline edits in the dashboard). On a TRIAGE_TICKET / TRIAGE_TIME_ENTRY action, fields_to_triage is a list and so replaces wholesale under the normal merge — send fields_to_triage_edits in that action’s input_as_dict to change one field keyed by field_name: a matching entry merges key-by-key (every other triage field stays byte-identical), an unmatched one is appended (field_name is the only setting it must carry), and an entry carrying remove: true drops its target instead of editing it — a removal names its target and nothing else, must match a configured field (a no-match returns 400 rather than silently doing nothing), and cannot remove the last remaining field. A PSA-unsupported field_name returns 400, and sending both fields_to_triage and fields_to_triage_edits in one action returns 400. Use the field_name spelling GET /agents/<id> returns (the PSA name, e.g. contact, customFields); the enum member name (CONTACT, CUSTOM_FIELD) is also accepted. A custom field is keyed by field_name (customFields) plus custom_field_name, since all custom fields share one field_name — send both to target the right one. A toolbox patch also MERGES per tool: each entry under tool_settings_by_type is merged key-by-key onto that tool’s current settings (lists like allowed_users replace; null for a tool key disables it), so changing one tool’s setting no longer requires resending the whole toolbox. agent_settings, integrations, schedule, and callback_settings MERGE the same way: send only the fields you’re changing — e.g. {"agent_settings": {"custom_instructions": "…"}} edits only the instructions and leaves test_mode/model/til_channel intact, sending one integration’s permissions leaves the others connected, and {"schedule": {"timezone": "…"}} leaves the run cadence and business-hours windows intact. To edit a long custom_instructions runbook without resending the whole blob, send agent_settings_edits.custom_instructions with either edits (a list of exact old_string/new_string search-replaces — each must match exactly once, or pass replace_all; zero or multiple matches reject the request and write nothing) or append (text added with a newline separator). An optional base_hash (sha256:… of the instructions you read) gives optimistic concurrency: a stale hash returns 409 agent_stale_write instead of clobbering a concurrent dashboard edit. This form is mutually exclusive with a full agent_settings.custom_instructions in the same request (400), and applies only to AGENTIC / CONVERSATIONAL agents (CHAINED_ACTIONS has no agent_settings layer → 400). Refuses Neo-managed agents (403 agent_managed_by_neo). Editing actions, agent_settings, toolbox, integrations, or the conditions is a destructive change (triggers a TIL approval when an agent makes the call via NEO_API_REQUEST). 409 agent_update_conflict on a concurrent edit.