feishu-messaging

# Feishu Messaging Configuration

## Quick Start

For stable, consistent message formatting in Feishu, configure:

```yaml
channels:
  feishu:
    renderMode: "card"  # Recommended for most use cases
```

This ensures all auto-replies use interactive cards with proper markdown rendering.

## Message Format Stability

### The Problem: Raw vs Card Mixing

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

This creates a poor user experience with unpredictable message appearance.

### The Solution: Explicit renderMode

Set `renderMode` explicitly instead of relying on "auto":

| Mode | Behavior | Use Case |
|------|----------|----------|
| `auto` | Detects content, uses card for code/tables | Default, but can be inconsistent |
| `raw` | Always plain text | Simple text-only responses |
| `card` | Always interactive card | **Recommended** - consistent formatting |

**Recommended configuration:**

```yaml
channels:
  feishu:
    renderMode: "card"
```

This guarantees:
- ✅ Consistent message appearance
- ✅ Proper markdown rendering (syntax highlighting, tables, links)
- ✅ No unexpected format switching
- ✅ Professional, polished look

## Auto-Reply vs Proactive Messages

### Auto-Replies (Bot responds to user messages)

Controlled by `renderMode`:
- `renderMode: "card"` → All auto-replies use card format
- `renderMode: "raw"` → All auto-replies use plain text

**Example flow:**
1. User: "Show me the code"
2. Bot auto-reply uses card format (if `renderMode: "card"`)

### Proactive Messages (Bot sends via `message` tool)

Always use plain text format via `outbound.sendText`.

**To send card format proactively:**
1. Ask user to send a message first
2. Bot replies to that message (uses `renderMode`)

**Example:**
```
User: "Remind me about the meeting"
Bot (proactive): "OK, reminder set"  # Plain text via message tool...