| name | kars-spawn |
| description | Spawn secure isolated sub-agent sandboxes, delegate tasks via AGT mesh, receive results, and destroy sub-agents. Uses the kars_spawn, kars_mesh_send, kars_mesh_inbox, and kars_spawn_destroy tools. |
| metadata | {"openclaw":{"always":true}} |
kars Sub-Agent Spawn
Spawn secure isolated sub-agent sandboxes on AKS. Each sub-agent runs in its own K8s namespace with full security controls (NetworkPolicy, seccomp, read-only rootfs). Use the kars tools for ALL operations — do NOT use curl.
Available tools
- kars_spawn — create a new sub-agent ({name, model, governance})
- kars_spawn_status — check sub-agent phase ({name})
- kars_spawn_list — list all spawned sub-agents
- kars_mesh_send — send a task via AGT mesh ({to_agent, content})
- kars_mesh_inbox — check inbox for sub-agent responses
- kars_spawn_destroy — tear down a sub-agent ({name})
When to use
- Delegation: spawn a specialist sub-agent for a focused task (security audit, code review, data analysis)
- Parallel work: run multiple sub-agents on different tasks simultaneously
- Isolation: give untrusted code its own sandboxed environment
Workflow
- kars_spawn with
name, model (default: parent's), governance: true, and role (the persona — e.g. "data analyst", , ). The platform tracks the role in a Peer roster and prepends it to every mesh_send so siblings can resolve role references to canonical names.
