sessions_spawn permission issue: "allowed: none" despite configuration (Global tools.allow conflict?
Hello, I am experiencing an issue where my main agent is unable to spawn sub-agents, despite configuring the permissions.
Error Message:
When the agent tries to call sessions_spawn, it returns the following error:
agentId is not allowed for sessions_spawn (allowed: none)
My Configuration (~/.openclaw/openclaw.json):
I have explicitly enabled agentToAgent and allowed sessions_spawn in my configuration file:
"tools": {
"agentToAgent": {
"enabled": true,
"allow": [ "sessions_spawn" ]
}
}
Steps Taken:
Added the configuration above to openclaw.json.
Restarted the gateway (openclaw gateway restart).
Verified that there are no policy.yaml files overriding this setting (find command returned nothing).
However, the agent still reports that the tool is globally blocked or not allowed.
Question:
Is there a hidden global policy or another configuration layer I am missing? How can I enable sessions_spawn for my main agent?
Error Message:
When the agent tries to call sessions_spawn, it returns the following error:
agentId is not allowed for sessions_spawn (allowed: none)
My Configuration (~/.openclaw/openclaw.json):
I have explicitly enabled agentToAgent and allowed sessions_spawn in my configuration file:
"tools": {
"agentToAgent": {
"enabled": true,
"allow": [ "sessions_spawn" ]
}
}
Steps Taken:
Added the configuration above to openclaw.json.
Restarted the gateway (openclaw gateway restart).
Verified that there are no policy.yaml files overriding this setting (find command returned nothing).
However, the agent still reports that the tool is globally blocked or not allowed.
Question:
Is there a hidden global policy or another configuration layer I am missing? How can I enable sessions_spawn for my main agent?
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?
