openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@9624d81bb3

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-27 05:02:07 +00:00
parent 635e7e862e
commit e2dbf2f223
6 changed files with 25 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "6c49039a23a9e0e3e3eb8029f711aae50fbf831a",
"syncedAt": "2026-04-27T04:58:17.292Z"
"sha": "9624d81bb34ce008ad508ada7323f35572427352",
"syncedAt": "2026-04-27T05:00:42.566Z"
}

5
docs/install/development-channels.md
View File

@ -46,8 +46,9 @@ install method:
`OPENCLAW_GIT_DIR`), switches to `main`, rebases on upstream, builds, and
installs the global CLI from that checkout.
Tip: if you want stable + dev in parallel, keep two clones and point your
gateway at the stable one.
<Tip>
If you want stable and dev in parallel, keep two clones and point your gateway at the stable one.
</Tip>
## One-off version or tag targeting

6
docs/install/exe-dev.md
View File

@ -48,9 +48,9 @@ Then connect:
ssh <vm-name>.exe.xyz
```
Tip: keep this VM **stateful**. OpenClaw stores `openclaw.json`, per-agent
`auth-profiles.json`, sessions, and channel/provider state under
`~/.openclaw/`, plus the workspace under `~/.openclaw/workspace/`.
<Tip>
Keep this VM **stateful**. OpenClaw stores `openclaw.json`, per-agent `auth-profiles.json`, sessions, and channel/provider state under `~/.openclaw/`, plus the workspace under `~/.openclaw/workspace/`.
</Tip>
## 2) Install prerequisites (on the VM)

4
docs/install/hetzner.md
View File

@ -253,7 +253,9 @@ For teams preferring infrastructure-as-code workflows, a community-maintained Te
This approach complements the Docker setup above with reproducible deployments, version-controlled infrastructure, and automated disaster recovery.
> **Note:** Community-maintained. For issues or contributions, see the repository links above.
<Note>
Community-maintained. For issues or contributions, see the repository links above.
</Note>
## Next steps

4
docs/install/macos-vm.md
View File

@ -92,7 +92,9 @@ lume create openclaw --os macos --ipsw latest
This downloads macOS and creates the VM. A VNC window opens automatically.
Note: The download can take a while depending on your connection.
<Note>
The download can take a while depending on your connection.
</Note>
---

22
docs/install/migrating.md
View File

@ -6,26 +6,26 @@ read_when:
title: "Migration guide"
---
# Migrating OpenClaw to a New Machine
# Migrating OpenClaw to a new machine
This guide moves an OpenClaw gateway to a new machine without redoing onboarding.
Move an OpenClaw gateway to a new machine without redoing onboarding.
## What Gets Migrated
## What gets migrated
When you copy the **state directory** (`~/.openclaw/` by default) and your **workspace**, you preserve:
- **Config** -- `openclaw.json` and all gateway settings
- **Auth** -- per-agent `auth-profiles.json` (API keys + OAuth), plus any channel/provider state under `credentials/`
- **Sessions** -- conversation history and agent state
- **Channel state** -- WhatsApp login, Telegram session, etc.
- **Workspace files** -- `MEMORY.md`, `USER.md`, skills, and prompts
- **Config** — `openclaw.json` and all gateway settings.
- **Auth** — per-agent `auth-profiles.json` (API keys plus OAuth), plus any channel or provider state under `credentials/`.
- **Sessions** — conversation history and agent state.
- **Channel state** — WhatsApp login, Telegram session, and similar.
- **Workspace files** — `MEMORY.md`, `USER.md`, skills, and prompts.
<Tip>
Run `openclaw status` on the old machine to confirm your state directory path.
Custom profiles use `~/.openclaw-<profile>/` or a path set via `OPENCLAW_STATE_DIR`.
</Tip>
## Migration Steps
## Migration steps
<Steps>
<Step title="Stop the gateway and back up">
@ -70,7 +70,7 @@ Custom profiles use `~/.openclaw-<profile>/` or a path set via `OPENCLAW_STATE_D
</Step>
</Steps>
## Common Pitfalls
## Common pitfalls
<AccordionGroup>
<Accordion title="Profile or state-dir mismatch">
@ -102,7 +102,7 @@ Custom profiles use `~/.openclaw-<profile>/` or a path set via `OPENCLAW_STATE_D
</Accordion>
</AccordionGroup>
## Verification Checklist
## Verification checklist
On the new machine, confirm: