agent-messenger 1.14.0 → 2.0.0

package/docs/content/docs/{integrations → cli}/slackbot.mdx

@@ -150,7 +150,7 @@ agent-slackbot message get <channel> <ts>
 
 # Get thread replies
 agent-slackbot message replies <channel> <thread_ts>
-agent-slackbot message replies C0ACZKTDDC0 1234567890.123456
+agent-slackbot message replies C0ACZKTDDC0 1234567890.123456 --limit 50
 
 # Update a message (bot's own messages only)
 agent-slackbot message update <channel> <ts> <new-text>

package/docs/content/docs/{integrations → cli}/teams.mdx

@@ -39,7 +39,7 @@ This command:
 - Discovers ALL joined teams
 - Stores credentials securely in `~/.config/agent-messenger/`
 
-### ⚠️ TOKEN EXPIRY WARNING
+### TOKEN EXPIRY WARNING
 
 **Teams tokens expire in 60-90 minutes!** Unlike Slack and Discord tokens which last much longer, Microsoft Teams uses short-lived OAuth tokens.
 
@@ -312,7 +312,7 @@ fi
 agent-teams snapshot --limit 5 > /tmp/teams-context.json
 
 # 3. Send standup reminder
-agent-teams message send $STANDUP_CHANNEL "🌅 Good morning! Time for standup."
+agent-teams message send $STANDUP_CHANNEL "Good morning! Time for standup."
 ```
 
 ### Token Refresh Pattern for Long-Running Agents

package/docs/content/docs/cli/telegram.mdx

@@ -0,0 +1,107 @@
+---
+title: Telegram
+description: Complete reference for the agent-telegram CLI.
+---
+
+> **Tip**: After `npm install -g agent-messenger`, `agent-telegram` is available directly. For one-off execution without a global install you can use `npm exec --package agent-messenger agent-telegram ...`, `pnpm dlx --package agent-messenger agent-telegram ...`, `yarn dlx agent-messenger agent-telegram ...`, or `bunx --package agent-messenger agent-telegram ...`.
+
+## Requirements
+
+Telegram is different from the Slack/Discord/Teams integrations:
+
+- It uses [TDLib](https://core.telegram.org/tdlib), but this package can ship `libtdjson` through `prebuilt-tdlib`.
+- It needs a Telegram app credential (`api_id` and `api_hash`). The CLI automatically provisions these via my.telegram.org on first login. For CI/CD, set `AGENT_TELEGRAM_API_ID` / `AGENT_TELEGRAM_API_HASH` environment variables.
+- Authentication is stateful and may require multiple `auth login` calls.
+
+## Quick Start
+
+```bash
+# The CLI will automatically provision API credentials via my.telegram.org
+agent-telegram auth login
+
+# The command will then interactively ask for phone, code, password, email, etc. as needed
+
+# Inspect chats
+agent-telegram chat list
+
+# Send a message
+agent-telegram message send <chat-id-or-@username> "Hello from Telegram"
+```
+
+## Authentication
+
+### Login
+
+```bash
+# Interactive - auto-provisions API credentials
+agent-telegram auth login
+```
+
+The CLI automatically provisions API credentials via my.telegram.org. For CI/CD or custom apps, set `AGENT_TELEGRAM_API_ID` and `AGENT_TELEGRAM_API_HASH` environment variables, or pass `--api-id` and `--api-hash` flags.
+
+```bash
+agent-telegram auth login \
+  --api-id <api-id> \
+  --api-hash <api-hash> \
+  --phone +14155551234 \
+  --tdlib-path /opt/homebrew/lib/libtdjson.dylib
+```
+
+If TDLib isn't bundled and automatic lookup fails, pass `--tdlib-path` explicitly or install TDLib yourself.
+
+### Status and Account Management
+
+```bash
+# Check current auth state
+agent-telegram auth status
+
+# List stored accounts
+agent-telegram auth list
+
+# Switch current account
+agent-telegram auth use <account-id>
+
+# Log out
+agent-telegram auth logout
+
+# Remove local TDLib state for an account
+agent-telegram auth remove <account-id>
+```
+
+## Commands
+
+### Chat Commands
+
+```bash
+# List chats
+agent-telegram chat list --limit 50
+
+# Search chats
+agent-telegram chat search "ops"
+
+# Get a chat by ID, username, or exact title
+agent-telegram chat get @durov
+```
+
+### Message Commands
+
+```bash
+# List recent messages
+agent-telegram message list @durov --limit 20
+
+# Send a text message
+agent-telegram message send @durov "Hello from agent-messenger"
+```
+
+## Storage
+
+- Account metadata lives in `~/.config/agent-messenger/telegram-credentials.json`
+- TDLib databases live in `~/.config/agent-messenger/telegram/<account-id>/`
+
+## Publishing For Zero-Friction `bunx`
+
+To make `bunx --package agent-messenger agent-telegram auth login` work smoothly, the published package should:
+
+1. Keep `prebuilt-tdlib` in optionalDependencies
+2. Document `AGENT_TELEGRAM_API_ID`
+3. Document `AGENT_TELEGRAM_API_HASH`

package/docs/content/docs/cli/whatsapp.mdx

@@ -0,0 +1,163 @@
+---
+title: WhatsApp
+description: Complete reference for the agent-whatsapp CLI.
+---
+
+> **Tip**: After `npm install -g agent-messenger`, `agent-whatsapp` is available directly. For one-off execution without a global install you can use `npm exec --package agent-messenger agent-whatsapp ...`, `pnpm dlx --package agent-messenger agent-whatsapp ...`, `yarn dlx agent-messenger agent-whatsapp ...`, or `bunx --package agent-messenger agent-whatsapp ...`.
+
+## Requirements
+
+WhatsApp integration uses [Baileys](https://github.com/WhiskeySockets/Baileys), a reverse-engineered WhatsApp Web API:
+
+- Links as a **companion device** via pairing code, so your phone stays connected.
+- Each command opens a WebSocket connection on demand and disconnects when done. No persistent background process.
+- Multiple WhatsApp accounts can be linked simultaneously.
+
+## Quick Start
+
+```bash
+# Link as companion device (enter the pairing code on your phone)
+agent-whatsapp auth login --phone +1234567890
+
+# List chats
+agent-whatsapp chat list
+
+# Send a message
+agent-whatsapp message send +1234567890 "Hello from agent-whatsapp"
+```
+
+## Authentication
+
+### Pairing Code Login
+
+The CLI registers as a companion (linked) device using a numeric pairing code. Your phone session is never affected.
+
+```bash
+# Start login (displays a pairing code)
+agent-whatsapp auth login --phone +1234567890
+```
+
+The CLI outputs a pairing code. Enter it on your phone: WhatsApp > Settings > Linked Devices > Link a Device.
+
+### Account Management
+
+```bash
+# Check current auth state
+agent-whatsapp auth status
+agent-whatsapp auth status --account <id>
+
+# List linked accounts
+agent-whatsapp auth list
+
+# Switch active account
+agent-whatsapp auth use <id>
+
+# Unlink account
+agent-whatsapp auth logout
+agent-whatsapp auth logout --account <id>
+```
+
+## Commands
+
+### Chat Commands
+
+```bash
+# List chats (sorted by most recent activity)
+agent-whatsapp chat list
+agent-whatsapp chat list --limit 50
+agent-whatsapp chat list --account <id>
+
+# Search chats by name
+agent-whatsapp chat search "project"
+agent-whatsapp chat search "project" --limit 10
+agent-whatsapp chat search "project" --account <id>
+```
+
+### Message Commands
+
+```bash
+# List messages in a chat
+agent-whatsapp message list <chat> --limit 20
+agent-whatsapp message list +1234567890 --limit 50
+agent-whatsapp message list 123456789-123345@g.us --limit 10
+
+# Send a text message
+agent-whatsapp message send <chat> <text>
+agent-whatsapp message send +1234567890 "Hello!"
+agent-whatsapp message send 123456789-123345@g.us "Hello team!"
+
+# React to a message
+agent-whatsapp message react <chat> <message-id> <emoji>
+agent-whatsapp message react +1234567890 ABC123DEF456 "👍"
+agent-whatsapp message react +1234567890 ABC123DEF456 "👍" --from-me
+```
+
+The `<chat>` argument accepts:
+- Phone number: `+1234567890` (auto-resolved to JID)
+- Individual JID: `1234567890@s.whatsapp.net`
+- Group JID: `123456789-123345@g.us`
+
+The `--from-me` flag on `message react` indicates the target message was sent by you (outgoing). Without it, the reaction targets an incoming message.
+
+## Global Options
+
+| Option           | Description                                |
+| ---------------- | ------------------------------------------ |
+| `--pretty`       | Human-readable output instead of JSON      |
+| `--account <id>` | Use a specific account for this command     |
+
+## Storage
+
+- Credentials stored in `~/.config/agent-messenger/whatsapp-credentials.json`
+- Session data stored in `~/.config/agent-messenger/whatsapp/<account-id>/`
+
+## Limitations
+
+- **Connect-on-demand**: Each command opens a WebSocket connection and closes it when done. No persistent daemon.
+- **Ban risk**: WhatsApp monitors for automated behavior. Avoid high-volume messaging, rapid-fire sends, or bulk operations. Space out commands when sending multiple messages.
+- **No file uploads or downloads**
+- **No voice or video calls**
+- **No status/story support**
+
+## Troubleshooting
+
+### `agent-whatsapp: command not found`
+
+**`agent-whatsapp` is NOT the npm package name.** The npm package is `agent-messenger`.
+
+```bash
+# If installed globally
+agent-whatsapp chat list --pretty
+
+# If not installed, use --package
+npx -y --package agent-messenger agent-whatsapp chat list --pretty
+```
+
+**NEVER run `npx agent-whatsapp`** without `--package agent-messenger`. It will fail or install a wrong package.
+
+### Pairing code not working
+
+1. Make sure WhatsApp is open on your phone
+2. Go to Settings > Linked Devices > Link a Device
+3. Choose "Link with phone number instead" if you see a QR code
+4. Enter the pairing code shown in the terminal
+5. If the code expires, run `auth login --phone <number>` again for a fresh code
+
+### Connection drops
+
+WhatsApp may disconnect linked devices that are inactive for extended periods. If commands start failing:
+
+```bash
+# Check if still linked
+agent-whatsapp auth status
+
+# Re-link if needed
+agent-whatsapp auth login --phone +1234567890
+```
+
+## AI Agent Integration
+
+See [`skills/agent-whatsapp/`](https://github.com/devxoul/agent-messenger/tree/main/skills/agent-whatsapp) for:
+
+- Complete skill documentation
+- Common patterns for AI agent workflows

package/docs/content/docs/cli/whatsappbot.mdx

@@ -0,0 +1,169 @@
+---
+title: WhatsApp Bot
+description: Complete reference for the agent-whatsappbot CLI.
+---
+
+> **Tip**: `agent-whatsappbot` is a shortcut for `agent-messenger whatsappbot`.
+
+## Quick Start
+
+```bash
+# 1. Set your API credentials
+agent-whatsappbot auth set your-phone-number-id your-access-token
+
+# 2. Verify authentication
+agent-whatsappbot auth status
+
+# 3. List available message templates
+agent-whatsappbot template list --pretty
+
+# 4. Send a text message (recipient must have messaged you within 24h)
+agent-whatsappbot message send 15551234567 "Hello from the CLI!"
+```
+
+## Key Concepts
+
+WhatsApp Business Cloud API works differently from the user-mode WhatsApp integration:
+
+| Concept              | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| **Send-only**        | Cannot list or read received messages. Inbound messages require webhooks.    |
+| **Template messages** | Required outside the 24-hour customer service window. Must be pre-approved. |
+| **Phone Number ID**  | Your WhatsApp Business phone number's unique identifier (not the number).   |
+| **Access Token**     | Token from Meta Business Manager with `whatsapp_business_messaging` permission. |
+| **Rate limits**      | Tier 0-3: 80 msg/s. Tier 4: 1,000 msg/s. Based on business verification.   |
+
+## Authentication
+
+### API Credential Setup
+
+agent-whatsappbot uses Phone Number ID + Access Token pairs from Meta Business Manager:
+
+```bash
+# Set credentials (validates against WhatsApp Cloud API before saving)
+agent-whatsappbot auth set <phone-number-id> <access-token>
+
+# Check auth status
+agent-whatsappbot auth status
+agent-whatsappbot auth status --account <account-id>
+
+# Clear stored credentials
+agent-whatsappbot auth clear
+```
+
+### How to Get API Credentials
+
+1. Go to [Meta Business Manager](https://business.facebook.com/)
+2. Navigate to your WhatsApp Business Account
+3. Open **WhatsApp Manager > Phone Numbers** to find your **Phone Number ID**
+4. Go to **Business Settings > System Users** to create a system user and generate an **Access Token** with `whatsapp_business_messaging` permission
+5. Run `agent-whatsappbot auth set <phone-number-id> <access-token>`
+
+### Multi-Account Management
+
+```bash
+# List stored accounts
+agent-whatsappbot auth list
+
+# Switch active account
+agent-whatsappbot auth use <account-id>
+
+# Remove a stored account
+agent-whatsappbot auth remove <account-id>
+```
+
+## Commands
+
+### Message Commands
+
+```bash
+# Send a text message
+agent-whatsappbot message send <to> <text>
+agent-whatsappbot message send 15551234567 "Your order has shipped!"
+
+# Send a template message
+agent-whatsappbot message send-template <to> <template-name>
+agent-whatsappbot message send-template 15551234567 order_confirmation \
+  --language en_US \
+  --components '[{"type":"body","parameters":[{"type":"text","text":"Alice"},{"type":"text","text":"ORD-9876"}]}]'
+
+# Send a reaction to a message
+agent-whatsappbot message send-reaction <to> <message-id> <emoji>
+agent-whatsappbot message send-reaction 15551234567 wamid.abc123 "👍"
+
+# Send an image
+agent-whatsappbot message send-image <to> <url>
+agent-whatsappbot message send-image 15551234567 "https://example.com/photo.jpg" --caption "Product photo"
+
+# Send a document
+agent-whatsappbot message send-document <to> <url>
+agent-whatsappbot message send-document 15551234567 "https://example.com/invoice.pdf" \
+  --filename "invoice.pdf" --caption "Your invoice"
+```
+
+### Template Commands
+
+```bash
+# List message templates
+agent-whatsappbot template list
+agent-whatsappbot template list --limit 20
+
+# Get template details
+agent-whatsappbot template get <template-name>
+agent-whatsappbot template get order_confirmation
+```
+
+## Global Options
+
+| Option           | Description                                |
+| ---------------- | ------------------------------------------ |
+| `--pretty`       | Human-readable output instead of JSON      |
+| `--account <id>` | Use a specific account for this command     |
+
+## Storage
+
+Credentials stored in `~/.config/agent-messenger/whatsappbot-credentials.json` (0600 permissions).
+
+## Limitations
+
+- **Cannot list or read received messages** -- WhatsApp Cloud API delivers inbound messages via webhooks only. This CLI is send-only.
+- **Template messages required outside 24h window** -- Free-form text only works within 24 hours of the customer's last message.
+- **Business verification required for higher tiers** -- Unverified businesses are limited in daily messaging volume.
+- **No group chat support** -- WhatsApp Cloud API does not support group messaging.
+- **No real-time events / WebSocket connection** -- Inbound messages require a separate webhook server.
+- **No message editing or deletion**
+- **No file upload from local disk** -- Images and documents must be provided as URLs.
+- **No voice or video calls**
+- **Phone number must be registered with WhatsApp Business** -- Personal WhatsApp numbers won't work.
+
+## Troubleshooting
+
+### `agent-whatsappbot: command not found`
+
+**`agent-whatsappbot` is NOT the npm package name.** The npm package is `agent-messenger`.
+
+```bash
+# If installed globally
+agent-whatsappbot message send 15551234567 "Hello"
+
+# If not installed, use npx
+npx -y agent-messenger whatsappbot message send 15551234567 "Hello"
+```
+
+### Template messages not sending
+
+- Verify the template exists: `agent-whatsappbot template get <name>`
+- Check the template status is `APPROVED` (not `PENDING` or `REJECTED`)
+- Ensure the `--language` matches the template's language code exactly
+- Verify `--components` JSON matches the template's parameter structure
+
+### Rate limiting
+
+WhatsApp enforces rate limits based on your business tier. The CLI automatically retries on rate limit (429) responses. For bulk operations, add delays between requests.
+
+## AI Agent Integration
+
+See [`skills/agent-whatsappbot/`](https://github.com/devxoul/agent-messenger/tree/main/skills/agent-whatsappbot) for:
+
+- Complete skill documentation
+- Common patterns for AI agent workflows

package/docs/content/docs/index.mdx

@@ -1,10 +1,10 @@
 ---
 title: What is Agent Messenger?
-description: Give your AI agent the power to read and send messages across Slack, Discord, Teams and more
+description: Give your AI agent the power to read and send messages across Slack, Discord, Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, Channel Talk, and more
 icon: Info
 ---
 
-Agent Messenger is a unified, agent-friendly CLI for messaging platforms. Zero-config credential extraction from your desktop apps—no OAuth flows, no API keys, no admin approval needed. Works out of the box.
+Agent Messenger is a unified, agent-friendly CLI for messaging platforms. Zero-config credential extraction from your desktop apps—no OAuth flows, no API keys, no admin approval needed. Works out of the box. Supports Slack, Discord, Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk (beta).
 
 ## Why Agent Messenger?
 
@@ -12,14 +12,14 @@ Messaging platforms only offer Bot tokens for API access—your AI agent can nev
 
 - **Act as yourself, not a bot** — Extracted user tokens let your agent operate on your behalf
 - **No API keys needed** — Automatically extracts credentials from your installed desktop apps
-- **One interface, multiple platforms** — Learn once, use everywhere (Slack, Discord, Teams)
+- **One interface, multiple platforms** — Learn once, use everywhere (Slack, Discord, Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, Channel Talk)
 - **AI-agent friendly** — JSON output by default, perfect for LLM tool use
 - **Human friendly too** — Add `--pretty` for readable output
 - **Token efficient** — CLI, not MCP. Load only what you need
 
 ## How It Works
 
-Agent Messenger reads authentication tokens directly from your installed desktop apps (Slack, Discord, Teams). These apps store session tokens locally, and Agent Messenger safely extracts them.
+Agent Messenger reads authentication tokens directly from your installed desktop apps (Slack, Discord, Teams, KakaoTalk, Channel Talk). Telegram uses TDLib with auto-provisioned API credentials. WhatsApp authenticates via pairing code. KakaoTalk supports both credential extraction and sub-device login. These apps store session tokens locally, and Agent Messenger safely extracts them.
 
 ```bash
 # Extract credentials from Slack desktop app
