OpenClaw is a self-hosted gateway for using agents through messaging channels and a browser dashboard. Its personal assistant guide describes an assistant that stays available through a running gateway. It suits users who want control over hosting, workspaces and connections.
Start with the dashboard
Follow the current quickstart. It currently requires Node.js 24.16+ or 26.1+ and recommends Node 26. Run npx openclaw@latest, review the provider and permissions selected by onboarding, and confirm one response in the dashboard before connecting a messaging account. This command downloads and runs software; read the official install options first.
The foreground gateway stops with its terminal. For background service setup, the guide documents openclaw gateway install, then openclaw gateway status and openclaw dashboard. A service still depends on its host being awake and online. We have not executed these commands for this listing.
Memory, channels and ongoing work
Workspace files hold instructions and context; the default workspace is ~/.openclaw/workspace. Review stored facts rather than assuming every conversation is remembered correctly. For WhatsApp, the official guide recommends a separate assistant number and an explicit sender allowlist. Other channels have their own setup and access controls.
Inspect openclaw automations list --all after setup: proactive work may already be configured. Keep only the jobs you need, with bounded tools, recipients and frequency. Compare this gateway approach with Hermes and hosted products in our personal agent guide.
What running it costs
The project uses the MIT license. That covers the software, not inference, connected services or hosting. A local model also needs compatible hardware. Check the billing terms of the exact authentication route selected by onboarding; an existing subscription is not universal API credit.
Reviewed against official sources on October 23, 2026. No installation, model benchmark or unattended task was tested by this site.