---
title: "Update Worker"
method: PATCH
path: "/worker/{worker_id}"
tags: ["workers"]
---

# Update Worker

`PATCH /worker/{worker_id}`

Patch a worker's standing configuration or enabled state.

State-changing, so it goes through the standard ``AuthorizedUserDep`` chain
(authenticated + CSRF-validated). The organization comes from the
authenticated user, never the request body.

## Path parameters

- `worker_id` string, required

## Request body

- UpdateWorkerRequest — Patch a worker's operator-managed configuration and lifecycle. The instruction is read from durable worker state on each fresh agent run, so changes apply on the next revival without redeploying. Pass a non-null string to overwrite it; omit it or pass ``null`` to leave it unchanged. ``enabled=false`` gracefully stops the worker through the same path as the Slack kill switch. ``enabled=true`` deliberately clears that terminal stop; the next eligible message revives a dormant execution normally.
  - `custom_instruction` string, nullable
  - `enabled` boolean, nullable

## Response `200`

Successful Response

- WorkerResponse
  - `id` string, required
  - `resource_id` string, required
  - `display_name` string, required
  - `platform` 'slack' | 'teams' | 'web', required — A supported chat platform. Values align with ``integration_instances.type`` so a chat install's platform and its integration row stay in lockstep.
  - `agent_type` string, required
  - `mode` 'incident' | 'alerts', required — The kind of channel the agent lives in — its standing mission. Drives the swappable mode block in the system prompt (and, later, the toolset). ``incident`` and ``alerts`` have mode blocks today; ``escalation`` and others land as localized drop-ins (their standing block + tooling) when that work begins.
  - `custom_instruction` string, nullable
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `stopped_at` string, date-time, nullable, required
  - `status` 'critical' | 'attention' | 'working' | 'stable', required — The worker's present-tense status top-line, shown as a pill on the /workers list. Only these agent-picked values are ever stored in the `status` column; a null column means none has been emitted yet (the UI renders that as `starting`), and the terminal `stopped` state is derived from `stopped_at` — neither is stored here, so there is no second source of truth. The agent-facing definitions live on the ``status`` field in ``prompts.py`` (the only copy the model reads); keep this summary in sync with it. Values: CRITICAL: Immediate coordinated response is warranted because user-facing impact is severe or escalating. ATTENTION: A specific person or team should act now, but immediate coordinated incident response is not warranted. STABLE: Resting floor — no specific person or team needs to act now and no coordinated incident response is warranted. WORKING: Legacy — no longer emittable, see ``EmittableWorkerStatus``.
  - `status_message` string, nullable, required
  - `status_updated_at` string, date-time, nullable, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/traversal/apis/fastapi.md) · [All operations](https://skmtc.net/traversal/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/traversal/fastapi/revisions/2134ebffd1ef/schema)