Worker Management
Use when admin requests hand-creating or resetting a Worker, starting/stopping a...
Install
npx skills add agentscope-ai/AgentTeams --skill worker-management -g -a claude-code -y- Repository
- agentscope-ai/AgentTeams5.9k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,988 tokens
- Runs scripts
- Yes, review before use
What it does
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.
-
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. -
Runtime, pick one. The actual default is whatever admin chose at install, read
${AGENTTEAMS_DEFAULT_WORKER_RUNTIME}(controller falls back toopenclawonly 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 openclawNode.js ~500MB General tasks. Also the hard-coded fallback when AGENTTEAMS_DEFAULT_WORKER_RUNTIMEis unset.copaw(legacy)Python ~150MB Do not create new (EOL). Legacy context only: migrating existing CoPaw workers to QwenPaw. qwenpawPython ~150MB QwenPaw 2.0 worker behavior or CoPaw-to-QwenPaw migration. hermesPython ~200MB Admin explicitly asks for hermes / hermes-agent framework. openhumanRust ~300MB Admin explicitly asks for OpenHuman / openhuman framework. Native Matrix support with E2EE.
