#hey should i use app or cli for openclaw
1 messages · Page 1 of 1 (latest)
If you hated the CLI, pick the path that minimizes it — the CLI is mostly an installer/admin tool, not the “main UI”.
What to choose
- On macOS: use the OpenClaw macOS app. It’s the smoothest onboarding and you can do most things without touching the terminal.
Docs: https://docs.openclaw.ai/start/onboarding-overview and https://docs.openclaw.ai/start/onboarding - On Windows/Linux (or if you want full control): use the CLI wizard (
openclaw onboard). After that you mainly use the Dashboard/Control UI in the browser.
Docs: https://docs.openclaw.ai/start/wizard and Dashboard: https://docs.openclaw.ai/web/dashboard
The “fast path” (even if you use CLI once)
- run onboarding (
openclaw onboard) - then open the web UI (
openclaw dashboard) and do everything there
What OS are you on (macOS / Windows / Linux), and what exactly “sucked” about the CLI last time (errors, confusing config, auth/provider setup)?
it auto runs compacting and memory flush even after disabling it
That behavior is usually “working as designed” when the session is getting close to the model’s context limit:
- Auto-compaction kicks in to prevent context overflow.
- “Memory flush” is a silent pre-compaction turn that tells the agent to write durable notes to disk before compaction.
1) Make sure you’re disabling the right thing
Memory flush is controlled by:
agents.defaults.compaction.memoryFlush.enabled
Docs: https://docs.openclaw.ai/concepts/memory#automatic-memory-flush-pre-compaction-ping
And changes require a gateway restart after editing config.
Quick sanity-check on the gateway host: