OpenClaw Intro & Setup

If you’ve used Claude Code, you can think of OpenClaw as its “async version”—Claude Code is great when you’re sitting at your computer working interactively, while OpenClaw is designed to let AI help you continuously in the background, even when you’re away from your desk.

What OpenClaw Is Actually For

One sentence: Give your AI assistant the ability to access and operate external tools, and interact with you through Telegram and other channels.

The problems it solves:

• AI models can’t reach out to you on their own (you have to ask before they answer)
• AI models have no persistent state (each conversation starts from scratch)
• AI models can’t directly manipulate external systems (GitHub, Notion, servers)

OpenClaw solves all three through the Skill system.

The Skill System

A Skill is the core concept of OpenClaw: each Skill gives your AI a new tool to work with.

Examples of existing Skills:

Install a Skill:

openclaw skill install github

Once installed, you can tell your AI assistant on Telegram “check for new Issues in the claude-code repo today” and it’ll operate GitHub directly.

OpenClaw vs Claude Code

They complement each other: Claude Code handles writing logic and editing code, OpenClaw handles automation and notifications.

My Dual-Machine Setup

I run OpenClaw on two devices:

Mac (admin): Main assistant, daily Q&A and tool calls Linux server (1.9): Dedicated quant machine, 24/7 signal monitoring

Config file on Mac at ~/.openclaw/openclaw.json:

{
  "bot_token": "...",
  "telegram_chat_id": "your_telegram_user_id",
  "model": "claude-opus-4-6",
  "skills": ["github", "obsidian", "weather", "healthcheck"]
}

The Linux server mainly uses the openclaw message send CLI command to push notifications—it doesn’t need full AI capabilities configured.

Scheduled Tasks: Making AI Do Work Proactively

OpenClaw supports cron triggers. I have it send me the weather forecast every morning:

# cron config
0 7 * * * openclaw cron run daily-weather-check

I also attach quant signal scripts and health check scripts to cron—the server runs them automatically and notifies me on Telegram if anything goes wrong.

Who Should Use This

• Multiple machines: Want AI to help manage services scattered across multiple servers
• Need async notifications: Strategy signals, service alerts, scheduled reports
• Tired of building Telegram Bots: One openclaw message send command, no need to implement Bot API yourself

Not ideal for:

• You just want AI to write code (Claude Code is better)
• You need real-time back-and-forth conversation (Claude.ai is better)

Quick Start

# Install
npm install -g openclaw

# Initialize (guided setup for Telegram Bot Token)
openclaw init

# Test sending a message
openclaw message send --channel telegram --target your_user_id --message "test message"

# Install a Skill
openclaw skill install weather

# Start the gateway (so Telegram messages can trigger AI)
openclaw gateway start

Real-World Example: OpenClaw + Quant Trading

OpenClaw’s real value shines in “AI + external system orchestration” scenarios. Here’s one I actually use:

• Trigger: Send “check pionex” on Telegram
• Skill chain: OpenClaw reads the message → queries Pionex API for balances → queries Binance API for positions → Claude synthesizes a risk assessment → pushes back to Telegram

The whole thing completes in 3 seconds. You can ask for position risk 20 times a day without breaking the bank. Details at OpenClaw Quant Workflow.

If you haven’t started on crypto quant trading yet, Pionex has 16 built-in trading bots that work without writing a single line of code—it’s the perfect sandbox for OpenClaw-style AI tooling.

Questions or want to chat about OpenClaw use cases? Find me on Telegram or follow me on X @panshi8848.

📷 Cover image · Generated with Flux Schnell · panshi.io brand style