configure-openclaw

Configure OpenClaw notification gateway to route OMX session events to HTTP endpoints or CLI commands.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill configure-openclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-openclaw
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/configure-openclaw
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill configure-openclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure OpenClaw as a notification gateway to route OMX session events to an HTTP endpoint or a CLI command.

Core Features & Use Cases

  • Two gateway modes: HTTP gateway and CLI command gateway, enabling OMX to post events to webhooks or execute shell commands.
  • Interactive setup that merges settings into ~/.codex/.omx-config.json, with validation and guardrails.
  • Activation gates, testing steps, and clear guidance to verify proper operation before enabling notifications.

Quick Start

Follow the interactive prompts to configure the OpenClaw gateway and save the settings to ~/.codex/.omx-config.json.

Frequently Asked Questions about configure-openclaw

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

FAQPage Schema
How do I configure a webhook gateway for OMX session events?

Configuring a webhook gateway for OMX session events involves selecting the HTTP gateway mode, providing your endpoint URL, and generating the configuration in ~/.codex/.omx-config.json. The setup includes validation and a test step to verify proper event routing.

Can I route OMX notifications to a CLI command instead of an HTTP endpoint?

Yes, you can route OMX notifications to a CLI command by selecting the CLI command gateway mode. This allows OMX to execute shell commands for session events, requiring the OMX_OPENCLAW_COMMAND environment variable gate for activation and proper deployment constraints.

What environment variables are required to activate the OpenClaw notification gateway?

Activating the OpenClaw notification gateway requires the OMX_OPENCLAW environment variable gate, and the OMX_OPENCLAW_COMMAND variable when using the CLI command gateway mode, ensuring proper security and deployment constraints are enforced.

How do I test if my OpenClaw gateway configuration is working correctly?

You can verify your OpenClaw gateway configuration by using the built-in testing step offered during setup. This validation checks activation gates and verifies proper operation by routing a test event to your defined HTTP endpoint or CLI command.

Does configuring the OMX config file overwrite existing gateway settings?

Configuring the OMX config file does not overwrite existing settings blindly; the interactive setup detects existing configuration and merges new settings into ~/.codex/.omx-config.json while enforcing guardrails and validation to preserve valid data.