@@ -36,11 +36,11 @@ No app creation. No admin approval. No waiting.
 | Feature             | Description                                                                                                                       |
 | ------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | **Auto-extraction** | Pulls tokens from desktop apps automatically                                                                                      |
-| **Multi-platform**  | Slack, Discord, and Microsoft Teams                                                                                               |
+| **Multi-platform**  | Slack, Discord, Microsoft Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk (beta)                                                                          |
 | **Multi-workspace** | Switch between workspaces/servers easily                                                                                          |
 | **JSON output**     | Machine-readable by default, `--pretty` for humans                                                                                |
 | **Comprehensive**   | Messages, channels, users, reactions, files                                                                                       |
-| **Bot support**     | [`agent-slackbot`](/docs/integrations/slackbot) and [`agent-discordbot`](/docs/integrations/discordbot) for server-side and CI/CD |
+| **Bot support**     | [`agent-slackbot`](/docs/cli/slackbot), [`agent-discordbot`](/docs/cli/discordbot), and [`agent-channeltalkbot`](/docs/cli/channeltalkbot) for server-side and CI/CD |
 
 ## Why Not MCP?
 
@@ -81,7 +81,7 @@ OAuth is better when you need:
 - **Multi-user applications** - Many users authenticating separately
 - **Granular permissions** - Fine-tuned access control
 
