feishu-chat

# Feishu Group Chat Guide

## Quick Start: Configure renderMode

**⚠️ IMPORTANT: Set renderMode explicitly for stable message formatting**

```yaml
# Recommended configuration
channels:
  feishu:
    renderMode: "card"  # Always use card format
```

**Why?** The default "auto" mode causes unpredictable format switching (raw vs card), creating poor user experience.

**Configuration:**
```bash
openclaw config set channels.feishu.renderMode "card"
openclaw gateway restart
```

**Verify:**
```bash
openclaw config get channels.feishu.renderMode
```

---

## Prerequisites

1. **In a Feishu group** - OpenClaw connected to Feishu
2. **Configure renderMode** - Set to "card" for consistent formatting
3. **Know member IDs**:
   - Human: `open_id` (ou_xxx format)
   - Bot: `App ID` (cli_xxx format)

---

## 0. Message Format Stability

### The Problem: Raw vs Card Mixing

Without proper `renderMode` configuration, messages can inconsistently appear as:
- **Raw text**: Plain markdown source, no formatting
- **Card format**: Rendered markdown with syntax highlighting, tables, links

### The Solution: Explicit renderMode

| Mode | Behavior | Use Case |
|------|----------|----------|
| `auto` | Detects content, uses card for code/tables | ❌ **Avoid** - unpredictable |
| `raw` | Always plain text | Simple text-only responses |
| `card` | Always interactive card | ✅ **Recommended** - consistent |

**Recommended:** `renderMode: "card"` for all production use.

---

## 1. Message Sending

### ⚠️ CRITICAL: Only Use ONE Method

**DO NOT use both direct reply and message tool for the same content!** This will send two messages.

Choose ONE:
- Plain text → message tool only
- Markdown → direct reply only

---

### Two Methods

| Method | Tool | Render Mode | Use Case |
|--------|------|-------------|----------|
| **message tool** | `message` | Raw (plain text) | Plain text, @ mentions |
| **Direct reply** | Session reply | Card (with Markdown) | Markdown formatted messages |

### Raw Mod...