Skip to content

Comments

fix: update all paths from legacy clawdbot to openclaw convention#1

Open
getmolty wants to merge 2 commits intoclawdbrunner:mainfrom
getmolty:fix/openclaw-directory-paths
Open

fix: update all paths from legacy clawdbot to openclaw convention#1
getmolty wants to merge 2 commits intoclawdbrunner:mainfrom
getmolty:fix/openclaw-directory-paths

Conversation

@getmolty
Copy link

Summary

  • All directory paths updated from legacy ~/clawd/ and ~/.clawdbot/ to ~/.openclaw/
  • Graphiti group names updated from clawdbot-* to openclaw-*
  • LaunchAgent labels updated from com.clawd.* to com.openclaw.*
  • Variable names updated: CLAWD_DIROPENCLAW_DIR
  • Normalized example user group from user-chris to user-main
  • Updated repo URL placeholder to actual upstream

Context

The extension was written when OpenClaw was still called "clawdbot". This caused it to write state and logs to the wrong directories on current OpenClaw installations (~/clawd/ and ~/.clawdbot/ instead of ~/.openclaw/), splitting state across two directory trees and preventing the extension from functioning correctly.

Files changed (16)

All scripts, configs, templates, documentation, and launchd plists updated. Files confirmed unchanged: docker-compose.yml, graphiti-search.sh, .gitignore, LICENSE, infrastructure.example.md, user-profile.example.md.

Test plan

  • Verify grep -rn 'clawdbot\|~/clawd\|\.clawdbot\|com\.clawd\|CLAWD_DIR\|user-chris' . returns zero matches
  • Run install.sh --dry-run and confirm all paths point to ~/.openclaw/
  • Verify LaunchAgent plists reference correct com.openclaw.* labels and ~/.openclaw/ paths
  • Test scripts with a running Graphiti instance

🤖 Generated with Claude Code

Frank and others added 2 commits February 12, 2026 23:22
The extension was written when OpenClaw was still called "clawdbot" and used
~/clawd/ and ~/.clawdbot/ directories. This caused the extension to write
state/logs to the wrong locations on current OpenClaw installations, splitting
state across two directory trees and failing to function correctly.

Changes across 16 files:
- Directory paths: ~/clawd/ and ~/.clawdbot/ → ~/.openclaw/
- Variable names: CLAWD_DIR → OPENCLAW_DIR
- Graphiti group names: clawdbot-* → openclaw-*
- LaunchAgent labels: com.clawd.* → com.openclaw.*
- Normalize example user group: user-chris → user-main
- Update repo URL placeholder to actual upstream

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The Graphiti API returns {"status":"healthy"} but the status script
only checked for {"status":"ok"}, causing it to always report the
API as not responding even when it was running correctly.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Owner

@clawdbrunner clawdbrunner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review

Thanks for the thorough rename — the core clawdbot → openclaw updates (group IDs, LaunchAgent labels, env vars, repo URL) are all correct and welcome. The healthcheck status expansion is a nice catch too.

Requested change: make workspace path configurable

The PR hardcodes workspace files to ~/.openclaw/workspace/ (e.g. ~/.openclaw/workspace/MEMORY.md, ~/.openclaw/workspace/memory/). However, ~/.openclaw/ is the OpenClaw config directory — workspace locations vary per user (e.g. ~/clawd/, ~/my-agent/, etc.).

Please make the workspace path configurable rather than assuming ~/.openclaw/workspace/:

  • In install.sh: add a WORKSPACE_DIR variable (defaulting to $HOME/clawd or similar) separate from OPENCLAW_DIR
  • In Python scripts: use an env var like OPENCLAW_WORKSPACE for MEMORY_DIR, WATCHED_FILES, etc.
  • In docs/README: show it as a configurable value rather than a hardcoded path

This keeps the config dir (~/.openclaw/) and workspace dir as independent concepts, which matches how OpenClaw actually works.

Minor notes

  • The _shared/shared/ rename seems incidental — worth calling out in the description or splitting out
  • user-chrisuser-main is a good generalization for a public repo 👍

Everything else looks solid. Happy to approve once the workspace path is configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants