xclaw-openclaw

Routes OpenClaw CLI commands through a local wrapper to avoid conflicts.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/polaris-dxz/xclaw --skill xclaw-openclaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xclaw-openclaw
Source: https://github.com/polaris-dxz/xclaw/tree/main/apps/desktop/openclaw-runtime/config/skills/xclaw-openclaw
Command: npx skills add https://github.com/polaris-dxz/xclaw --skill xclaw-openclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a safe, in-app wrapper for the OpenClaw CLI by routing all commands through the bundled xclaw scripts, avoiding conflicts with any globally installed openclaw.

Core Features & Use Cases

  • Safe CLI routing: all OpenClaw commands (config, cron, models, skills, plugins, and daemon operations) run through the xclaw wrapper to ensure correct environment binding and wall-clock safety.
  • Environment persistence: commands read runtime state from ~/.xclaw/xclaw.json and configuration from ~/.xclaw/openclaw.json, with OpenClaw services managed by the Electron daemon.
  • Cross-platform support: macOS/Linux via xclaw-mac.sh and Windows via xclaw-win.cmd, providing a unified interface for OpenClaw management.

Quick Start

Run the provided xclaw wrapper to execute OpenClaw CLI commands safely within the app-managed environment.

Frequently Asked Questions about xclaw-openclaw

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

FAQPage Schema
How do I prevent CLI conflicts with a system-wide OpenClaw installation?▼

To prevent CLI conflicts with a system-wide OpenClaw installation, route all commands through a local wrapper to enforce correct environment binding. This isolates runtime state and configuration from global installations.

How do I run OpenClaw commands safely within an Electron app environment?▼

Run OpenClaw commands safely within an Electron app by using bundled wrapper scripts for execution. The Electron daemon supervises OpenClaw services to ensure wall-clock safety and correct environment binding.

Where does the local OpenClaw wrapper store runtime state and configuration?▼

The local OpenClaw wrapper stores runtime state in ~/.xclaw/xclaw.json and configuration in ~/.xclaw/openclaw.json. This enforces using local runtime state to manage config, cron, and models safely.

Does the OpenClaw CLI wrapper support both macOS and Windows environments?▼

Yes, the OpenClaw CLI wrapper supports macOS and Linux via xclaw-mac.sh and Windows via xclaw-win.cmd. This provides a unified interface for OpenClaw management across platforms.

What OpenClaw CLI operations are covered by the local wrapper?▼

The local wrapper covers OpenClaw CLI operations across config, cron, models, skills, plugins, and service management. It targets environments without a global OpenClaw CLI installation.

Why should I use a wrapper script instead of calling OpenClaw directly?▼

Use a wrapper script instead of calling OpenClaw directly to ensure commands read from local runtime state and config files. This prevents execution conflicts with any globally installed openclaw.