docs(kilo-docs): add workspace migration section to KiloClaw FAQ#8287
Merged
docs(kilo-docs): add workspace migration section to KiloClaw FAQ#8287
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
|
|
||
| Ask your Claw to push the workspace to a GitHub repository: | ||
|
|
||
| > Create a new GitHub repo and push your entire workspace there with the `gh` CLI. Tell me the URL of the repo you used. |
Contributor
Author
There was a problem hiding this comment.
WARNING: GitHub repo backup can produce incomplete restores
Pushing the entire workspace into a new GitHub repository does not faithfully preserve common /root/clawd layouts. Nested project repositories are typically recorded as gitlinks instead of full contents, and anything not committed into the temporary backup repo is dropped on restore. That makes this migration path prone to silent data loss unless it is limited to non-nested workspaces or changed to use an archive-based backup.
Contributor
Author
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional issues found outside the diff. Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by gpt-5.4-20260305 · 136,500 tokens |
…AQ page Move the 'Migrating Your Workspace' content from dashboard.md to faq/general.md where it better fits as a frequently asked question. The FAQ version is expanded with a clear what-migrates/what-doesn't breakdown, workspace memory/context note, and step-by-step integration reconfiguration instructions.
kilo-code-bot
bot
changed the title
…n scenarios Rewrite the migration section to explicitly cover three use cases: - Migrating from another OpenClaw provider to KiloClaw - Moving between KiloClaw instances (individual to org or vice versa) - Leaving KiloClaw for another OpenClaw provider Clarify that the process is the same for all three, and distinguish what migrates via backup/restore (workspace files, memory, context) from what needs manual reconfiguration (integrations).
Updated migration instructions for OpenClaw to clarify workspace migration process and reconfiguration of integrations.
LigiaZ
approved these changes
Apr 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Built for Alex Gold by Kilo for Slack