Files

Selig 4c966a3ad2 Initial commit: OpenClaw Skill Collection

6 custom skills (assign-task, dispatch-webhook, daily-briefing,
task-capture, qmd-brain, tts-voice) with technical documentation.
Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.

2026-03-13 10:58:30 +08:00

1.6 KiB

Raw Blame History

Channel Routing

OpenClaw's channel routing system deterministically directs replies back to their originating channel. The system uses agents as isolated workspaces that handle messages across multiple platforms including WhatsApp, Telegram, Discord, Slack, Signal, iMessage, and WebChat.

Key Components

Channels & Session Management

The platform organizes conversations through session keys that vary by context. Direct messages use a main session structure (agent:main:main), while group conversations and threaded discussions receive isolated keys incorporating channel and conversation identifiers.

Routing Priority

Message routing follows a hierarchical matching system:

Exact peer match (highest priority)
Guild/team matching
Account-level routing
Channel-level defaults
Fallback to the primary agent configuration

Multi-Agent Broadcasting

For scenarios requiring simultaneous agent responses, the broadcast groups feature enables "parallel" execution across multiple agents for a single message - useful for support workflows combining human agents with logging systems.

Storage & Configuration

Session data persists in ~/.openclaw/agents/<agentId>/sessions/, supporting both JSON session stores and JSONL transcripts.

Configuration relies on two primary structures:

agents.list for agent definitions
bindings for mapping inbound channels to specific agents

WebChat Integration

WebChat instances attach to selected agents and default to main sessions, enabling cross-channel context visibility within a single interface.

1.6 KiB Raw Blame History