-For these use cases, Agent Messenger also supports bot tokens via [`agent-slackbot`](/docs/integrations/slackbot) and [`agent-discordbot`](/docs/integrations/discordbot).
+For these use cases, Agent Messenger also supports bot tokens via [`agent-slackbot`](/docs/cli/slackbot), [`agent-discordbot`](/docs/cli/discordbot), and [`agent-channeltalkbot`](/docs/cli/channeltalkbot).
 
 ## Design Principles
 
@@ -95,7 +95,7 @@ Default output is JSON for machines. Add `--pretty` for humans. Both are first-c
 
 ### Unified Interface
 
-Learn once, use everywhere. The same commands work across Slack, Discord, and Teams.
+Learn once, use everywhere. The same commands work across Slack, Discord, Teams, Telegram, WhatsApp, LINE, Instagram, KakaoTalk, and Channel Talk.
 
 ### Fail Fast, Fail Clear
 
@@ -108,11 +108,19 @@ Tokens stay on your machine. Nothing is sent to external servers. Your credentia
 ## Next Steps
 
 - [Quick Start](/docs/quick-start) - Get running in 30 seconds
-- [Slack](/docs/integrations/slack) - Full Slack command reference
-- [Slack Bot](/docs/integrations/slackbot) - Bot token integration for server-side and CI/CD
-- [Discord](/docs/integrations/discord) - Full Discord command reference
-- [Discord Bot](/docs/integrations/discordbot) - Bot token integration for server-side and CI/CD
-- [Teams](/docs/integrations/teams) - Full Teams command reference
+- [Slack](/docs/cli/slack) - Full Slack command reference
+- [Slack Bot](/docs/cli/slackbot) - Bot token integration for server-side and CI/CD
+- [Discord](/docs/cli/discord) - Full Discord command reference
+- [Discord Bot](/docs/cli/discordbot) - Bot token integration for server-side and CI/CD
+- [Teams](/docs/cli/teams) - Full Teams command reference
+- [Telegram](/docs/cli/telegram) - TDLib setup and Telegram command reference
+- [WhatsApp](/docs/cli/whatsapp) - Full WhatsApp command reference
+- [WhatsApp Bot](/docs/cli/whatsappbot) - Cloud API integration for WhatsApp Business
+- [LINE](/docs/cli/line) - Full LINE command reference
+- [Instagram](/docs/cli/instagram) - Instagram DM integration via private mobile API
+- [KakaoTalk](/docs/cli/kakaotalk) - Full KakaoTalk command reference
+- [Channel Talk](/docs/cli/channeltalk) - Full Channel Talk command reference (beta)
+- [Channel Talk Bot](/docs/cli/channeltalkbot) - Bot API integration for Channel Talk (beta)
 
 ## Inspiration
 

