2dfd73a497
OpenClaw users who started before the rebrand (when the project was clawd/clawdbot) often have a custom workspace directory configured via agents.defaults.workspace in openclaw.json (e.g. ~/clawd/ instead of ~/.openclaw/workspace/). The migration tool only checked hardcoded relative paths (workspace/, workspace-main/, workspace-assistant/) inside the source root, so files like MEMORY.md, skills, and daily memory in custom workspaces were silently skipped. This change: - Reads agents.defaults.workspace from openclaw.json at init time - Uses it as a final fallback in source_candidate() when files aren't found in the standard locations - Standard workspace paths are still preferred (custom is fallback only) - Custom workspace is only used when it's outside the source_root tree (avoids double-matching when workspace/ is the default) Adds two tests: - Custom workspace files are discovered and migrated - Standard workspace location is preferred over custom |
||
|---|---|---|
| .. | ||
| autonomous-ai-agents | ||
| blockchain | ||
| communication | ||
| creative | ||
| devops | ||
| dogfood | ||
| email/agentmail | ||
| health | ||
| mcp | ||
| migration | ||
| mlops | ||
| productivity | ||
| research | ||
| security | ||
| web-development | ||
| DESCRIPTION.md | ||