Skip to main content
An Agent is a reusable, versioned configuration for persona and capabilities. It contains a model, system prompt, tools, MCP servers, Skills, metadata, and an optional multiagent roster. An Agent is not a running process. Checkfu follows the Claude Managed Agents lifecycle: there is no separate Draft or publish step. Creating an Agent produces Version 1. Every update that changes the configuration produces the next immutable Version automatically; a no-op update returns the current Version.

Create an Agent

The response includes the stable agent_… ID and version: 1.

Update and inspect Versions

version is an optional optimistic-concurrency guard. Supplying it rejects a stale update with 409; omitting it applies to the newest head. Omitted fields are preserved. Array fields replace the whole array, metadata merges by key, and system or description can be cleared with null or an empty string.
Within a supplied model object, effort is the sole retained subfield when the model ID is unchanged and effort is omitted. Other model fields are whole-object replacement: omitting speed restores standard, and omitting inference_geo clears the pin.

Coordinator rosters

An Agent becomes a coordinator when multiagent contains a roster:
A bare Agent ID resolves to its current Version when the coordinator Version is created. The object form pins an exact Version. self is rebound to the new coordinator Version on every update. All members must be active in the same Workspace, must not themselves be coordinators, and must use the same inference geo. An optional advisor is always returned last.

Archive

Archiving makes the Agent read-only. Existing immutable Versions remain retrievable, and list calls omit archived Agents unless include_archived is set. The CMA-compatible Session admission surface is migrating separately. Until it lands, do not use the retired Draft, Release, or AgentDeployment APIs with these Agents.