Problem
The OpenClaw adapter exports a single workspace for the parent agent and only lists sub-agents as metadata in AGENTS.md. It does not generate separate OpenClaw workspaces for each sub-agent.
OpenClaw's multi-agent model uses separate workspace directories per agent (workspace-main/, workspace-coding/, etc.), each with its own SOUL.md, AGENTS.md, TOOLS.md. Agents are configured in openclaw.json via an agents.list array.
Current behavior
gitagent export -f openclaw -d examples/full
Outputs a single workspace with sub-agents listed as metadata only.
Expected behavior
Each sub-agent in agents/ should produce its own OpenClaw workspace directory with full SOUL.md, AGENTS.md, TOOLS.md, and skills. The openclaw.json should list all agents with separate workspace paths.
Acceptance criteria
Problem
The OpenClaw adapter exports a single workspace for the parent agent and only lists sub-agents as metadata in AGENTS.md. It does not generate separate OpenClaw workspaces for each sub-agent.
OpenClaw's multi-agent model uses separate workspace directories per agent (
workspace-main/,workspace-coding/, etc.), each with its own SOUL.md, AGENTS.md, TOOLS.md. Agents are configured inopenclaw.jsonvia anagents.listarray.Current behavior
Outputs a single workspace with sub-agents listed as metadata only.
Expected behavior
Each sub-agent in
agents/should produce its own OpenClaw workspace directory with full SOUL.md, AGENTS.md, TOOLS.md, and skills. Theopenclaw.jsonshould list all agents with separate workspace paths.Acceptance criteria
exportToOpenClaw()returnssubAgentsarray with full workspace files per sub-agentopenclaw.jsonuses multi-agent format withagents.listand per-agent workspace pathsexportToOpenClawString()outputs separate workspace sections per sub-agent