> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/agent-work-settings/openapi.json](/docs/api/agent-work-settings/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Agent work settings: Update the agent work settings

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Agent work settings](/docs/api/agent-work-settings.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Update the agent work settings

`PATCH /v1/agent-work-settings` - operationId `agent-work-settings.update`

| Permission | Rate limit |
| --- | --- |
| The `workspace_settings` permission | 4,800 requests a minute per API key |

Sets the executor of each kind you name and leaves the others as they are. Body:
`{ "settings": [ { "kind": "personalization", "executor": "my_agent" } ] }`. Returns every kind after the
change, in the same shape as the GET. With `my_agent`, the kind's work waits for the workspace's agent: Kenso's
AI does not run it, and the full prompt and the lead's facts go to that agent.

Errors:

- `400 validation_failed`: `settings` is missing or empty, a `kind` or `executor` is not a
known value, or a kind is named twice. Each problem is one `details[]` entry, such as
`settings[1].kind`. Nothing is saved. A kind set to `my_agent` while its `available` is false
is a detail with code `kind_not_available`.
- `404 not_found`: the workspace does not have the `agent_work` feature.

Requires the `workspace_settings` permission.

Needs the `agent_work` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/agent-work-settings/PATCH/v1/agent-work-settings)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `settings` | array of UpdateAgentWorkSettingEntry | no | One entry per kind to change, each kind at most once. At least one entry. |

### Response 200

`data` is a `AgentWorkSettings`.

| Field | Type | Description |
| --- | --- | --- |
| `settings` | array of AgentWorkSetting | All eight kinds, always, in hand-out order (work with a deadline first). |

### Request

```bash
curl -X PATCH "https://api.ken.so/v1/agent-work-settings" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "settings": [
    {
      "kind": "meeting_brief",
      "executor": "kenso_ai"
    }
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "settings": [
      {
        "kind": "meeting_brief",
        "executor": "string",
        "updatedAt": "2026-09-23T15:02:11Z",
        "available": true
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### UpdateAgentWorkSettingEntry

One kind and its new executor.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | `meeting_brief`, `call_brief`, `workflow_prompt`, `qualification`, `segmentation`, `personalization`, `rewriting` or `background_ai`. |
| `executor` | string | no | `kenso_ai` or `my_agent`. |

### AgentWorkSetting

One kind of agent work and who runs it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | `meeting_brief`, `call_brief`, `workflow_prompt`, `qualification`, `segmentation`, `personalization`, `rewriting` or `background_ai`. |
| `executor` | string | no | `kenso_ai` (Kenso's AI runs it, the default) or `my_agent` (the workspace's own coding agent collects it with `kenso work run`). |
| `updatedAt` | string (date-time) | no | When the kind was last saved, in UTC; null for a kind the workspace never saved. |
| `available` | boolean | no | Whether the kind can be given to your agent now. False: Kenso cannot hand this kind out yet, so setting it to `my_agent` answers `kind_not_available`. |
