Skip to main content
This page covers implemented agent lifecycle, hierarchy views, and template-based creation.

​
Agents

Agent records include runtime identity and control fields:
  • display identity (displayName, slug, runtimeAgentId)
  • lifecycle/status (idle, active, blocked, error)
  • kind (worker, manager, ceo, guard)
  • dispatch eligibility and WIP limit
  • model + fallback configuration
Default CEO behavior:
  • If the OpenClaw runtime agent main exists, ClawControl treats it as the default CEO inbox (escalation/notification target).
  • On fresh installs and workspace changes, ClawControl scaffolds agents/main/SOUL.md and agents/main/HEARTBEAT.md create-if-missing.
Workspace contract (recommended):
  • Maintain a workspace-root AGENTS.md with your governance and hierarchy rules.
  • Keep per-agent files under agents/<id>/:
    • SOUL.md
    • HEARTBEAT.md
    • MEMORY.md
See Workspace Files.

​
Agent Actions

Implemented actions include:
  • create agent directly
  • create from template
  • preview template expansion
  • provision agent to OpenClaw
  • test agent execution
  • update agent metadata/state
  • set/remove avatar with typed confirmation

​
Hierarchy View

Agents page supports list and hierarchy modes backed by /api/agents/hierarchy.

​
Templates

Agent templates support:
  • list/get/create/update/delete
  • import/export
  • file retrieval per template

​
Teams

Teams are managed from the Agents page and support:
  • create/edit/delete
  • linked workflow/template metadata
  • export as team YAML or package bundle
  • package deploy ingestion from the shared import flow

​
Skills Duplication

Agents workflow includes duplication of global skills into agent scope where supported.

​
Last updated

2026-02-13