### Start OpenClaw Onboarding Wizard

Source: https://deepwiki.com/openclaw/openclaw/1-overview

Initiates the interactive onboarding process for setting up OpenClaw, guiding through model provider configuration, messaging channel linking, and gateway service setup.

```bash
openclaw onboard
```

--------------------------------

### Provider Monitor Pattern Diagram

Source: https://deepwiki.com/openclaw/openclaw/4-messaging-channels

Illustrates the provider monitor pattern used for messaging channel integrations, where each platform's integration runs as a separate process.

```text

```

--------------------------------

### Status Reply Formatting

Source: https://deepwiki.com/openclaw/openclaw/3.5.2-status-and-directives

The `buildStatusReply` function is used to format the collected status components into a single, unified response. It identifies the active runtime environment.

```typescript
buildStatusReply to format these components into a unified response 1-20 It identifies the active runtime, such as the built-in "Pi" runtime or external harnesses like "Codex" 174-192
```

--------------------------------

### Status Message Construction Pipeline

Source: https://deepwiki.com/openclaw/openclaw/3.5.2-status-and-directives

The `handleStatusCommand` function is the main entry point for processing status requests. It orchestrates the gathering of status information from various sources.

```typescript
handleStatusCommand in src/auto-reply/reply/commands-info.ts serves as the primary entry point for status requests 179-200
```

--------------------------------

### Run OpenClaw Security Audit CLI

Source: https://deepwiki.com/openclaw/openclaw/7.2-security-audit-system

Invokes the security audit system via the CLI. Use `--deep` for live probing, `--fix` to attempt auto-remediation, and `--json` for machine-readable output.

```bash
openclaw security audit [--deep] [--fix] [--json]
```

--------------------------------

### Discord Integration (discord.js)

Source: https://deepwiki.com/openclaw/openclaw/4-messaging-channels

Connects to Discord via its gateway, requiring privileged intents such as the Message Content Intent.

```typescript
Message Content Intent
```

--------------------------------

### Programmatic Session Status Inspection

Source: https://deepwiki.com/openclaw/openclaw/3.5.2-status-and-directives

The `SessionStatusTool` enables agents to programmatically inspect their own session state or that of related sessions. This is useful for debugging and monitoring agent behavior.

```typescript
buildTaskStatusSnapshotForRelatedSessionKeyForOwner 193-196
```

--------------------------------

### Message Normalization Utilities

Source: https://deepwiki.com/openclaw/openclaw/4-messaging-channels

Utilities for normalizing chat types and resolving group session identifiers within channel integrations.

```typescript
normalizeChatType
resolveGroupSessionKey
```

--------------------------------

### Telegram Bot Integration (grammY)

Source: https://deepwiki.com/openclaw/openclaw/4-messaging-channels

Production-ready support for Telegram bots, including direct messages and group chats. Supports both long polling and webhook modes.

```typescript
GENERATED_BUNDLED_CHANNEL_CONFIG_METADATA
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.