worker-management

name	worker-management
description	Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.

Worker Management

Before You Create: Confirm with Admin

Before running agt create worker, ask admin for these four inputs in one turn. Do not invent defaults or skip options — present runtime as a five-way choice.

1. Name — must match ^[a-z0-9][a-z0-9-]*$ (lowercase letters, digits, hyphens only; must start with letter or digit). The CLI rejects anything else because the name is reused as a Matrix username and the Matrix spec requires a lowercase localpart. Tuwunel may also reject very short names at registration.

2. Runtime — pick one. The actual default is whatever admin chose at install — read ${AGENTTEAMS_DEFAULT_WORKER_RUNTIME} (controller falls back to openclaw only if the env var is unset) and present that value as "the default", then offer all five options so admin can switch:

   Runtime	Language	RAM	When to pick
   openclaw	Node.js	~500MB	General tasks. Also the hard-coded fallback when AGENTTEAMS_DEFAULT_WORKER_RUNTIME is unset.
   copaw	Python	~150MB	Python tasks or AgentScope-based worker behavior.
   qwenpaw	Python	~150MB