feat: migrate from clawdbot to openclaw #155
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Upgrade the CLI package from [email protected] to [email protected] and update all references throughout the codebase: - CLI commands: clawdbot → openclaw - Config paths: ~/.clawdbot/clawdbot.json → ~/.openclaw/openclaw.json - Env vars: CLAWDBOT_* → OPENCLAW_* - R2 backup paths: clawdbot/ → openclaw/ - Branding: Moltbot → OpenClaw in docs and comments Includes a one-time migration in start-moltbot.sh that automatically moves existing R2 backups and local configs from old paths to new ones, preserving paired devices and conversation history. Dockerfile also optimized to skip Puppeteer/Chromium downloads and clean up caches to reduce image size.
Author
|
i think it fails the E2E as it cant reach the repository secrets? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
[email protected]to[email protected]clawdbot→openclaw), config paths (~/.clawdbot/→~/.openclaw/), env vars (CLAWDBOT_*→OPENCLAW_*), R2 backup paths, and branding in docs/commentsstart-moltbot.shto automatically move existing R2 backups and local configs from old paths to new ones, preserving paired devices and conversation historyCo-Authored-By: Claude Opus 4.5 [email protected]
Test plan
openclaw --versionruns successfully in the container~/.openclaw/openclaw.jsonclawdbot/— should auto-migrate toopenclaw/pathsopenclaw devicesCLIMOLTBOT_GATEWAY_TOKEN→OPENCLAW_GATEWAY_TOKEN,DEV_MODE→OPENCLAW_DEV_MODEnpm test)Version after the upgrade