At a glance
Usual causes	The computer sleeps or drops Wi-Fi; the gateway isn't running as a background service; an update changed the config; your AI provider's login or limit
First commands	`openclaw status`, `openclaw gateway status`, `openclaw doctor`, `openclaw logs --follow`
Stays with you	Your accounts, your keys, and what the agent may do while it's down or recovering
Rough cost	An hour or two of your time for the common causes (a rough estimate)
Skip it if	You only used it for chat: the ChatGPT or Claude app may be enough

1What it looks like when it keeps working

You message your agent and it answers. Its morning jobs run. You don't think about the gateway, and you haven't reset it in weeks. That's the goal, and it's reachable on a Mac mini, a Windows PC or a Linux box at home.

What people describe instead is familiar: it "constantly stops working", and they reset the gateway again and again until they're "about to give up". Others nuke the install and start fresh. Starting fresh often works for a while, which hides the cause. The cause is usually one of these:

The computer sleeps: OpenClaw's own FAQ lists it for laptops: sleep and network drops disconnect the gateway, and OS updates and reboots interrupt it. A Mac mini that's never touched can still nap.
It goes quiet on a Mac, then wakes when you look: OpenClaw's docs describe this exactly: macOS maintenance sleep briefly drops Wi-Fi, the gateway crashes, and after a few crashes macOS stops restarting it until you log in, open the dashboard or SSH in. Older releases were hit hardest; 2026.5.26 and newer treat those network blips as warnings.
The gateway isn't a service: If you started it in a terminal window, it stops when that window closes or the user logs out. OpenClaw can install itself as a background service (a LaunchAgent on a Mac, a systemd user service on Linux and WSL2) that starts on its own.
Two copies fight: A second install or service on the same computer competes for the same port. The log says EADDRINUSE or "another gateway instance is already listening".
An update changed things: OpenClaw ships often. Its troubleshooting page says most breakage after an upgrade is "config drift or stricter defaults now being enforced".
The AI provider said no: An expired login, a used-up limit or a long-context rule shows as errors in the log (for example, an HTTP 429 from Anthropic), not as a crash.

2Finding the cause and fixing it, end to end

Run openclaw status and openclaw gateway status. You want "Runtime: running" and "Connectivity probe: ok". If it says the service isn't loaded, it was never installed as one.
Run openclaw doctor. It checks the config and the service, and openclaw doctor --fix repairs what it can, such as a service still pointing at an old port.
Watch openclaw logs --follow while you message the agent. Repeating errors name the cause: a port conflict, an auth error from your provider, a channel that's been logged out.
If it was started by hand, install it as a service with openclaw gateway install (or rerun onboarding), so it starts with the computer and restarts when it stops.
Stop the computer sleeping. On a Mac mini kept as a server, OpenClaw's docs suggest sudo pmset -a sleep 0 disksleep 0 standby 0 powernap 0; on Windows, set sleep to "Never" on mains power.
Update with openclaw update rather than reinstalling, then run openclaw doctor and openclaw health. Recent releases check the new version before switching to it.
Check it again tomorrow morning. If it went quiet overnight, the logs will show when, and you'll know which cause it was.

If you'd like another AI to read the evidence for you, openclaw triage writes a cleaned-up diagnosis you can paste to it.

3What stays with you

Your keys and logins: Don't paste API keys, gateway tokens or passwords into a public post asking for help. openclaw triage writes a cleaned-up report meant for sharing; read it before you post it anyway.
What it may do: A fresh local install turns on the full tool profile, and command approvals are off by default. While you're fixing things, decide what it should ask before doing. In the setups I do, it asks before it spends money or sends anything.
Exposing it to the internet: To reach it from your phone, OpenClaw's docs recommend keeping the gateway on the local machine and using Tailscale Serve, and never exposing it without a login. Opening a port to the internet to "fix" a connection problem trades it for a bigger one.

4When the fix doesn't hold

It still goes quiet overnight: On a Mac, OpenClaw's docs suggest a small watchdog that checks the service every few minutes and restarts it. On upkeep, I set that up and watch it.
An update broke it again: Run openclaw doctor first. OpenClaw's update docs cover rolling back, and recommend a verified backup before updating.
A channel keeps logging out: WhatsApp, Telegram and the rest each have their own login. openclaw channels status --probe shows which one dropped.
You fix one thing and another breaks: That's the point where it has become a second job. It's also the point where most people give up, and where upkeep earns its price.

5What it costs

Item	What it means
OpenClaw	Free and open source.
Your time	An hour or two for the common causes above, if you're comfortable in a terminal (a rough estimate). Longer if the cause is in a channel or a provider.
The computer	The one you have, set never to sleep. A Mac mini left on uses about 50 cents of electricity a month at the US average price (selfhostedaiagent.com).
A rented server, instead	OpenClaw's FAQ suggests one if you've had gateway disconnects before: always on, no sleep. It costs every month, and your agent and its files live on someone else's computer.

Doing it yourself

Run openclaw status, openclaw gateway status and openclaw doctor, and read what they say.
Watch openclaw logs --follow while you message the agent, and note any repeating error.
Install the gateway as a service if it isn't one, and remove any second copy.
Turn off sleep on the computer that runs it.
Update with openclaw update, then run openclaw doctor and openclaw health.
Check it the next morning, and keep notes of what you changed.

OpenClaw's troubleshooting page is the place to start; everything above comes from it and the pages it links.

6When not to bother

You only chatted with it. If you asked questions and drafted text, the ChatGPT or Claude app does that with no gateway to keep alive.
You're trying it out on your everyday laptop. OpenClaw's FAQ calls that fine for testing, but expect pauses when it sleeps or updates. Move it to a computer that stays on before trusting it with daily jobs.
You don't have a job for it yet. Keeping an agent running only pays off when it does something you'd otherwise do yourself. Pick the job first.

If a $20 subscription does it, I'll tell you.

7Want this running on your own computer?

I'll set it up, and keep it running if you like. On a Mac mini, a Windows PC or Omarchy, with the agent you use or want: OpenClaw, Hermes, Claude Code, Codex or another. Out of the box, it asks before it spends money or sends anything. Tell me about the job and I'll quote it. If a $20 subscription does it, I'll tell you. You keep the computer, the accounts and the setup.

Tell me about the work →

Tyler Mayberry, who runs Cirlet (formerly Animas)

Cirlet sets up assistants and teaches teams at independent insurance agencies nationwide. Monthly live training and lifetime learning-library access are included. Open the team training library.

"My OpenClaw keeps breaking": what's going on and what to do