Asosiy tarkibga o'tish

OpenClaw’ni yangi mashinaga ko‘chirish

Ushbu qo‘llanma OpenClaw Gateway’ni bir mashinadan boshqasiga onboarding’ni qayta bajarilmasdan ko‘chiradi. Migratsiya kontseptual jihatdan sodda:
  • Holat katalogini nusxalang ($OPENCLAW_STATE_DIR, standart: ~/.openclaw/) — bu konfiguratsiya, autentifikatsiya, sessiyalar va kanal holatini o‘z ichiga oladi.
  • Workspace’ingizni nusxalang (standart bo‘yicha ~/.openclaw/workspace/) — bu agent fayllaringizni (xotira, promptlar va hokazo) o‘z ichiga oladi.
Ammo profillar, ruxsatlar va qisman nusxalar bilan bog‘liq keng tarqalgan xatolar mavjud.

Boshlashdan oldin (nimani ko‘chiryapsiz)

1. Identify your state directory

Ko‘pchilik o‘rnatishlar standart sozlamadan foydalanadi:
  • Holat katalogi: ~/.openclaw/
Ammo quyidagilardan foydalansangiz, u boshqacha bo‘lishi mumkin:
  • --profile <name> (odatda ~/.openclaw-<profile>/ ga aylanadi)
  • OPENCLAW_STATE_DIR=/some/path
Agar ishonchingiz komil bo‘lmasa, eski kompyuterda quyidagini ishga tushiring:
openclaw status
Look for mentions of OPENCLAW_STATE_DIR / profile in the output. If you run multiple gateways, repeat for each profile.

2. Identify your workspace

Keng tarqalgan standartlar:
  • ~/.openclaw/workspace/ (tavsiya etilgan ish maydoni)
  • siz yaratgan maxsus papka
Your workspace is where files like MEMORY.md, USER.md, and memory/*.md live.

3. Understand what you will preserve

If you copy both the state dir and workspace, you keep:
  • Gateway configuration (openclaw.json)
  • Auth profiles / API keys / OAuth tokens
  • Session history + agent state
  • Channel state (e.g. WhatsApp login/session)
  • Your workspace files (memory, skills notes, etc.)
If you copy only the workspace (e.g., via Git), you do not preserve:
  • sessions
  • credentials
  • channel logins
Those live under $OPENCLAW_STATE_DIR.

Step 0 — Make a backup (old machine)

On the old machine, stop the gateway first so files aren’t changing mid-copy:
openclaw gateway stop
(Optional but recommended) archive the state dir and workspace:
# Adjust paths if you use a profile or custom locations
cd ~
tar -czf openclaw-state.tgz .openclaw

tar -czf openclaw-workspace.tgz .openclaw/workspace
If you have multiple profiles/state dirs (e.g. ~/.openclaw-main, ~/.openclaw-work), archive each.

Step 1 — Install OpenClaw on the new machine

On the new machine, install the CLI (and Node if needed): At this stage, it’s OK if onboarding creates a fresh ~/.openclaw/ — you will overwrite it in the next step.

Step 2 — Copy the state dir + workspace to the new machine

Copy both:
  • $OPENCLAW_STATE_DIR (default ~/.openclaw/)
  • your workspace (default ~/.openclaw/workspace/)
Common approaches:
  • scp the tarballs and extract
  • rsync -a over SSH
  • external drive
After copying, ensure:
  • Hidden directories were included (e.g. .openclaw/)
  • File ownership is correct for the user running the gateway

1. 3-qadam — Doktorni ishga tushirish (migratsiyalar + xizmatlarni tiklash)

  1. yangi mashinada:
3. openclaw doctor
  1. Doctor — bu “xavfsiz va zerikarli” buyruq. 5. U xizmatlarni tuzatadi, konfiguratsiya migratsiyalarini qo‘llaydi va nomuvofiqliklar haqida ogohlantiradi.
  2. So‘ng:
7. openclaw gateway restart
openclaw status

8. Keng tarqalgan xatolar (va ularni qanday oldini olish)

9. Xato: profil / state-dir nomuvofiqligi

  1. Agar eski gateway’ni profil (yoki OPENCLAW_STATE_DIR) bilan ishga tushirgan bo‘lsangiz va yangi gateway boshqasidan foydalansa, quyidagi alomatlarni ko‘rasiz:
  • Yechim: migratsiya qilingan xuddi shu profil/state dir’dan foydalanib gateway/xizmatni ishga tushiring, so‘ng yana ishga tushiring:
    1. kanallar yo‘qolgan / tizimdan chiqib ketgan
    1. bo‘sh sessiya tarixi
  1. Yechim: migratsiya qilingan xuddi shu profil/state dir’dan foydalanib gateway/xizmatni ishga tushiring, so‘ng yana ishga tushiring:
15. openclaw doctor

16. Xato: faqat openclaw.json ni ko‘chirish

  1. openclaw.json yetarli emas. 18. Ko‘plab provayderlar holatni quyida saqlaydi:
  • $OPENCLAW_STATE_DIR/credentials/
  • $OPENCLAW_STATE_DIR/agents/<agentId>/...
  1. Har doim butun $OPENCLAW_STATE_DIR papkasini migratsiya qiling.

22. Xato: ruxsatlar / egalik

  1. Agar root sifatida ko‘chirgan bo‘lsangiz yoki foydalanuvchini o‘zgartirgan bo‘lsangiz, gateway credential’lar/sessiyalarni o‘qiy olmasligi mumkin.
  2. Yechim: state dir va workspace gateway’ni ishga tushirayotgan foydalanuvchiga tegishli ekanini ta’minlang.

25. Xato: masofaviy/mahalliy rejimlar o‘rtasida migratsiya

    1. Agar UI (WebUI/TUI) masofaviy gateway’ga ulanayotgan bo‘lsa, sessiya ombori va workspace masofaviy xostga tegishli bo‘ladi.
    1. Noutbukingizni migratsiya qilish masofaviy gateway’ning holatini ko‘chirmaydi.
  1. Agar masofaviy rejimda bo‘lsangiz, gateway xostini migratsiya qiling.

29. Xato: zaxira nusxalardagi sirlar

  1. $OPENCLAW_STATE_DIR ichida sirlar mavjud (API kalitlari, OAuth tokenlari, WhatsApp credential’lari). 31. Zaxira nusxalarini ishlab chiqarish sirlaridek ko‘ring:
  • Yangi mashinada quyidagilarni tasdiqlang:
    1. xavfsiz bo‘lmagan kanallar orqali ulashishdan saqlaning
    1. oshkor bo‘lganidan shubhalansangiz, kalitlarni aylantiring

35. Tekshiruv ro‘yxati

  1. Yangi mashinada quyidagilarni tasdiqlang:
    1. openclaw status gateway ishlayotganini ko‘rsatadi
    1. Kanallaringiz hanuz ulangan (masalan, WhatsApp qayta juftlashni talab qilmaydi)
    1. Boshqaruv paneli ochiladi va mavjud sessiyalarni ko‘rsatadi
    1. Workspace fayllaringiz (xotira, konfiguratsiyalar) mavjud

41. Bog‘liq