better-dsh 0.2.4 → 0.2.5

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/messaging/whatsapp.md

@@ -0,0 +1,283 @@
+---
+sidebar_position: 5
+title: "WhatsApp"
+description: "Set up Hermes Agent as a WhatsApp bot via the built-in Baileys bridge"
+---
+
+# WhatsApp Setup
+
+Hermes connects to WhatsApp through a built-in bridge based on **Baileys**. This works by emulating a WhatsApp Web session — **not** through the official WhatsApp Business API. No Meta developer account or Business verification is required.
+
+> Run `hermes gateway setup` and pick **WhatsApp** for a guided walk-through.
+
+:::tip Two WhatsApp integrations
+This page is for the **Baileys bridge** — quick to set up, personal accounts, no public URL needed, ban risk.
+
+If you're running a real business bot and want stability, see the **[WhatsApp Business Cloud API guide](./whatsapp-cloud.md)** instead. It's the official Meta-supported path: no account ban risk, but requires a Meta Business account and a public webhook URL.
+
+The two adapters can also run in parallel against different phone numbers if you have a reason to.
+:::
+
+:::warning Unofficial API — Ban Risk
+WhatsApp does **not** officially support third-party bots outside the Business API. Using a third-party bridge carries a small risk of account restrictions. To minimize risk:
+- **Use a dedicated phone number** for the bot (not your personal number)
+- **Don't send bulk/spam messages** — keep usage conversational
+- **Don't automate outbound messaging** to people who haven't messaged first
+:::
+
+:::warning WhatsApp Web Protocol Updates
+WhatsApp periodically updates their Web protocol, which can temporarily break compatibility
+with third-party bridges. When this happens, Hermes will update the bridge dependency. If the
+bot stops working after a WhatsApp update, pull the latest Hermes version and re-pair.
+:::
+
+## Two Modes
+
+| Mode | How it works | Best for |
+|------|-------------|----------|
+| **Separate bot number** (recommended) | Dedicate a phone number to the bot. People message that number directly. | Clean UX, multiple users, lower ban risk |
+| **Personal self-chat** | Use your own WhatsApp. You message yourself to talk to the agent. | Quick setup, single user, testing |
+
+---
+
+## Prerequisites
+
+- **Node.js v18+** and **npm** — the WhatsApp bridge runs as a Node.js process
+- **A phone with WhatsApp** installed (for scanning the QR code)
+
+Unlike older browser-driven bridges, the current Baileys-based bridge does **not** require a local Chromium or Puppeteer dependency stack.
+
+---
+
+## Step 1: Run the Setup Wizard
+
+```bash
+hermes whatsapp
+```
+
+The wizard will:
+
+1. Ask which mode you want (**bot** or **self-chat**)
+2. Install bridge dependencies if needed
+3. Display a **QR code** in your terminal
+4. Wait for you to scan it
+
+**To scan the QR code:**
+
+1. Open WhatsApp on your phone
+2. Go to **Settings → Linked Devices**
+3. Tap **Link a Device**
+4. Point your camera at the terminal QR code
+
+Once paired, the wizard confirms the connection and exits. Your session is saved automatically.
+
+:::tip
+If the QR code looks garbled, make sure your terminal is at least 60 columns wide and supports
+Unicode. You can also try a different terminal emulator.
+:::
+
+---
+
+## Step 2: Getting a Second Phone Number (Bot Mode)
+
+For bot mode, you need a phone number that isn't already registered with WhatsApp. Three options:
+
+| Option | Cost | Notes |
+|--------|------|-------|
+| **Google Voice** | Free | US only. Get a number at [voice.google.com](https://voice.google.com). Verify WhatsApp via SMS through the Google Voice app. |
+| **Prepaid SIM** | $5–15 one-time | Any carrier. Activate, verify WhatsApp, then the SIM can sit in a drawer. Number must stay active (make a call every 90 days). |
+| **VoIP services** | Free–$5/month | TextNow, TextFree, or similar. Some VoIP numbers are blocked by WhatsApp — try a few if the first doesn't work. |
+
+After getting the number:
+
+1. Install WhatsApp on a phone (or use WhatsApp Business app with dual-SIM)
+2. Register the new number with WhatsApp
+3. Run `hermes whatsapp` and scan the QR code from that WhatsApp account
+
+---
+
+## Step 3: Configure Hermes
+
+Add the following to your `~/.hermes/.env` file:
+
+```bash
+# Required
+WHATSAPP_ENABLED=true
+WHATSAPP_MODE=bot                          # "bot" or "self-chat"
+
+# Access control — pick ONE of these options:
+WHATSAPP_ALLOWED_USERS=15551234567         # Comma-separated phone numbers (with country code, no +)
+# WHATSAPP_ALLOWED_USERS=*                 # OR use * to allow everyone
+# WHATSAPP_ALLOW_ALL_USERS=true            # OR set this flag instead (same effect as *)
+```
+
+:::tip Allow-all shorthand
+Setting `WHATSAPP_ALLOWED_USERS=*` allows **all** senders (equivalent to `WHATSAPP_ALLOW_ALL_USERS=true`).
+This is consistent with [Signal group allowlists](/reference/environment-variables).
+To use the pairing flow instead, remove both variables and rely on the
+[DM pairing system](/user-guide/security#dm-pairing-system).
+:::
+
+Optional behavior settings in `~/.hermes/config.yaml`:
+
+```yaml
+unauthorized_dm_behavior: pair
+
+whatsapp:
+  unauthorized_dm_behavior: ignore
+```
+
+- `unauthorized_dm_behavior: pair` is the global default. Unknown DM senders get a pairing code.
+- `whatsapp.unauthorized_dm_behavior: ignore` makes WhatsApp stay silent for unauthorized DMs, which is usually the better choice for a private number.
+
+Then start the gateway:
+
+```bash
+hermes gateway              # Foreground
+hermes gateway install      # Install as a user service
+sudo hermes gateway install --system   # Linux only: boot-time system service
+```
+
+The gateway starts the WhatsApp bridge automatically using the saved session.
+
+---
+
+## Session Persistence
+
+The Baileys bridge saves its session under `~/.hermes/platforms/whatsapp/session`. This means:
+
+- **Sessions survive restarts** — you don't need to re-scan the QR code every time
+- The session data includes encryption keys and device credentials
+- **Do not share or commit this session directory** — it grants full access to the WhatsApp account
+
+---
+
+## Re-pairing
+
+If the session breaks (phone reset, WhatsApp update, manually unlinked), you'll see connection
+errors in the gateway logs. To fix it:
+
+```bash
+hermes whatsapp
+```
+
+This generates a fresh QR code. Scan it again and the session is re-established. The gateway
+handles **temporary** disconnections (network blips, phone going offline briefly) automatically
+with reconnection logic.
+
+---
+
+## Voice Messages
+
+Hermes supports voice on WhatsApp:
+
+- **Incoming:** Voice messages (`.ogg` opus) are automatically transcribed using the configured STT provider: local `faster-whisper`, Groq Whisper (`GROQ_API_KEY`), or OpenAI Whisper (`VOICE_TOOLS_OPENAI_KEY`)
+- **Outgoing:** TTS responses are sent as MP3 audio file attachments
+- Agent responses are prefixed with "☤ **Hermes Agent**" by default. You can customize or disable this in `config.yaml`:
+
+```yaml
+# ~/.hermes/config.yaml
+whatsapp:
+  reply_prefix: ""                          # Empty string disables the header
+  # reply_prefix: "🤖 *My Bot*\n──────\n"  # Custom prefix (supports \n for newlines)
+  send_read_receipts: false                 # Mark accepted inbound messages as read (blue ticks)
+```
+
+When `send_read_receipts` is `true`, the adapter marks policy-accepted inbound messages as read after DM/group/mention filtering passes. Rejected messages (e.g., from non-allowlisted senders) are not marked read. Disabled by default for privacy. Changing this setting automatically restarts the bridge subprocess on the next connection.
+
+---
+
+## Message Formatting & Delivery
+
+WhatsApp supports **streaming (progressive) responses** — the bot edits its message in real-time as the AI generates text, just like Discord and Telegram. Internally, WhatsApp is classified as a TIER_MEDIUM platform for delivery capabilities.
+
+### Chunking
+
+Long responses are automatically split into multiple messages at **4,096 characters** per chunk (WhatsApp's practical display limit). You don't need to configure anything — the gateway handles splitting and sends chunks sequentially.
+
+### WhatsApp-Compatible Markdown
+
+Standard Markdown in AI responses is automatically converted to WhatsApp's native formatting:
+
+| Markdown | WhatsApp | Renders as |
+|----------|----------|------------|
+| `**bold**` | `*bold*` | **bold** |
+| `~~strikethrough~~` | `~strikethrough~` | ~~strikethrough~~ |
+| `# Heading` | `*Heading*` | Bold text (no native headings) |
+| `[link text](url)` | `link text (url)` | Inline URL |
+
+Code blocks and inline code are preserved as-is since WhatsApp supports triple-backtick formatting natively.
+
+### Tool Progress
+
+When the agent calls tools (web search, file operations, etc.), WhatsApp displays real-time progress indicators showing which tool is running. This is enabled by default — no configuration needed.
+
+### Native Polls, Clarify-as-Poll, and Locations
+
+The Baileys-bridge adapter (bot mode) supports several native WhatsApp message types:
+
+- **Polls** — the agent can send a native WhatsApp poll (question + options) via the bridge's `/send-poll` endpoint. Poll votes flow back into the conversation.
+- **Clarify questions as polls** — when the agent asks a multiple-choice clarify question, it's rendered as a native single-select poll; tapping an option answers the question. If the poll fails to send, the adapter falls back to a plain text question. Approval prompts are **never** mapped onto polls — polls are only used for genuine multiple-choice clarifies.
+- **Location pins** — the agent can send a native location pin (latitude/longitude, optional name/address) via `/send-location`, and incoming shared locations (including live locations) are delivered to the agent as location messages.
+
+All of this works out of the box in bot (Baileys) mode; no configuration needed.
+
+### Message Batching (Debounce)
+
+WhatsApp delivers each message individually, so a rapid burst (forwarded batches, paste-splits, multi-line text) would otherwise trigger a separate agent invocation per fragment — wasting tokens and producing several disjointed replies. The adapter buffers successive text messages from the same chat and dispatches them as one combined request after a short quiet period (default **5s**, extended to **10s** for very long fragments). Tune via `config.yaml`:
+
+```yaml
+# ~/.hermes/config.yaml
+gateway:
+  platforms:
+    whatsapp:
+      extra:
+        text_batch_delay_seconds: 5.0         # quiet period before flushing a batch
+        text_batch_split_delay_seconds: 10.0  # extended delay near the split threshold
+```
+
+Set `text_batch_delay_seconds: 0` to dispatch each message immediately (disables batching).
+
+### Quoted Replies
+
+Replying to (quoting) an earlier message gives the agent the quoted text as context. Quoting an image, voice note, video or document also attaches that file to the turn, so "what is this?" under a quoted image works — whether the attachment came from another person or from the bot itself (a cron-delivered chart, a generated image). WhatsApp only ships a thumbnail stub with a quote, so the file is resolved from the bridge's download cache (inbound media, in-memory for the bridge's lifetime) or from a local index of the bot's own sends (last 1000 messages); quotes of anything older arrive without the attachment.
+
+---
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| **QR code not scanning** | Ensure terminal is wide enough (60+ columns). Try a different terminal. Make sure you're scanning from the correct WhatsApp account (bot number, not personal). |
+| **QR code expires** | QR codes refresh every ~20 seconds. If it times out, restart `hermes whatsapp`. |
+| **Session not persisting** | Check that `~/.hermes/platforms/whatsapp/session` exists and is writable. If containerized, mount it as a persistent volume. |
+| **Logged out unexpectedly** | WhatsApp unlinks devices after long inactivity. Keep the phone on and connected to the network, then re-pair with `hermes whatsapp` if needed. |
+| **Bridge crashes or reconnect loops** | Restart the gateway, update Hermes, and re-pair if the session was invalidated by a WhatsApp protocol change. |
+| **Bot stops working after WhatsApp update** | Update Hermes to get the latest bridge version, then re-pair. |
+| **macOS: "Node.js not installed" but node works in terminal** | launchd services don't inherit your shell PATH. Run `hermes gateway install` to re-snapshot your current PATH into the plist, then `hermes gateway start`. See the [Gateway Service docs](./index.md#macos-launchd) for details. |
+| **Messages not being received** | Verify `WHATSAPP_ALLOWED_USERS` includes the sender's number (with country code, no `+` or spaces), or set it to `*` to allow everyone. Set `WHATSAPP_DEBUG=true` in `.env` and restart the gateway to see raw message events in `bridge.log`. |
+| **Bot replies to strangers with a pairing code** | Set `whatsapp.unauthorized_dm_behavior: ignore` in `~/.hermes/config.yaml` if you want unauthorized DMs to be silently ignored instead. |
+
+---
+
+## Security
+
+:::warning
+**Configure access control** before going live. Set `WHATSAPP_ALLOWED_USERS` with specific
+phone numbers (including country code, without the `+`), use `*` to allow everyone, or set
+`WHATSAPP_ALLOW_ALL_USERS=true`. Without any of these, the gateway **denies all incoming
+messages** as a safety measure.
+:::
+
+By default, unauthorized DMs still receive a pairing code reply. If you want a private WhatsApp number to stay completely silent to strangers, set:
+
+```yaml
+whatsapp:
+  unauthorized_dm_behavior: ignore
+```
+
+- The `~/.hermes/platforms/whatsapp/session` directory contains full session credentials — protect it like a password
+- Set file permissions: `chmod 700 ~/.hermes/platforms/whatsapp/session`
+- Use a **dedicated phone number** for the bot to isolate risk from your personal account
+- If you suspect compromise, unlink the device from WhatsApp → Settings → Linked Devices
+- Phone numbers in logs are partially redacted, but review your log retention policy

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/messaging/yuanbao.md

@@ -0,0 +1,342 @@
+---
+sidebar_position: 16
+title: "Yuanbao"
+description: "Connect Hermes Agent to the Yuanbao enterprise messaging platform via WebSocket gateway"
+---
+
+# Yuanbao
+
+Connect Hermes to [Yuanbao](https://yuanbao.tencent.com/), Tencent's enterprise messaging platform. The adapter uses a WebSocket gateway for real-time message delivery and supports both direct (C2C) and group conversations.
+
+:::info
+Yuanbao is an enterprise messaging platform primarily used within Tencent and enterprise environments. It uses WebSocket for real-time communication, HMAC-based authentication, and supports rich media including images, files, and voice messages.
+:::
+
+## Prerequisites
+
+- A Yuanbao account with bot creation permissions
+- Yuanbao APP_ID and APP_SECRET (from platform admin)
+- Python packages: `websockets` and `httpx`
+- For media support: `aiofiles`
+
+Install the required dependencies:
+
+```bash
+pip install websockets httpx aiofiles
+```
+
+## Setup
+
+### 1. Create a Bot in Yuanbao
+
+1. Download the Yuanbao app from [https://yuanbao.tencent.com/](https://yuanbao.tencent.com/)
+2. In the app, go to **PAI → My Bot** and create a new bot
+3. After the bot is created, copy the **APP_ID** and **APP_SECRET**
+
+### 2. Run the Setup Wizard
+
+The easiest way to configure Yuanbao is through the interactive setup:
+
+```bash
+hermes gateway setup
+```
+
+Select **Yuanbao** when prompted. The wizard will:
+
+1. Ask for your APP_ID
+2. Ask for your APP_SECRET
+3. Save the configuration automatically
+
+:::tip
+The WebSocket URL and API Domain have sensible defaults built in. You only need to provide APP_ID and APP_SECRET to get started.
+:::
+
+### 3. Configure Environment Variables
+
+After initial setup, verify these variables in `~/.hermes/.env`:
+
+```bash
+# Required
+YUANBAO_APP_ID=your-app-id
+YUANBAO_APP_SECRET=your-app-secret
+YUANBAO_WS_URL=wss://api.yuanbao.example.com/ws
+YUANBAO_API_DOMAIN=https://api.yuanbao.example.com
+
+# Optional: bot account ID (normally obtained automatically from sign-token)
+# YUANBAO_BOT_ID=your-bot-id
+
+# Optional: internal routing environment (e.g. test/staging/production)
+# YUANBAO_ROUTE_ENV=production
+
+# Optional: home channel for cron/notifications (format: direct:<account> or group:<group_code>)
+YUANBAO_HOME_CHANNEL=direct:bot_account_id
+YUANBAO_HOME_CHANNEL_NAME="Bot Notifications"
+
+# Optional: restrict access (legacy, see Access Control below for fine-grained policies)
+YUANBAO_ALLOWED_USERS=user_account_1,user_account_2
+```
+
+### 4. Start the Gateway
+
+```bash
+hermes gateway
+```
+
+The adapter will connect to the Yuanbao WebSocket gateway, authenticate using HMAC signatures, and begin processing messages.
+
+## Features
+
+- **WebSocket gateway** — real-time bidirectional communication
+- **HMAC authentication** — secure request signing with APP_ID/APP_SECRET
+- **C2C messaging** — direct user-to-bot conversations
+- **Group messaging** — conversations in group chats
+- **Media support** — images, files, and voice messages via COS (Cloud Object Storage)
+- **Markdown formatting** — messages are automatically chunked for Yuanbao's size limits
+- **Message deduplication** — prevents duplicate processing of the same message
+- **Heartbeat/keep-alive** — maintains WebSocket connection stability
+- **Typing indicators** — shows "typing…" status while the agent processes
+- **Automatic reconnection** — handles WebSocket disconnections with exponential backoff
+- **Group information queries** — retrieve group details and member lists
+- **Sticker/Emoji support** — send TIMFaceElem stickers and emoji in conversations
+- **WeChat forwarded chat-history support** — when a user forwards a WeChat chat-history bundle into Yuanbao, the adapter decodes the forwarded records (sender nicknames, text, and multimedia entries, including nested forwards) and injects them into the conversation so the agent can read the full forwarded thread
+- **Auto-sethome** — first user to message the bot is automatically set as the home channel owner
+- **Slow-response notification** — sends a waiting message when the agent takes longer than expected
+
+## Configuration Options
+
+### Chat ID Formats
+
+Yuanbao uses prefixed identifiers depending on conversation type:
+
+| Chat Type | Format | Example |
+|-----------|--------|---------|
+| Direct message (C2C) | `direct:<account>` | `direct:user123` |
+| Group message | `group:<group_code>` | `group:grp456` |
+
+### Media Uploads
+
+The Yuanbao adapter automatically handles media uploads via COS (Tencent Cloud Object Storage):
+
+- **Images**: Supports JPEG, PNG, GIF, WebP
+- **Files**: Supports all common document types
+- **Voice**: Supports WAV, MP3, OGG
+
+Media URLs are automatically validated and downloaded before upload to prevent SSRF attacks.
+
+## Home Channel
+
+Use the `/sethome` command in any Yuanbao chat (DM or group) to designate it as the **home channel**. Scheduled tasks (cron jobs) deliver their results to this channel.
+
+:::tip Auto-sethome
+If no home channel is configured, the first user to message the bot will be automatically set as the home channel owner. If the current home channel is a group chat, the first DM will upgrade it to a direct channel.
+:::
+
+You can also set it manually in `~/.hermes/.env`:
+
+```bash
+YUANBAO_HOME_CHANNEL=direct:user_account_id
+# or for a group:
+# YUANBAO_HOME_CHANNEL=group:group_code
+YUANBAO_HOME_CHANNEL_NAME="My Bot Updates"
+```
+
+### Example: Set Home Channel
+
+1. Start a conversation with the bot in Yuanbao
+2. Send the command: `/sethome`
+3. The bot responds: "Home channel set to [chat_name] with ID [chat_id]. Cron jobs will deliver to this location."
+4. Future cron jobs and notifications will be sent to this channel
+
+### Example: Cron Job Delivery
+
+Create a cron job:
+
+```bash
+/cron "0 9 * * *" Check server status
+```
+
+The scheduled output will be delivered to your Yuanbao home channel every day at 9 AM.
+
+## Usage Tips
+
+### Starting a Conversation
+
+Send any message to the bot in Yuanbao:
+
+```
+hello
+```
+
+The bot responds in the same conversation thread.
+
+### Available Commands
+
+All standard Hermes commands work on Yuanbao:
+
+| Command | Description |
+|---------|-------------|
+| `/new` | Start a fresh conversation |
+| `/model [provider:model]` | Show or change the model |
+| `/sethome` | Set this chat as the home channel |
+| `/status` | Show session info |
+| `/help` | Show available commands |
+
+### Sending Files
+
+To send a file to the bot, simply attach it directly in the Yuanbao chat. The bot will automatically download and process the file attachment.
+
+You can also include a message with the attachment:
+
+```
+Please analyze this document
+```
+
+### Receiving Files
+
+When you ask the bot to create or export a file, it sends the file directly to your Yuanbao chat.
+
+## Troubleshooting
+
+### Bot is online but not responding to messages
+
+**Cause**: Authentication failed during WebSocket handshake.
+
+**Fix**:
+1. Verify APP_ID and APP_SECRET are correct
+2. Check that the WebSocket URL is accessible
+3. Ensure the bot account has proper permissions
+4. Review gateway logs: `tail -f ~/.hermes/logs/gateway.log`
+
+### "Connection refused" error
+
+**Cause**: WebSocket URL is unreachable or incorrect.
+
+**Fix**:
+1. Verify the WebSocket URL format (should start with `wss://`)
+2. Check network connectivity to the Yuanbao API domain
+3. Confirm firewall allows WebSocket connections
+4. Test URL with: `curl -I https://[YUANBAO_API_DOMAIN]`
+
+### Media uploads fail
+
+**Cause**: COS credentials are invalid or media server is unreachable.
+
+**Fix**:
+1. Verify API_DOMAIN is correct
+2. Check that media upload permissions are enabled for your bot
+3. Ensure the media file is accessible and not corrupted
+4. Check COS bucket configuration with platform admin
+
+### Messages not delivered to home channel
+
+**Cause**: Home channel ID format is incorrect or cron job hasn't triggered.
+
+**Fix**:
+1. Verify YUANBAO_HOME_CHANNEL is in correct format
+2. Test with `/sethome` command to auto-detect correct format
+3. Check cron job schedule with `/status`
+4. Verify bot has send permissions in the target chat
+
+### Frequent disconnections
+
+**Cause**: WebSocket connection is unstable or network is unreliable.
+
+**Fix**:
+1. Check gateway logs for error patterns
+2. Increase heartbeat timeout in connection settings
+3. Ensure stable network connection to Yuanbao API
+4. Consider enabling verbose logging: `hermes gateway run -vv`
+
+## Access Control
+
+Yuanbao supports fine-grained access control for both DM and group conversations:
+
+```bash
+# DM policy: open (default) | allowlist | disabled
+YUANBAO_DM_POLICY=open
+# Comma-separated user IDs allowed to DM the bot (only used when DM_POLICY=allowlist)
+YUANBAO_DM_ALLOW_FROM=user_id_1,user_id_2
+
+# Group policy: open (default) | allowlist | disabled
+YUANBAO_GROUP_POLICY=open
+# Comma-separated group codes allowed (only used when GROUP_POLICY=allowlist)
+YUANBAO_GROUP_ALLOW_FROM=group_code_1,group_code_2
+```
+
+These can also be set in `config.yaml`:
+
+```yaml
+platforms:
+  yuanbao:
+    extra:
+      dm_policy: allowlist
+      dm_allow_from: "user1,user2"
+      group_policy: open
+      group_allow_from: ""
+```
+
+## Advanced Configuration
+
+### Message Chunking
+
+Yuanbao has a maximum message size. Hermes automatically chunks large responses with Markdown-aware splitting (respects code fences, tables, and paragraph boundaries).
+
+### Connection Parameters
+
+The following connection parameters are built into the adapter with sensible defaults:
+
+| Parameter | Default Value | Description |
+|-----------|---------------|-------------|
+| WebSocket connect timeout | 15 seconds | Time to wait for WS handshake |
+| Heartbeat interval | 30 seconds | Ping frequency to keep connection alive |
+| Max reconnect attempts | 100 | Maximum number of reconnection tries |
+| Reconnect backoff | 1s → 60s (exponential) | Wait time between reconnect attempts |
+| Reply heartbeat interval | 2 seconds | RUNNING status send frequency |
+| Send timeout | 30 seconds | Timeout for outbound WS messages |
+
+:::note
+These values are currently not configurable via environment variables. They are optimized for typical Yuanbao deployments.
+:::
+
+### Verbose Logging
+
+Enable debug logging to troubleshoot connection issues:
+
+```bash
+hermes gateway run -vv
+```
+
+## Integration with Other Features
+
+### Cron Jobs
+
+Schedule tasks that run on Yuanbao:
+
+```
+/cron "0 */4 * * *" Report system health
+```
+
+Results are delivered to your home channel.
+
+### Background Tasks
+
+Run long operations without blocking the conversation:
+
+```
+/bg Analyze all files in the archive
+```
+
+### Cross-Platform Messages
+
+Send a message from CLI to Yuanbao:
+
+```bash
+hermes chat -q "Send 'Hello from CLI' to yuanbao:group:group_code"
+```
+
+## Related Documentation
+
+- [Messaging Gateway Overview](./index.md)
+- [Slash Commands Reference](/reference/slash-commands)
+- [Cron Jobs](/user-guide/features/cron)
+- [Background Sessions](/user-guide/cli#background-sessions)