#Basic details

1 messages · Page 1 of 1 (latest)

royal tree
#

I need some basic details & help with the system.

slender grottoBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

glass otterBOT
shell aspenBOT
#

Yep, I can help.

If you want troubleshooting, first paste:

openclaw --version

Also send:

  • your OS
  • how you installed OpenClaw
  • what you’re trying to set up
  • the exact error/output

Basic setup details:

  • Node 24 recommended (22.14+ also supported)
  • Fastest install/start path on macOS/Linux:
royal tree
#

OpenClaw version: OpenClaw 2026.4.20 (115f05d)
OS: Windows 11
Installed on: WSL2 Ubuntu Linux

Details I need:

  1. How can I back up the current state of OpenClaw? Including data, memories, history, etc. So I can recover it if something breaks it.

  2. How do I update the OpenCLaw version? I saw a new update and used npm install -g openclaw@latest

now Doctor is saying:

│
◇  Update ──────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│  This install is not a git checkout.                                                      │
│  Run `openclaw update` to update via your package manager (npm/pnpm), then rerun doctor.  │
│                                                                                           │
├───────────────────────────────────────────────────────────────────────────────────────────╯
Error: Cannot find module 'grammy'
Require stack:
- /home/wrakeeb/.npm-global/lib/node_modules/openclaw/dist/extensions/telegram/allowed-updates-BD2bJyzD.js```
#

Reply?

shell aspenBOT
#

I’ve got it, just wanted to verify the docs before guessing. One quick check on that grammy error, then I’ll give you exact steps.

#

Yep. I checked the docs and the package, and I’m pretty sure the grammy error is not your fault.

For WSL2, treat the Linux side as the real host. Your OpenClaw data lives under /home/wrakeeb/..., not Windows %AppData%.

1. Backup

Best built-in option:

mkdir -p ~/Backups
openclaw backup create --verify --output ~/Backups

That backs up:

  • ~/.openclaw (config, credentials, auth, sessions)
  • your workspace, usually ~/.openclaw/workspace
  • memories like AGENTS.md, SOUL.md, USER.md, memory/...
# 
openclaw update

The doctor line about “not a git checkout” is normal for an npm install.
The real problem is the missing grammy module.

I checked the published 2026.4.20 npm package, and it imports grammy but does not declare it as a dependency, which matches your error exactly.

Recommended fix right now

Roll back to the last stable version that still includes those deps:

npm install -g openclaw@2026.4.15
openclaw doctor
# 
openclaw gateway restart

This should not delete your data. It only changes the code install, not ~/.openclaw or your workspace.

Temporary workaround if you want to stay on 2026.4.20

npm install -g grammy @grammyjs/runner @grammyjs/transformer-throttler
openclaw doctor
openclaw gateway restart

That’s more of a band-aid. I’d still recommend pinning 2026.4.15 for now.

Docs:

royal tree
#

Alright. I ran

mkdir -p ~/Backups
openclaw backup create --verify --output ~/Backups

Now where to find this file in my PC And how to keep it safe? Should I run this every time I change something?

shell aspenBOT
#

Since you ran it in WSL2, the file is in the Linux home folder:

/home/wrakeeb/Backups

Quick check:

ls -lh ~/Backups

You should see a timestamped file like:

2026-04-21T...-openclaw-backup.tar.gz
#

How to find it from Windows

Open File Explorer and go to:

\\wsl$\Ubuntu\home\wrakeeb\Backups

If your distro name is different, replace Ubuntu with that distro name.

How to keep it safe

That backup can contain:

  • config
  • memories/workspace files
  • session history
  • tokens/credentials
#

So treat it like a secret file.

Good options:

  • copy it to an external drive
  • store it in a private cloud folder
  • better, store it encrypted (BitLocker drive, encrypted zip/7z, etc.)

Things I would not do:

  • public GitHub
  • public file-sharing links
  • unencrypted random uploads

How often to run it

I would not run a full backup after every tiny change.

Good rule of thumb:

#
  • always before updates/upgrades
  • before changing config/channels/models
  • before risky experiments
  • weekly if the setup matters
  • daily only if you’re actively changing it and care about losing recent history

For frequent small memory/workspace edits, a private git repo for ~/.openclaw/workspace is better than doing full tar backups constantly.

If you want, I can give you:

  1. a best-practice backup routine for WSL2, or
  2. a command that saves backups directly onto your Windows drive instead of inside WSL.
royal tree
#

I don't see the file in my Windows. The location is not accessible

shell aspenBOT
#

Yeah, that usually means the distro name/path isn’t what we guessed.

Try this inside WSL:

wslpath -w ~/Backups

That will print the exact Windows path for your backup folder.
Copy that output and paste it into File Explorer.

Also try this from inside WSL:

cd ~/Backups
explorer.exe .
#

That should open the folder directly in Windows Explorer.

If you just want the backup on your normal Windows drive, easiest is to create the next one straight on C::

openclaw backup create --verify --output /mnt/c/Users/<your-Windows-username>/Downloads

If wslpath -w ~/Backups still gives you trouble, paste its output here and I’ll tell you the exact folder to open.

royal tree
#

Thank you.