package/docs/content/docs/meta.json

@@ -1,3 +1,11 @@
 {
-  "pages": ["index", "quick-start", "integrations", "agent-skills"]
+  "pages": [
+    "index",
+    "quick-start",
+    "agent-skills",
+    "tui",
+    "---",
+    "cli",
+    "sdk"
+  ]
 }

package/docs/content/docs/quick-start.mdx

@@ -23,13 +23,21 @@ yarn global add agent-messenger
 bun add -g agent-messenger
 ```
 
-This installs five CLI tools:
+This installs these CLI tools:
 
 - `agent-slack` — Slack CLI (user token, zero-config)
 - `agent-slackbot` — Slack Bot CLI (bot token, for server-side/CI/CD)
 - `agent-discord` — Discord CLI (user token, zero-config)
 - `agent-discordbot` — Discord Bot CLI (bot token, for server-side/CI/CD)
 - `agent-teams` — Microsoft Teams CLI
+- `agent-telegram` — Telegram CLI (user account via TDLib)
+- `agent-whatsapp` — WhatsApp CLI (user account via Baileys, pairing code auth)
+- `agent-whatsappbot` — WhatsApp Bot CLI (Cloud API, for server-side/CI/CD)
+- `agent-line` — LINE CLI (QR code login, Thrift protocol)
+- `agent-instagram` — Instagram DM CLI (user account via private mobile API)
+- `agent-kakaotalk` — KakaoTalk CLI (sub-device login, LOCO protocol)
+- `agent-channeltalk` — Channel Talk CLI (beta, zero-config, extracted cookies)
+- `agent-channeltalkbot` — Channel Talk Bot CLI (beta, API credentials, for server-side/CI/CD)
 
 ## Extract Credentials
 
@@ -44,6 +52,15 @@ agent-discord auth extract
 
 # For Teams
 agent-teams auth extract
+
+# For Telegram — interactive login with auto API credential provisioning
+agent-telegram auth login
+
+# For KakaoTalk — login as sub-device (desktop stays running)
+agent-kakaotalk auth login
+
+# For Channel Talk (beta) — auto-extracted from desktop app
+agent-channeltalk auth extract
 ```
 
 That's it. No OAuth flows. No API tokens. No configuration files.
