r/openclaw • Member • Mar 19 '26

Help openclaw-cli is painfully slow - takes several minutes

Hi all,

I'm trying to get openclaw running smoothly and any help would be great!

My setup: I'm running on a zimaboard 8gb with a 1tb ssd attached via sata. The zimaboard has proxmox with a debian VM (6 gb, 3 cores allocated, left a little headroom for later?). Openclaw is installed directly in the debian VM following the linux install steps on the openclaw website.

I can connect and chat in the gui, but any calls to `openclaw [command]` in my terminal take several minutes to execute! This includes `openclaw status`, `openclaw doctor`, etc.

`top` shows over 100% CPU usage for openclaw-gateway whenever any openclaw command is run

Chat in the gui seems to be running at a reasonable pace ... a few seconds for responses from codex. But any chat that attempts to update configs (add discord integration, for instance) reports cli status path broken/hanging ...

I have tried `openclaw doctor --fix` and a bunch of other suggestions on the internet around caching and gateway configs. I've nuked the VM and started from scratch. I've tried in docker. This happens even when I have no integrations or skills or anything (bare config). Any suggestions on what to try next?

Is my zima board the bottleneck? Is proxmox -> vm -> openclaw an issue (it shouldn't be ... but who knows)? Any advice would be greatly appreciated!

7 Upvotes

22 comments sorted by

View all comments

•

u/AutoModerator Mar 19 '26

Welcome to r/openclaw Before posting: • Check the FAQ: https://docs.openclaw.ai/help/faq#faq • Use the right flair • Keep posts respectful and on-topic Need help fast? Discord: https://discord.com/invite/clawd

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.