#Agent setup Question
1 messages · Page 1 of 1 (latest)
Yep — your friend is probably fine 😉
That layout is expected now:
~/.openclaw/agents/mybot/agent= agent state/config/auth~/.openclaw/agents/mybot/sessions= that agent’s sessions~/.openclaw/workspace/mybot= that agent’s workspace, ifagents.defaults.workspaceis set to~/.openclaw/workspace
Older/docs examples may show ~/.openclaw/workspace-mybot; that’s the fallback when there isn’t a shared default workspace root.
To sanity-check, run:
openclaw --version
openclaw agents list --bindings
openclaw config get agents.defaults.workspace
agents default workspace set to .openclaw/workspace why not their own workspace like .openclaw/workspace/mybot, or how do i set it
If agents.defaults.workspace is set to:
"~/.openclaw/workspace"
then OpenClaw treats that as the workspace root.
So usually:
- default agent →
~/.openclaw/workspace - non-default agent
mybot→~/.openclaw/workspace/mybot
If you want to force a specific path, set it per-agent:
{
agents: {
defaults: {
workspace: "~/.openclaw/workspace",
},
list: [
{
id: "mybot",
workspace: "~/.openclaw/workspace/mybot",
},
],
},
}
Or if you prefer the older-looking style:
{
id: "mybot",
workspace: "~/.openclaw/workspace-mybot",
}
One gotcha: if mybot is marked default: true, then it may use agents.defaults.workspace directly instead of appending /mybot.
Worth checking:
openclaw --version
openclaw agents list --bindings
openclaw config get agents