Bug Report: sessions_spawn Ignores allowAgents Configuration After All Restart Methods
Hello! We've encountered a persistent issue where sessions_spawn fails to authorize a sub-agent, even when the configuration appears correct. We believe this might be a bug.
Environment:
OpenClaw: v2026.1.30
OS: WSL2 (Linux 6.6.87.2)
Deployment: systemd user service (openclaw-gateway.service)
Goal:
Allow the default agent to spawn a sub-agent with agentId: "Tester".
Configuration in /home/alfredo/.openclaw/openclaw.json:
We've verified the file on disk is correct. The agents.list is configured as follows:
"list": [
{
"id": "default",
"subagents": {
"allowAgents": [
"default",
"Tester"
]
}
},
{
"id": "Tester"
}
]
Troubleshooting Steps Performed:
The configuration was updated, but the issue persists despite:
Using the gateway('restart') tool.
Restarting the service with systemctl --user restart openclaw-gateway.service.
A full, clean restart using systemctl --user stop, daemon-reload, and start.
Result:
Every single attempt to call sessions_spawn({ agentId: "Tester", ... }) fails with the exact same error:
{
"status": "forbidden",
"error": "agentId is not allowed for sessions_spawn (allowed: none)"
}
Conclusion:
The gateway is consistently ignoring the allowAgents configuration, regardless of how the service is restarted. This strongly suggests a bug in how the agent configuration is loaded or applied. Any help would be appreciated
Environment:
OpenClaw: v2026.1.30
OS: WSL2 (Linux 6.6.87.2)
Deployment: systemd user service (openclaw-gateway.service)
Goal:
Allow the default agent to spawn a sub-agent with agentId: "Tester".
Configuration in /home/alfredo/.openclaw/openclaw.json:
We've verified the file on disk is correct. The agents.list is configured as follows:
"list": [
{
"id": "default",
"subagents": {
"allowAgents": [
"default",
"Tester"
]
}
},
{
"id": "Tester"
}
]
Troubleshooting Steps Performed:
The configuration was updated, but the issue persists despite:
Using the gateway('restart') tool.
Restarting the service with systemctl --user restart openclaw-gateway.service.
A full, clean restart using systemctl --user stop, daemon-reload, and start.
Result:
Every single attempt to call sessions_spawn({ agentId: "Tester", ... }) fails with the exact same error:
{
"status": "forbidden",
"error": "agentId is not allowed for sessions_spawn (allowed: none)"
}
Conclusion:
The gateway is consistently ignoring the allowAgents configuration, regardless of how the service is restarted. This strongly suggests a bug in how the agent configuration is loaded or applied. Any help would be appreciated
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
