openclaw-config

Configures OpenClaw gateway JSON5 to connect Docker services to messaging channels and AI providers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill openclaw-config-elvinouyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-config
Source: https://github.com/ElvinOuyang/claude-skill-collection/tree/main/plugins/openclaw-config/skills/openclaw-config
Command: npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill openclaw-config-elvinouyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you configure OpenClaw, a self-hosted personal AI gateway running in Docker, so it can securely connect messaging channels to AI providers using the right settings and secrets management.

Core Features & Use Cases

  • Docker deployment & onboarding: Guides you through using the OpenClaw Docker image and operational setup scripts.
  • Correct openclaw.json gateway configuration: Explains how to set gateway bind mode, port, and authentication safely (e.g., loopback vs lan).
  • Provider API keys without hardcoding: Shows how to store secrets in ~/.openclaw/.env and reference them in openclaw.json using env var interpolation.
  • Messaging channel integration: Walks you through adding channels (such as Telegram) via the OpenClaw CLI and/or editing channels in the config.

Quick Start

Ask the assistant: “Help me configure OpenClaw on my server with Docker for Telegram and set my Anthropic and OpenAI API keys without hardcoding them.”

Frequently Asked Questions about openclaw-config

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

FAQPage Schema
How do I configure OpenClaw in Docker to connect Telegram without hardcoding API keys?

To configure OpenClaw in Docker, store your provider API keys as secrets in the ~/.openclaw/.env file and reference them in openclaw.json using ${VAR_NAME} environment variable interpolation. This securely connects messaging channels like Telegram without hardcoding sensitive keys.

How do I set up gateway bind mode and authentication for a Docker AI gateway on my local network?

Setting up gateway bind mode and authentication involves editing the JSON5 configuration at ~/.openclaw/openclaw.json. You choose between loopback for localhost-only access or lan for local network access, then define authentication parameters to secure the Docker-hosted AI gateway.

What is the correct file path and format for editing OpenClaw gateway configuration?

The OpenClaw gateway configuration uses the JSON5 format and is located at ~/.openclaw/openclaw.json. This file manages gateway bind settings, port assignments, provider API keys, and messaging channel integration for Docker-hosted services.

Can I manage Telegram channel integration and provider settings using the OpenClaw CLI?

Yes, you can enable and manage messaging channels such as Telegram using the OpenClaw CLI via docker compose commands. Alternatively, you can directly edit the channel configurations within the openclaw.json file to integrate your AI providers.

Why does my OpenClaw container lose access to API keys configured in the JSON5 file?

Container access issues usually occur when secrets are hardcoded instead of interpolated. You must store secrets in ~/.openclaw/.env and reference them in openclaw.json using ${VAR_NAME} syntax to ensure the Docker container properly loads environment variables.

Does OpenClaw Docker configuration support both localhost and LAN deployments?

Yes, OpenClaw supports both localhost and LAN deployments. You configure the gateway bind mode in openclaw.json to either loopback for localhost-only access or lan for local network access, ensuring secure container access based on your deployment context.