openclaw-restart

Restarts the OpenClaw gateway with cron cleanup, stow re-linking, and health verification.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-restart-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-restart
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/openclaw-skills/skills/openclaw-restart
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-restart-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Restarting the OpenClaw gateway with raw launchctl commands can leave broken cron symlinks, stale state, and silent channel failures. This Skill provides a canonical five-step restart sequence that cleans transient cron state, re-applies symlinks, kickstarts the launchd service, and verifies channel recovery. ## Core Features & Use Cases - Safe Restart Sequence: Removes the transient cron jobs file, re-applies GNU stow symlinks, and kickstarts the com.openclaw.gateway launchd service in the correct order. - Crash-Loop Detection: Inspects launchd state after restart and fails explicitly if the gateway is still crash-looping or the health endpoint is unreachable. - Channel Verification: Checks recent logs for Telegram, Slack, or WhatsApp reconnection events and emits a JSON status summary for callers. - Use Case: After editing openclaw.json or rotating channel secrets, run this restart procedure to ensure the gateway picks up changes and all messaging channels reconnect cleanly. ## Quick Start Ask the agent to restart the OpenClaw gateway safely after your config change and verify that all channels reconnect.

Frequently Asked Questions about openclaw-restart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restart the OpenClaw gateway safely?

Remove the transient cron file at ~/.openclaw/cron/jobs.json, re-apply symlinks with stow --no-folding, then run launchctl kickstart -k on gui/$(id -u)/com.openclaw.gateway. Wait about five seconds, then verify the health endpoint and channel logs.

Why not just run launchctl kickstart to restart OpenClaw?

Running launchctl kickstart alone can leave broken cron symlinks unresolved and skip verification of channel reconnection. The full sequence cleans transient cron state first and confirms the gateway is not stuck in a crash loop.

When should I restart the OpenClaw gateway?

Restart after editing openclaw.json, secrets, or channel configs, after stow deploys so the runtime picks up changes, and during incident recovery when the service state is stale or unresponsive.

Why does OpenClaw show a healthy process but channels are not working?

A healthy process without channel log events can indicate partial startup failure, often from missing or mismatched credentials. Check recent logs for Telegram, Slack, or WhatsApp reconnection events and run the status skill to capture startup logs.

How do I detect if the OpenClaw gateway is crash-looping?

Run launchctl print on the gateway service and check for 'last exit reason' containing crash or restart-limit markers. The restart procedure exits non-zero with a JSON error if the gateway remains in a crash loop after kickstart.