@@ -100,9 +117,15 @@ agent-slack workspace current
 
 ## Next Steps
 
-- [Slack Reference](/docs/integrations/slack) - Full command reference
-- [Slack Bot Reference](/docs/integrations/slackbot) - Bot token for server-side/CI/CD
-- [Discord Reference](/docs/integrations/discord) - Full command reference
-- [Discord Bot Reference](/docs/integrations/discordbot) - Bot token for server-side/CI/CD
-- [Teams Reference](/docs/integrations/teams) - Full command reference
+- [Slack Reference](/docs/cli/slack) - Full command reference
+- [Slack Bot Reference](/docs/cli/slackbot) - Bot token for server-side/CI/CD
+- [Discord Reference](/docs/cli/discord) - Full command reference
+- [Discord Bot Reference](/docs/cli/discordbot) - Bot token for server-side/CI/CD
+- [Teams Reference](/docs/cli/teams) - Full command reference
+- [Telegram Reference](/docs/cli/telegram) - TDLib setup and command reference
+- [WhatsApp Reference](/docs/cli/whatsapp) - Full command reference
+- [WhatsApp Bot Reference](/docs/cli/whatsappbot) - Cloud API for WhatsApp Business
+- [KakaoTalk Reference](/docs/cli/kakaotalk) - Full command reference
+- [Channel Talk Reference](/docs/cli/channeltalk) - Full command reference (beta)
+- [Channel Talk Bot Reference](/docs/cli/channeltalkbot) - Bot API for Channel Talk (beta)
 - [Agent Skills](/docs/agent-skills) - Integrate with AI coding agents