> 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-sandbox-connections/openapi.json](/docs/api/agent-sandbox-connections/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Agent sandbox connections: Disconnect an agent

> **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 sandbox connections](/docs/api/agent-sandbox-connections.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Disconnect an agent

`DELETE /v1/agent-sandbox/connections/{agent}` - operationId `agent-sandbox-connections.disconnect`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 4,800 requests a minute per API key |

Logs the agent CLI out in your Kenso sandbox and answers `{ agent, status: "not_connected" }`. With no agent left
connected, the sandbox itself is deleted. Disconnecting an agent that is not connected answers the same.

Errors:

- `400 validation_failed`: an unknown agent.
- `404 not_found`: a feature is off, or the credential is not a person's.
- `409 run_active`: your sandbox is running a run. Stop it first.
- `503 service_unavailable` with `Retry-After`: the sandbox did not answer; try again.

Needs the `agent_sandboxes` feature on your workspace. Until it is on, calls answer 404. 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-sandbox-connections/DELETE/v1/agent-sandbox/connections/%7Bagent%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `agent` | path | string | yes | The agent's id: `claude`, `codex`, `antigravity`, `opencode`, `grok` or `cursor`. |
| `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`. |

### Response 200

`data` is a `AgentSandboxDisconnect`.

| Field | Type | Description |
| --- | --- | --- |
| `agent` | string | The agent's id. |
| `status` | string | Always `not_connected`. |

### Request

```bash
curl -X DELETE "https://api.ken.so/v1/agent-sandbox/connections/claude" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "agent": "string",
    "status": "string"
  }
}
```
