Merge pull request #2119 from BeaconCat/fix/update-assets

docs: add macOS Gatekeeper bypass guide to WebUI Launcher section docs: update WeCom channel docs and README provider/channel tables docs: add Malay README and docs, add v0.2.4 news to all languages docs(wecom): add fr/ja/pt-br/vi translations for unified WeCom channel
2026-06-12 18:08:54 +00:00 · 2026-03-28 19:02:43 +08:00
parent 62d40a02d4 465ca0361c
commit 30155c1c59
37 changed files with 1494 additions and 1575 deletions
@@ -18,7 +18,7 @@
    <a href="https://discord.gg/V4sAZ9XWpN"><img src="https://img.shields.io/badge/Discord-Community-4c60eb?style=flat&logo=discord&logoColor=white" alt="Discord"></a>
  </p>

-[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | **Français** | [Italiano](README.it.md) | [Bahasa Indonesia](README.id.md) | [English](README.md)
+[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | **Français** | [Italiano](README.it.md) | [Bahasa Indonesia](README.id.md) | [Malay](README.my.md) | [English](README.md)

 </div>

@@ -57,17 +57,19 @@

 ## 📢 Actualités

+2026-03-25 🚀 **v0.2.4 publiée !** Refonte de l'architecture Agent (SubTurn, Hooks, Steering, EventBus), intégration WeChat/WeCom, renforcement de la sécurité (.security.yml, filtrage des données sensibles), nouveaux providers (AWS Bedrock, Azure, Xiaomi MiMo), et 35 corrections de bugs. PicoClaw a atteint **26K Stars** !
+
 2026-03-17 🚀 **v0.2.3 publiée !** Interface system tray (Windows & Linux), requête de statut des sous-agents (`spawn_status`), rechargement à chaud expérimental du Gateway, sécurisation Cron, et 2 correctifs de sécurité. PicoClaw a atteint **25K Stars** !

-2026-03-09 🎉 **v0.2.1 — La plus grande mise à jour à ce jour !** Support du protocole MCP, 4 nouveaux channels (Matrix/IRC/WeCom/Discord Proxy), 3 nouveaux providers (Kimi/Minimax/Avian), pipeline vision, stockage mémoire JSONL, routage de modèles.
+2026-03-09 🎉 **v0.2.1 — Plus grande mise à jour à ce jour !** Support du protocole MCP, 4 nouveaux channels (Matrix/IRC/WeCom/Discord Proxy), 3 nouveaux providers (Kimi/Minimax/Avian), pipeline vision, stockage mémoire JSONL, routage de modèles.

 2026-02-28 📦 **v0.2.0** publiée avec support Docker Compose et Web UI Launcher.

-2026-02-26 🎉 PicoClaw atteint **20K Stars** en seulement 17 jours ! L'orchestration automatique des channels et les interfaces de capacités sont disponibles.
-
 <details>
 <summary>Actualités précédentes...</summary>

+2026-02-26 🎉 PicoClaw atteint **20K Stars** en seulement 17 jours ! L'orchestration automatique des channels et les interfaces de capacités sont disponibles.
+
 2026-02-16 🎉 PicoClaw dépasse 12K Stars en une semaine ! Rôles de mainteneurs communautaires et [Roadmap](ROADMAP.md) officiellement lancés.

 2026-02-13 🎉 PicoClaw dépasse 5000 Stars en 4 jours ! Roadmap du projet et groupes de développeurs en cours.
@@ -257,6 +259,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — Avertissement de sécurité au premier lancement</b></summary>
+
+macOS peut bloquer `picoclaw-launcher` au premier lancement car il est téléchargé depuis Internet et n'est pas notarisé via le Mac App Store.
+
+**Étape 1 :** Double-cliquez sur `picoclaw-launcher`. Un avertissement de sécurité s'affiche :
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Avertissement macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" n'a pas pu être ouvert — Apple n'a pas pu vérifier que "picoclaw-launcher" ne contient pas de logiciel malveillant susceptible de nuire à votre Mac ou de compromettre votre confidentialité.*
+
+**Étape 2 :** Ouvrez **Réglages Système** → **Confidentialité et sécurité** → faites défiler jusqu'à la section **Sécurité** → cliquez sur **Ouvrir quand même** → confirmez en cliquant sur **Ouvrir quand même** dans la boîte de dialogue.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Confidentialité et sécurité — Ouvrir quand même" width="600">
+</p>
+
+Après cette étape unique, `picoclaw-launcher` s'ouvrira normalement lors des lancements suivants.
+
+</details>
+
 ### 💻 TUI Launcher (Recommandé pour les environnements sans interface / SSH)

 Le TUI (Terminal UI) Launcher fournit une interface terminal complète pour la configuration et la gestion. Idéal pour les serveurs, Raspberry Pi et autres environnements sans interface graphique.
@@ -371,6 +396,7 @@ PicoClaw supporte plus de 30 providers LLM via la configuration `model_list`. Ut
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Requise | Modèles hébergés NVIDIA |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Requise | Inférence rapide |
 | [Novita AI](https://novita.ai/) | `novita/` | Requise | Divers modèles open |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Requise | Modèles MiMo |
 | [Ollama](https://ollama.com/) | `ollama/` | Non requise | Modèles locaux, auto-hébergé |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Non requise | Déploiement local, compatible OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Variable | Proxy pour 100+ providers |
@@ -427,9 +453,7 @@ Parlez à votre PicoClaw via plus de 17 plateformes de messagerie :
 | **DingTalk** | Moyen (identifiants client) | Stream | [Guide](docs/channels/dingtalk/README.fr.md) |
 | **Feishu / Lark** | Moyen (App ID + Secret) | WebSocket/SDK | [Guide](docs/channels/feishu/README.fr.md) |
 | **LINE** | Moyen (identifiants + webhook) | Webhook | [Guide](docs/channels/line/README.fr.md) |
-| **WeCom Bot** | Moyen (URL webhook) | Webhook | [Guide](docs/channels/wecom/wecom_bot/README.fr.md) |
-| **WeCom App** | Moyen (identifiants corp) | Webhook | [Guide](docs/channels/wecom/wecom_app/README.fr.md) |
-| **WeCom AI Bot** | Moyen (token + clé AES) | WebSocket / Webhook | [Guide](docs/channels/wecom/wecom_aibot/README.fr.md) |
+| **WeCom** | Facile (QR login ou manuel) | WebSocket | [Guide](docs/channels/wecom/README.md) |
 | **IRC** | Moyen (serveur + pseudo) | Protocole IRC | [Guide](docs/fr/chat-apps.md#irc) |
 | **OneBot** | Moyen (URL WebSocket) | OneBot v11 | [Guide](docs/channels/onebot/README.fr.md) |
 | **MaixCam** | Facile (activer) | Socket TCP | [Guide](docs/channels/maixcam/README.fr.md) |
@@ -18,7 +18,7 @@
    <a href="https://discord.gg/V4sAZ9XWpN"><img src="https://img.shields.io/badge/Discord-Community-4c60eb?style=flat&logo=discord&logoColor=white" alt="Discord"></a>
  </p>

-[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | [Français](README.fr.md) | [Italiano](README.it.md) | [English](README.md) | **Bahasa Indonesia**
+[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | [Français](README.fr.md) | [Italiano](README.it.md) | [Malay](README.my.md) | [English](README.md) | **Bahasa Indonesia**

 </div>

@@ -56,17 +56,19 @@

 ## 📢 Berita

+2026-03-25 🚀 **v0.2.4 Dirilis!** Perombakan arsitektur Agent (SubTurn, Hooks, Steering, EventBus), integrasi WeChat/WeCom, penguatan keamanan (.security.yml, penyaringan data sensitif), provider baru (AWS Bedrock, Azure, Xiaomi MiMo), dan 35 perbaikan bug. PicoClaw telah mencapai **26K Stars**!
+
 2026-03-17 🚀 **v0.2.3 Dirilis!** UI system tray (Windows & Linux), pelacakan status sub-agent (`spawn_status`), eksperimental Gateway hot-reload, gerbang keamanan Cron, dan 2 perbaikan keamanan. PicoClaw telah mencapai **25K Stars**!

-2026-03-09 🎉 **v0.2.1 — Update terbesar sejauh ini!** Dukungan protokol MCP, 4 channel baru (Matrix/IRC/WeCom/Discord Proxy), 3 provider baru (Kimi/Minimax/Avian), pipeline vision, penyimpanan memori JSONL, routing model.
+2026-03-09 🎉 **v0.2.1 — Pembaruan terbesar sejauh ini!** Dukungan protokol MCP, 4 channel baru (Matrix/IRC/WeCom/Discord Proxy), 3 provider baru (Kimi/Minimax/Avian), pipeline visi, penyimpanan memori JSONL, perutean model.

 2026-02-28 📦 **v0.2.0** dirilis dengan dukungan Docker Compose dan Web UI Launcher.

-2026-02-26 🎉 PicoClaw mencapai **20K Stars** hanya dalam 17 hari! Orkestrasi channel otomatis dan antarmuka kapabilitas kini aktif.
-
 <details>
 <summary>Berita sebelumnya...</summary>

+2026-02-26 🎉 PicoClaw mencapai **20K Stars** hanya dalam 17 hari! Orkestrasi channel otomatis dan antarmuka kapabilitas kini aktif.
+
 2026-02-16 🎉 PicoClaw menembus 12K Stars dalam satu minggu! Peran maintainer komunitas dan [Roadmap](ROADMAP.md) resmi diluncurkan.

 2026-02-13 🎉 PicoClaw menembus 5000 Stars dalam 4 hari! Roadmap proyek dan grup pengembang sedang dalam proses.
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — Peringatan Keamanan saat Pertama Kali Diluncurkan</b></summary>
+
+macOS mungkin memblokir `picoclaw-launcher` saat pertama kali diluncurkan karena diunduh dari internet dan tidak dinotarisasi melalui Mac App Store.
+
+**Langkah 1:** Klik dua kali `picoclaw-launcher`. Anda akan melihat peringatan keamanan:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Peringatan macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" Tidak Dapat Dibuka — Apple tidak dapat memverifikasi bahwa "picoclaw-launcher" bebas dari malware yang dapat membahayakan Mac Anda atau mengancam privasi Anda.*
+
+**Langkah 2:** Buka **Pengaturan Sistem** → **Privasi & Keamanan** → gulir ke bawah ke bagian **Keamanan** → klik **Tetap Buka** → konfirmasi dengan mengklik **Tetap Buka** pada dialog.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Privasi & Keamanan — Tetap Buka" width="600">
+</p>
+
+Setelah langkah satu kali ini, `picoclaw-launcher` akan terbuka secara normal pada peluncuran berikutnya.
+
+</details>
+
 ### 💻 TUI Launcher (Direkomendasikan untuk Headless / SSH)

 TUI (Terminal UI) Launcher menyediakan antarmuka terminal lengkap untuk konfigurasi dan manajemen. Ideal untuk server, Raspberry Pi, dan lingkungan headless lainnya.
@@ -367,6 +392,7 @@ PicoClaw mendukung 30+ provider LLM melalui konfigurasi `model_list`. Gunakan fo
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Diperlukan | Model yang di-host NVIDIA |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Diperlukan | Inferensi cepat |
 | [Novita AI](https://novita.ai/) | `novita/` | Diperlukan | Berbagai model open |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Diperlukan | Model MiMo |
 | [Ollama](https://ollama.com/) | `ollama/` | Tidak perlu | Model lokal, self-hosted |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Tidak perlu | Deploy lokal, kompatibel OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Bervariasi | Proxy untuk 100+ provider |
@@ -423,9 +449,7 @@ Bicara dengan PicoClaw Anda melalui 17+ platform pesan:
 | **DingTalk** | Sedang (client credentials) | Stream | [Panduan](docs/channels/dingtalk/README.md) |
 | **Feishu / Lark** | Sedang (App ID + Secret) | WebSocket/SDK | [Panduan](docs/channels/feishu/README.md) |
 | **LINE** | Sedang (credentials + webhook) | Webhook | [Panduan](docs/channels/line/README.md) |
-| **WeCom Bot** | Sedang (webhook URL) | Webhook | [Panduan](docs/channels/wecom/wecom_bot/README.md) |
-| **WeCom App** | Sedang (corp credentials) | Webhook | [Panduan](docs/channels/wecom/wecom_app/README.md) |
-| **WeCom AI Bot** | Sedang (token + AES key) | WebSocket / Webhook | [Panduan](docs/channels/wecom/wecom_aibot/README.md) |
+| **WeCom** | Mudah (login QR atau manual) | WebSocket | [Panduan](docs/channels/wecom/README.md) |
 | **IRC** | Sedang (server + nick) | IRC protocol | [Panduan](docs/chat-apps.md#irc) |
 | **OneBot** | Sedang (WebSocket URL) | OneBot v11 | [Panduan](docs/channels/onebot/README.md) |
 | **MaixCam** | Mudah (aktifkan) | TCP socket | [Panduan](docs/channels/maixcam/README.md) |
@@ -56,17 +56,19 @@

 ## 📢 Novità

+2026-03-25 🚀 **v0.2.4 rilasciata!** Revisione dell'architettura Agent (SubTurn, Hooks, Steering, EventBus), integrazione WeChat/WeCom, rafforzamento della sicurezza (.security.yml, filtraggio dati sensibili), nuovi provider (AWS Bedrock, Azure, Xiaomi MiMo) e 35 correzioni di bug. PicoClaw raggiunge **26K Stars**!
+
 2026-03-17 🚀 **v0.2.3 rilasciata!** Interfaccia system tray (Windows & Linux), query sullo stato dei sub-agent (`spawn_status`), hot-reload sperimentale del Gateway, gate di sicurezza per Cron e 2 correzioni di sicurezza. PicoClaw raggiunge **25K Stars**!

-2026-03-09 🎉 **v0.2.1 — Il più grande aggiornamento di sempre!** Supporto al protocollo MCP, 4 nuovi canali (Matrix/IRC/WeCom/Discord Proxy), 3 nuovi provider (Kimi/Minimax/Avian), pipeline di visione, store di memoria JSONL e routing dei modelli.
+2026-03-09 🎉 **v0.2.1 — Il più grande aggiornamento di sempre!** Supporto al protocollo MCP, 4 nuovi canali (Matrix/IRC/WeCom/Discord Proxy), 3 nuovi provider (Kimi/Minimax/Avian), pipeline visiva, archivio memoria JSONL, routing dei modelli.

 2026-02-28 📦 **v0.2.0** rilasciata con supporto Docker Compose e Web UI Launcher.

-2026-02-26 🎉 PicoClaw raggiunge **20K stelle** in soli 17 giorni! Orchestrazione automatica dei canali e interfacce di capacità sono attive.
-
 <details>
 <summary>Notizie precedenti...</summary>

+2026-02-26 🎉 PicoClaw raggiunge **20K stelle** in soli 17 giorni! Orchestrazione automatica dei canali e interfacce di capacità sono attive.
+
 2026-02-16 🎉 PicoClaw supera 12K stelle in una settimana! Ruoli di maintainer della community e [Roadmap](ROADMAP.md) pubblicati ufficialmente.

 2026-02-13 🎉 PicoClaw supera 5000 stelle in 4 giorni! Roadmap del progetto e gruppi sviluppatori in fase di avvio.
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — Avviso di sicurezza al primo avvio</b></summary>
+
+macOS potrebbe bloccare `picoclaw-launcher` al primo avvio perché è stato scaricato da internet e non è notarizzato tramite il Mac App Store.
+
+**Passo 1:** Fai doppio clic su `picoclaw-launcher`. Verrà visualizzato un avviso di sicurezza:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Avviso macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" Non Aperto — Apple non è riuscita a verificare che "picoclaw-launcher" sia privo di malware che potrebbe danneggiare il Mac o compromettere la privacy.*
+
+**Passo 2:** Apri **Impostazioni di Sistema** → **Privacy e sicurezza** → scorri fino alla sezione **Sicurezza** → clicca su **Apri comunque** → conferma cliccando su **Apri comunque** nella finestra di dialogo.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Privacy e sicurezza — Apri comunque" width="600">
+</p>
+
+Dopo questo passaggio una tantum, `picoclaw-launcher` si aprirà normalmente ai lanci successivi.
+
+</details>
+
 ### 💻 TUI Launcher (Consigliato per Headless / SSH)

 Il TUI (Terminal UI) Launcher fornisce un'interfaccia terminale completa per la configurazione e la gestione. Ideale per server, Raspberry Pi e altri ambienti headless.
@@ -367,6 +392,7 @@ PicoClaw supporta 30+ provider LLM tramite la configurazione `model_list`. Usa i
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Richiesta | Modelli ospitati NVIDIA |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Richiesta | Inferenza veloce |
 | [Novita AI](https://novita.ai/) | `novita/` | Richiesta | Vari modelli open |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Richiesta | Modelli MiMo |
 | [Ollama](https://ollama.com/) | `ollama/` | Non necessaria | Modelli locali, self-hosted |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Non necessaria | Deploy locale, compatibile OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Variabile | Proxy per 100+ provider |
@@ -423,9 +449,7 @@ Parla con il tuo PicoClaw attraverso 17+ piattaforme di messaggistica:
 | **DingTalk** | Medio (credenziali client) | Stream | [Guida](docs/channels/dingtalk/README.md) |
 | **Feishu / Lark** | Medio (App ID + Secret) | WebSocket/SDK | [Guida](docs/channels/feishu/README.md) |
 | **LINE** | Medio (credenziali + webhook) | Webhook | [Guida](docs/channels/line/README.md) |
-| **WeCom Bot** | Medio (webhook URL) | Webhook | [Guida](docs/channels/wecom/wecom_bot/README.md) |
-| **WeCom App** | Medio (credenziali aziendali) | Webhook | [Guida](docs/channels/wecom/wecom_app/README.md) |
-| **WeCom AI Bot** | Medio (token + AES key) | WebSocket / Webhook | [Guida](docs/channels/wecom/wecom_aibot/README.md) |
+| **WeCom** | Facile (login QR o manuale) | WebSocket | [Guida](docs/channels/wecom/README.md) |
 | **IRC** | Medio (server + nick) | Protocollo IRC | [Guida](docs/chat-apps.md#irc) |
 | **OneBot** | Medio (WebSocket URL) | OneBot v11 | [Guida](docs/channels/onebot/README.md) |
 | **MaixCam** | Facile (abilita) | TCP socket | [Guida](docs/channels/maixcam/README.md) |
@@ -56,17 +56,19 @@

 ## 📢 ニュース

+2026-03-25 🚀 **v0.2.4 リリース！** Agent アーキテクチャ全面刷新（SubTurn、Hooks、Steering、EventBus）、WeChat/WeCom 統合、セキュリティ強化（.security.yml、機密データフィルタリング）、新プロバイダー（AWS Bedrock、Azure、Xiaomi MiMo）、35 件のバグ修正。PicoClaw **26K ⭐** 達成！
+
 2026-03-17 🚀 **v0.2.3 リリース！** システムトレイ UI（Windows & Linux）、サブエージェントステータス追跡（`spawn_status`）、実験的 Gateway ホットリロード、cron セキュリティゲート、セキュリティ修正 2 件。PicoClaw **25K ⭐** 達成！

-2026-03-09 🎉 **v0.2.1 — 史上最大のアップデート！** MCP プロトコル対応、4 つの新 Channel（Matrix/IRC/WeCom/Discord Proxy）、3 つの新 Provider（Kimi/Minimax/Avian）、ビジョンパイプライン、JSONL メモリストア、モデルルーティング。
+2026-03-09 🎉 **v0.2.1 — 最大のアップデート！** MCP プロトコルサポート、4 つの新チャンネル (Matrix/IRC/WeCom/Discord Proxy)、3 つの新プロバイダー (Kimi/Minimax/Avian)、ビジョンパイプライン、JSONL メモリストア、モデルルーティング。

-2026-02-28 📦 **v0.2.0** リリース — Docker Compose 対応と Web UI Launcher。
-
-2026-02-26 🎉 PicoClaw がわずか 17 日で **20K スター** 達成！Channel 自動オーケストレーションとケイパビリティインターフェースが実装されました。
+2026-02-28 📦 **v0.2.0** リリース — Docker Compose と Web UI Launcher サポート。

 <details>
 <summary>過去のニュース...</summary>

+2026-02-26 🎉 PicoClaw がわずか 17 日で **20K スター** 達成！Channel 自動オーケストレーションとケイパビリティインターフェースが実装されました。
+
 2026-02-16 🎉 PicoClaw が 1 週間で 12K スター達成！コミュニティメンテナーの役割と[ロードマップ](ROADMAP.md)が正式に公開されました。

 2026-02-13 🎉 PicoClaw が 4 日間で 5000 スター達成！プロジェクトロードマップと開発者グループの準備が進行中。
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — 初回起動時のセキュリティ警告</b></summary>
+
+`picoclaw-launcher` はインターネットからダウンロードされ、Mac App Store を通じて公証されていないため、macOS が初回起動時にブロックする場合があります。
+
+**ステップ 1：** `picoclaw-launcher` をダブルクリックすると、セキュリティ警告が表示されます：
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="macOS Gatekeeper 警告" width="400">
+</p>
+
+> *"picoclaw-launcher" は開けません — "picoclaw-launcher" がMacに害を与えたりプライバシーを侵害するマルウェアを含まないことをAppleは確認できません。*
+
+**ステップ 2：** **システム設定** → **プライバシーとセキュリティ** を開き、**セキュリティ** セクションまでスクロールして **このまま開く** をクリック → ダイアログで再度 **開く** をクリックします。
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS プライバシーとセキュリティ — このまま開く" width="600">
+</p>
+
+この操作を一度行うと、以降の起動では警告が表示されなくなります。
+
+</details>
+
 ### 💻 TUI Launcher（ヘッドレス / SSH 向け推奨）

 TUI（Terminal UI）Launcher は設定と管理のためのフル機能ターミナルインターフェースを提供します。サーバー、Raspberry Pi、その他のヘッドレス環境に最適です。
@@ -367,6 +392,7 @@ PicoClaw は `model_list` 設定を通じて 30 以上の LLM Provider をサポ
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | 必須 | NVIDIA ホスティングモデル |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | 必須 | 高速推論 |
 | [Novita AI](https://novita.ai/) | `novita/` | 必須 | 各種オープンモデル |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | 必須 | MiMo モデル |
 | [Ollama](https://ollama.com/) | `ollama/` | 不要 | ローカルモデル、セルフホスト |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | 不要 | ローカルデプロイ、OpenAI 互換 |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | 場合による | 100 以上の Provider のプロキシ |
@@ -423,9 +449,7 @@ Provider の完全な設定詳細は [Provider とモデル](docs/ja/providers.m
 | **DingTalk** | 中級（クライアント認証情報） | Stream | [ガイド](docs/channels/dingtalk/README.ja.md) |
 | **Feishu / Lark** | 中級（App ID + Secret） | WebSocket/SDK | [ガイド](docs/channels/feishu/README.ja.md) |
 | **LINE** | 中級（認証情報 + webhook） | Webhook | [ガイド](docs/channels/line/README.ja.md) |
-| **WeCom Bot** | 中級（webhook URL） | Webhook | [ガイド](docs/channels/wecom/wecom_bot/README.ja.md) |
-| **WeCom App** | 中級（corp 認証情報） | Webhook | [ガイド](docs/channels/wecom/wecom_app/README.ja.md) |
-| **WeCom AI Bot** | 中級（トークン + AES キー） | WebSocket / Webhook | [ガイド](docs/channels/wecom/wecom_aibot/README.ja.md) |
+| **WeCom** | 簡単（QR ログインまたは手動） | WebSocket | [ガイド](docs/channels/wecom/README.md) |
 | **IRC** | 中級（サーバー + nick） | IRC protocol | [ガイド](docs/ja/chat-apps.md#irc) |
 | **OneBot** | 中級（WebSocket URL） | OneBot v11 | [ガイド](docs/channels/onebot/README.ja.md) |
 | **MaixCam** | 簡単（有効化） | TCP socket | [ガイド](docs/channels/maixcam/README.ja.md) |
@@ -56,17 +56,19 @@

 ## 📢 News

+2026-03-25 🚀 **v0.2.4 Released!** Agent architecture overhaul (SubTurn, Hooks, Steering, EventBus), WeChat/WeCom integration, security hardening (.security.yml, sensitive data filtering), new providers (AWS Bedrock, Azure, Xiaomi MiMo), and 35 bug fixes. PicoClaw has reached **26K Stars**!
+
 2026-03-17 🚀 **v0.2.3 Released!** System tray UI (Windows & Linux), sub-agent status query (`spawn_status`), experimental Gateway hot-reload, Cron security gating, and 2 security fixes. PicoClaw has reached **25K Stars**!

 2026-03-09 🎉 **v0.2.1 — Biggest update yet!** MCP protocol support, 4 new channels (Matrix/IRC/WeCom/Discord Proxy), 3 new providers (Kimi/Minimax/Avian), vision pipeline, JSONL memory store, model routing.

 2026-02-28 📦 **v0.2.0** released with Docker Compose and Web UI Launcher support.

-2026-02-26 🎉 PicoClaw hits **20K Stars** in just 17 days! Channel auto-orchestration and capability interfaces are live.
-
 <details>
 <summary>Earlier news...</summary>

+2026-02-26 🎉 PicoClaw hits **20K Stars** in just 17 days! Channel auto-orchestration and capability interfaces are live.
+
 2026-02-16 🎉 PicoClaw breaks 12K Stars in one week! Community maintainer roles and [Roadmap](ROADMAP.md) officially launched.

 2026-02-13 🎉 PicoClaw breaks 5000 Stars in 4 days! Project roadmap and developer groups in progress.
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — First Launch Security Warning</b></summary>
+
+macOS may block `picoclaw-launcher` on first launch because it is downloaded from the internet and not notarized through the Mac App Store.
+
+**Step 1:** Double-click `picoclaw-launcher`. You will see a security warning:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="macOS Gatekeeper warning" width="400">
+</p>
+
+> *"picoclaw-launcher" Not Opened — Apple could not verify "picoclaw-launcher" is free of malware that may harm your Mac or compromise your privacy.*
+
+**Step 2:** Open **System Settings** → **Privacy & Security** → scroll down to the **Security** section → click **Open Anyway** → confirm by clicking **Open Anyway** in the dialog.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Privacy & Security — Open Anyway" width="600">
+</p>
+
+After this one-time step, `picoclaw-launcher` will open normally on subsequent launches.
+
+</details>
+
 ### 💻 TUI Launcher (Recommended for Headless / SSH)

 The TUI (Terminal UI) Launcher provides a full-featured terminal interface for configuration and management. Ideal for servers, Raspberry Pi, and other headless environments.
@@ -370,6 +395,7 @@ PicoClaw supports 30+ LLM providers through the `model_list` configuration. Use
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Required | NVIDIA hosted models |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Required | Fast inference |
 | [Novita AI](https://novita.ai/) | `novita/` | Required | Various open models |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Required | MiMo models |
 | [Ollama](https://ollama.com/) | `ollama/` | Not needed | Local models, self-hosted |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Not needed | Local deployment, OpenAI-compatible |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Varies | Proxy for 100+ providers |
@@ -429,9 +455,7 @@ Talk to your PicoClaw through 17+ messaging platforms:
 | **DingTalk** | Medium (client credentials) | Stream | [Guide](docs/channels/dingtalk/README.md) |
 | **Feishu / Lark** | Medium (App ID + Secret) | WebSocket/SDK | [Guide](docs/channels/feishu/README.md) |
 | **LINE** | Medium (credentials + webhook) | Webhook | [Guide](docs/channels/line/README.md) |
-| **WeCom Bot** | Medium (webhook URL) | Webhook | [Guide](docs/channels/wecom/wecom_bot/README.md) |
-| **WeCom App** | Medium (corp credentials) | Webhook | [Guide](docs/channels/wecom/wecom_app/README.md) |
-| **WeCom AI Bot** | Medium (token + AES key) | WebSocket / Webhook | [Guide](docs/channels/wecom/wecom_aibot/README.md) |
+| **WeCom** | Easy (QR login or manual) | WebSocket | [Guide](docs/channels/wecom/README.md) |
 | **IRC** | Medium (server + nick) | IRC protocol | [Guide](docs/chat-apps.md#irc) |
 | **OneBot** | Medium (WebSocket URL) | OneBot v11 | [Guide](docs/channels/onebot/README.md) |
 | **MaixCam** | Easy (enable) | TCP socket | [Guide](docs/channels/maixcam/README.md) |
@@ -1,9 +1,9 @@
 <div align="center">
-  <img src="assets/logo.webp" alt="PicoClaw" width="512">
+<img src="assets/logo.webp" alt="PicoClaw" width="512">

-  <h1>PicoClaw: Pembantu AI Sangat Efisien dalam Go</h1>
+<h1>PicoClaw: Pembantu AI Ultra-Cekap dalam Go</h1>

-  <h3>Perkakasan $10 · RAM <10MB · Boot <1s · 皮皮虾，我们走！</h3>
+<h3>Perkakasan $10 · RAM 10MB · Boot ms · Jom, PicoClaw!</h3>
  <p>
    <img src="https://img.shields.io/badge/Go-1.25+-00ADD8?style=flat&logo=go&logoColor=white" alt="Go">
    <img src="https://img.shields.io/badge/Arch-x86__64%2C%20ARM64%2C%20MIPS%2C%20RISC--V%2C%20LoongArch-blue" alt="Hardware">
@@ -18,232 +18,582 @@
    <a href="https://discord.gg/V4sAZ9XWpN"><img src="https://img.shields.io/badge/Discord-Community-4c60eb?style=flat&logo=discord&logoColor=white" alt="Discord"></a>
  </p>

-[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | [Français](README.fr.md) | [Italiano](README.it.md) | [English](README.md) | **Bahasa Melayu**
+[中文](README.zh.md) | [日本語](README.ja.md) | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | [Français](README.fr.md) | [Italiano](README.it.md) | [Bahasa Indonesia](README.id.md) | **Malay** | [English](README.md)

 </div>

 ---

-> **PicoClaw** ialah projek sumber terbuka bebas yang dimulakan oleh [Sipeed](https://sipeed.com). Ia ditulis sepenuhnya dalam **Go** — bukan fork OpenClaw, NanoBot, atau mana-mana projek lain.
+> **PicoClaw** adalah projek sumber terbuka bebas yang dilancarkan oleh [Sipeed](https://sipeed.com), ditulis sepenuhnya dalam **Go** dari awal — bukan cabang OpenClaw, NanoBot, atau projek lain.

-🦐 PicoClaw ialah Pembantu AI peribadi yang sangat ringan, diinspirasikan oleh [NanoBot](https://github.com/HKUDS/nanobot), dan dibina semula sepenuhnya dalam Go melalui proses bootstrap kendiri, di mana agen AI itu sendiri memacu keseluruhan migrasi seni bina dan pengoptimuman kod.
+**PicoClaw** adalah pembantu AI peribadi ultra-ringan yang terinspirasi oleh [NanoBot](https://github.com/HKUDS/nanobot). Ia dibina semula dari awal dalam **Go** melalui proses "self-bootstrapping" — AI Agent itu sendiri yang memacu migrasi seni bina dan pengoptimuman kod.

-⚡️ Berjalan pada perkakasan $10 dengan RAM <10MB: Itu 99% kurang penggunaan memori berbanding OpenClaw dan 98% lebih murah berbanding Mac mini!
+**Berjalan pada perkakasan $10 dengan RAM <10MB** — 99% lebih sedikit memori daripada OpenClaw dan 98% lebih murah daripada Mac mini!

 <table align="center">
-  <tr align="center">
-    <td align="center" valign="top">
-      <p align="center">
-        <img src="assets/picoclaw_mem.gif" width="360" height="240">
-      </p>
-    </td>
-    <td align="center" valign="top">
-      <p align="center">
-        <img src="assets/licheervnano.png" width="400" height="240">
-      </p>
-    </td>
-  </tr>
+<tr align="center">
+<td align="center" valign="top">
+<p align="center">
+<img src="assets/picoclaw_mem.gif" width="360" height="240">
+</p>
+</td>
+<td align="center" valign="top">
+<p align="center">
+<img src="assets/licheervnano.png" width="400" height="240">
+</p>
+</td>
+</tr>
 </table>

 > [!CAUTION]
-> **🚨 KESELAMATAN & SALURAN RASMI / 安全声明**
->
-> * **TIADA KRIPTO:** PicoClaw **TIADA** token/coin rasmi. Semua dakwaan di `pump.fun` atau platform dagangan lain ialah **PENIPUAN**.
+> **Notis Keselamatan**
 >
+> * **TIADA KRIPTO:** PicoClaw **tidak** mengeluarkan sebarang token atau mata wang kripto rasmi. Semua tuntutan di `pump.fun` atau platform dagangan lain adalah **penipuan**.
 > * **DOMAIN RASMI:** Satu-satunya laman web rasmi ialah **[picoclaw.io](https://picoclaw.io)**, dan laman web syarikat ialah **[sipeed.com](https://sipeed.com)**
-> * **Amaran:** Banyak domain `.ai/.org/.com/.net/...` didaftarkan oleh pihak ketiga.
-> * **Amaran:** picoclaw masih dalam pembangunan awal dan mungkin mempunyai isu keselamatan rangkaian yang belum diselesaikan. Jangan deploy ke persekitaran produksi sebelum keluaran v1.0.
-> * **Nota:** picoclaw baru-baru ini telah menggabungkan banyak PR, yang mungkin menyebabkan penggunaan memori lebih besar (10–20MB) dalam versi terkini. Kami bercadang mengutamakan pengoptimuman sumber sebaik sahaja set ciri semasa mencapai keadaan stabil.
+> * **BERHATI-HATI:** Banyak domain `.ai/.org/.com/.net/...` telah didaftarkan oleh pihak ketiga. Jangan percayai mereka.
+> * **NOTA:** PicoClaw dalam pembangunan pesat awal. Mungkin terdapat isu keselamatan yang belum diselesaikan. Jangan deploy ke pengeluaran sebelum v1.0.
+

 ## 📢 Berita

-2026-03-17 🚀 **v0.2.3 Dikeluarkan!** UI system tray (Windows & Linux), penjejakan status sub-agen (`spawn_status`), hot-reload gateway eksperimen, gerbang keselamatan cron, dan 2 pembaikan keselamatan. PicoClaw kini mencecah **25K ⭐**!
+2026-03-25 🚀 **v0.2.4 Dikeluarkan!** Penstrukturan semula seni bina Agent (SubTurn, Hooks, Steering, EventBus), integrasi WeChat/WeCom, penguatan keselamatan (.security.yml, penapisan data sensitif), penyedia baharu (AWS Bedrock, Azure, Xiaomi MiMo), dan 35 pembetulan pepijat. PicoClaw mencapai **26K Stars**!

-2026-03-09 🎉 **v0.2.1 — Kemas kini terbesar setakat ini!** Sokongan protokol MCP, 4 saluran baharu (Matrix/IRC/WeCom/Discord Proxy), 3 penyedia baharu (Kimi/Minimax/Avian), pipeline vision, stor memori JSONL, dan routing model.
+2026-03-17 🚀 **v0.2.3 Dikeluarkan!** UI dulang sistem (Windows & Linux), pertanyaan status sub-agent (`spawn_status`), muat semula panas Gateway eksperimental, kawalan keselamatan Cron, dan 2 pembetulan keselamatan. PicoClaw mencapai **25K Stars**!

-2026-02-28 📦 **v0.2.0** dikeluarkan dengan sokongan Docker Compose dan pelancar Web UI.
+2026-03-09 🎉 **v0.2.1 — Kemas kini terbesar setakat ini!** Sokongan protokol MCP, 4 saluran baharu (Matrix/IRC/WeCom/Discord Proxy), 3 penyedia baharu (Kimi/Minimax/Avian), saluran paip visi, storan memori JSONL, penghalaan model.

-2026-02-26 🎉 PicoClaw mencapai **20K stars** dalam hanya 17 hari! Auto-orchestration saluran dan antara muka capability telah tiba.
+2026-02-28 📦 **v0.2.0** dikeluarkan dengan sokongan Docker Compose dan Pelancar Web UI.

 <details>
-<summary>Berita lama...</summary>
+<summary>Berita terdahulu...</summary>

-2026-02-16 🎉 PicoClaw mencapai 12K stars dalam seminggu! Peranan penyelenggara komuniti dan [roadmap](ROADMAP.md) telah disiarkan secara rasmi.
+2026-02-26 🎉 PicoClaw mencapai **20K Stars** hanya dalam 17 hari! Orkestrasi saluran automatik dan antara muka keupayaan kini aktif.

-2026-02-13 🎉 PicoClaw mencapai 5000 stars dalam 4 hari! Roadmap projek dan kumpulan pembangun sedang disusun.
+2026-02-16 🎉 PicoClaw melepasi 12K Stars dalam seminggu! Peranan penyelenggara komuniti dan [Peta Jalan](ROADMAP.md) dilancarkan secara rasmi.

-2026-02-09 🎉 **PicoClaw Dilancarkan!** Dibina dalam 1 hari untuk membawa AI Agents ke perkakasan $10 dengan RAM <10MB. 🦐 PicoClaw, jom pergi!
+2026-02-13 🎉 PicoClaw melepasi 5000 Stars dalam 4 hari! Peta jalan projek dan kumpulan pembangun sedang dalam proses.
+
+2026-02-09 🎉 **PicoClaw Dikeluarkan!** Dibina dalam 1 hari untuk membawa AI Agent ke perkakasan $10 dengan RAM <10MB. Jom, PicoClaw!

 </details>

 ## ✨ Ciri-ciri

-🪶 **Sangat Ringan**: Penggunaan memori <10MB — 99% lebih kecil daripada fungsi teras OpenClaw.*
+🪶 **Ultra-ringan**: Jejak memori teras <10MB — 99% lebih kecil daripada OpenClaw.*

-💰 **Kos Minimum**: Cukup efisien untuk berjalan pada perkakasan $10 — 98% lebih murah daripada Mac mini.
+💰 **Kos minimum**: Cukup cekap untuk berjalan pada perkakasan $10 — 98% lebih murah daripada Mac mini.

-⚡️ **Sangat Pantas**: Masa startup 400X lebih pantas, but dalam <1 saat walaupun pada teras tunggal 0.6GHz.
+⚡️ **Boot kilat**: 400x lebih pantas. Boot dalam <1s walaupun pada pemproses teras tunggal 0.6GHz.

-🌍 **Portabiliti Sebenar**: Satu binari self-contained merentas RISC-V, ARM, MIPS, dan x86, satu klik untuk terus berjalan!
+🌍 **Benar-benar mudah alih**: Binari tunggal merentasi seni bina RISC-V, ARM, MIPS, dan x86.

-🤖 **Dibootstrapping oleh AI**: Pelaksanaan Go-native autonomi — 95% teras dijana oleh Agent dengan penambahbaikan human-in-the-loop.
+🤖 **Dibantu AI**: Pelaksanaan Go tulen — 95% kod teras dijana oleh Agent dan diperhalusi melalui semakan manusia.

-🔌 **Sokongan MCP**: Integrasi asli [Model Context Protocol](https://modelcontextprotocol.io/) — sambungkan mana-mana pelayan MCP untuk melanjutkan keupayaan agen.
+🔌 **Sokongan MCP**: Integrasi [Model Context Protocol](https://modelcontextprotocol.io/) natif.

-👁️ **Pipeline Vision**: Hantar imej dan fail terus kepada agen — pengekodan base64 automatik untuk LLM multimodal.
+👁️ **Saluran paip visi**: Hantar imej dan fail terus ke Agent — pengekodan base64 automatik untuk LLM multimodal.

-🧠 **Routing Pintar**: Routing model berasaskan peraturan — pertanyaan mudah pergi ke model ringan, menjimatkan kos API.
+🧠 **Penghalaan pintar**: Penghalaan model berasaskan peraturan — pertanyaan mudah ke model ringan, menjimatkan kos API.

-_*Versi terkini mungkin menggunakan 10–20MB disebabkan banyak gabungan ciri yang pantas. Pengoptimuman sumber dirancang. Perbandingan startup berdasarkan penanda aras teras tunggal 0.8GHz (lihat jadual di bawah)._
+_*Binaan terkini mungkin menggunakan 10-20MB disebabkan penggabungan PR yang pesat. Pengoptimuman sumber dirancang. Perbandingan kelajuan boot berdasarkan penanda aras teras tunggal 0.8GHz (lihat jadual di bawah)._

-|                                | OpenClaw      | NanoBot                        | **PicoClaw**                                   |
-| ------------------------------ | ------------- | ------------------------------ | ---------------------------------------------- |
-| **Bahasa**                     | TypeScript    | Python                         | **Go**                                         |
-| **RAM**                        | >1GB          | >100MB                         | **< 10MB***                                    |
-| **Startup**</br>(teras 0.8GHz) | >500s         | >30s                           | **<1s**                                        |
-| **Kos**                        | Mac Mini $599 | Kebanyakan Linux SBC </br>~$50 | **Mana-mana papan Linux**</br>**Serendah $10** |
+<div align="center">
+
+|                                | OpenClaw      | NanoBot                  | **PicoClaw**                           |
+| ------------------------------ | ------------- | ------------------------ | -------------------------------------- |
+| **Bahasa**                     | TypeScript    | Python                   | **Go**                                 |
+| **RAM**                        | >1GB          | >100MB                   | **< 10MB***                            |
+| **Masa Boot** (teras 0.8GHz)   | >500s         | >30s                     | **<1s**                                |
+| **Kos**                        | Mac Mini $599 | Kebanyakan papan Linux ~$50 | **Mana-mana papan Linux dari $10**  |

 <img src="assets/compare.jpg" alt="PicoClaw" width="512">

+</div>
+
+> **[Senarai Keserasian Perkakasan](docs/hardware-compatibility.md)** — Lihat semua papan yang diuji, dari RISC-V $5 hingga Raspberry Pi hingga telefon Android.
+
+<p align="center">
+<img src="assets/hardware-banner.jpg" alt="Keserasian Perkakasan PicoClaw" width="100%">
+</p>
+
 ## 🦾 Demonstrasi

 ### 🛠️ Aliran Kerja Pembantu Standard

 <table align="center">
-  <tr align="center">
-    <th><p align="center">🧩 Jurutera Full-Stack</p></th>
-    <th><p align="center">🗂️ Pengurusan Log & Perancangan</p></th>
-    <th><p align="center">🔎 Carian Web & Pembelajaran</p></th>
-  </tr>
-  <tr>
-    <td align="center"><p align="center"><img src="assets/picoclaw_code.gif" width="240" height="180"></p></td>
-    <td align="center"><p align="center"><img src="assets/picoclaw_memory.gif" width="240" height="180"></p></td>
-    <td align="center"><p align="center"><img src="assets/picoclaw_search.gif" width="240" height="180"></p></td>
-  </tr>
-  <tr>
-    <td align="center">Bangunkan • Deploy • Skalakan</td>
-    <td align="center">Jadual • Automasi • Memori</td>
-    <td align="center">Penemuan • Insight • Trend</td>
-  </tr>
+<tr align="center">
+<th><p align="center">Mod Jurutera Full-Stack</p></th>
+<th><p align="center">Pengelogan & Perancangan</p></th>
+<th><p align="center">Carian Web & Pembelajaran</p></th>
+</tr>
+<tr>
+<td align="center"><p align="center"><img src="assets/picoclaw_code.gif" width="240" height="180"></p></td>
+<td align="center"><p align="center"><img src="assets/picoclaw_memory.gif" width="240" height="180"></p></td>
+<td align="center"><p align="center"><img src="assets/picoclaw_search.gif" width="240" height="180"></p></td>
+</tr>
+<tr>
+<td align="center">Bangun · Deploy · Skala</td>
+<td align="center">Jadual · Automatik · Ingat</td>
+<td align="center">Temui · Wawasan · Trend</td>
+</tr>
 </table>

-### 📱 Jalankan pada Telefon Android Lama
+### 🐜 Deployment Jejak Rendah yang Inovatif

-Berikan telefon lama anda hayat kedua! Tukarkannya menjadi Pembantu AI pintar dengan PicoClaw. Permulaan pantas:
+PicoClaw boleh digunakan pada hampir mana-mana peranti Linux!

-1. **Pasang [Termux](https://github.com/termux/termux-app)** (Muat turun dari [GitHub Releases](https://github.com/termux/termux-app/releases), atau cari di F-Droid / Google Play).
-2. **Jalankan arahan**
-
-```bash
-# Download the latest release from https://github.com/sipeed/picoclaw/releases
-wget https://github.com/sipeed/picoclaw/releases/latest/download/picoclaw_Linux_arm64.tar.gz
-tar xzf picoclaw_Linux_arm64.tar.gz
-pkg install proot
-termux-chroot ./picoclaw onboard
-```
-
-Selepas itu, ikut arahan dalam bahagian "Quick Start" untuk melengkapkan konfigurasi!
-
-<img src="assets/termux.jpg" alt="PicoClaw" width="512">
-
-### 🐜 Deploy Jejak Sumber Rendah yang Inovatif
-
-PicoClaw boleh dideploy pada hampir mana-mana peranti Linux!
-
- $9.9 [LicheeRV-Nano](https://www.aliexpress.com/item/1005006519668532.html) versi E(Ethernet) atau W(WiFi6), untuk pembantu rumah minimum
- $30~50 [NanoKVM](https://www.aliexpress.com/item/1005007369816019.html), atau $100 [NanoKVM-Pro](https://www.aliexpress.com/item/1005010048471263.html) untuk penyelenggaraan pelayan automatik
- $50 [MaixCAM](https://www.aliexpress.com/item/1005008053333693.html) atau $100 [MaixCAM2](https://www.kickstarter.com/projects/zepan/maixcam2-build-your-next-gen-4k-ai-camera) untuk pemantauan pintar
+- $9.9 [LicheeRV-Nano](https://www.aliexpress.com/item/1005006519668532.html) untuk pembantu rumah minimal
+- $30~50 [NanoKVM](https://www.aliexpress.com/item/1005007369816019.html) untuk operasi pelayan automatik
+- $50 [MaixCAM](https://www.aliexpress.com/item/1005008053333693.html) untuk pengawasan pintar

 <https://private-user-images.githubusercontent.com/83055338/547056448-e7b031ff-d6f5-4468-bcca-5726b6fecb5c.mp4>

-🌟 Lebih banyak senario deployment sedang menanti!
+🌟 Lebih Banyak Kes Deployment Menanti!
+

 ## 📦 Pemasangan

-### Pasang dengan binari prabina
+### Muat turun dari picoclaw.io (Disyorkan)

-Muat turun binari untuk platform anda dari halaman [Releases](https://github.com/sipeed/picoclaw/releases).
+Lawati **[picoclaw.io](https://picoclaw.io)** — laman web rasmi mengesan platform anda secara automatik dan menyediakan muat turun satu klik.

-### Pasang dari sumber (ciri terkini, disyorkan untuk pembangunan)
+### Muat turun binari pra-kompil
+
+Muat turun binari untuk platform anda dari halaman [GitHub Releases](https://github.com/sipeed/picoclaw/releases).
+
+### Bina dari sumber (untuk pembangunan)

 ```bash
 git clone https://github.com/sipeed/picoclaw.git
-
 cd picoclaw
 make deps

-# Build, no need to install
+# Bina binari teras
 make build

-# Build for multiple platforms
+# Bina Pelancar Web UI (diperlukan untuk mod WebUI)
+make build-launcher
+
+# Bina untuk pelbagai platform
 make build-all

-# Build for Raspberry Pi Zero 2 W (32-bit: make build-linux-arm; 64-bit: make build-linux-arm64)
+# Bina untuk Raspberry Pi Zero 2 W (32-bit: make build-linux-arm; 64-bit: make build-linux-arm64)
 make build-pi-zero

-# Build And Install
+# Bina dan pasang
 make install
 ```

-**Raspberry Pi Zero 2 W:** Gunakan binari yang sepadan dengan OS anda: Raspberry Pi OS 32-bit → `make build-linux-arm`; 64-bit → `make build-linux-arm64`. Atau jalankan `make build-pi-zero` untuk membina kedua-duanya.
+**Raspberry Pi Zero 2 W:** Gunakan binari yang sepadan dengan OS anda: Raspberry Pi OS 32-bit -> `make build-linux-arm`; 64-bit -> `make build-linux-arm64`. Atau jalankan `make build-pi-zero` untuk membina kedua-duanya.

-## 📚 Dokumentasi
+## 🚀 Panduan Permulaan Pantas

-Untuk panduan terperinci, lihat dokumen di bawah. README hanya meliputi quick start.
+### 🌐 Pelancar WebUI (Disyorkan untuk Desktop)

-| Topik                                                 | Penerangan                                                                                          |
-| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
-| 🐳 [Docker & Quick Start](docs/my/docker.md)           | Setup Docker Compose, mod Launcher/Agent, konfigurasi Quick Start                                   |
-| 💬 [Aplikasi Sembang](docs/my/chat-apps.md)            | Telegram, Discord, WhatsApp, Matrix, QQ, Slack, IRC, DingTalk, LINE, Feishu, WeCom, dan banyak lagi |
-| ⚙️ [Konfigurasi](docs/my/configuration.md)             | Pemboleh ubah persekitaran, susun atur workspace, sumber skill, security sandbox, heartbeat         |
-| 🔌 [Penyedia & Model](docs/my/providers.md)            | 20+ penyedia LLM, routing model, konfigurasi model_list, seni bina penyedia                         |
-| 🔄 [Spawn & Tugasan Async](docs/my/spawn-tasks.md)     | Tugasan cepat, tugasan panjang dengan spawn, orkestrasi sub-agen async                              |
-| 🐛 [Penyelesaian Masalah](docs/my/troubleshooting.md)  | Masalah lazim dan penyelesaiannya                                                                   |
-| 🔧 [Konfigurasi Tools](docs/my/tools_configuration.md) | Hidup/mati per tool, polisi exec                                                                    |
+Pelancar WebUI menyediakan antara muka berasaskan pelayar untuk konfigurasi dan sembang. Ini adalah cara termudah untuk bermula — tiada pengetahuan baris arahan diperlukan.
+
+**Pilihan 1: Klik dua kali (Desktop)**
+
+Selepas memuat turun dari [picoclaw.io](https://picoclaw.io), klik dua kali `picoclaw-launcher` (atau `picoclaw-launcher.exe` pada Windows). Pelayar anda akan dibuka secara automatik di `http://localhost:18800`.
+
+**Pilihan 2: Baris arahan**
+
+```bash
+picoclaw-launcher
+# Buka http://localhost:18800 dalam pelayar anda
+```
+
+> [!TIP]
+> **Akses jauh / Docker / VM:** Tambah bendera `-public` untuk mendengar pada semua antara muka:
+> ```bash
+> picoclaw-launcher -public
+> ```
+
+<p align="center">
+<img src="assets/launcher-webui.jpg" alt="Pelancar WebUI" width="600">
+</p>
+
+**Memulakan:** Buka WebUI, kemudian: **1)** Konfigurasikan Penyedia (tambah kunci API LLM) -> **2)** Konfigurasikan Saluran (cth. Telegram) -> **3)** Mulakan Gateway -> **4)** Sembang!
+
+Untuk dokumentasi WebUI terperinci, lihat [docs.picoclaw.io](https://docs.picoclaw.io).
+
+<details>
+<summary><b>Docker (alternatif)</b></summary>
+
+```bash
+# 1. Klon repo ini
+git clone https://github.com/sipeed/picoclaw.git
+cd picoclaw
+
+# 2. Jalankan pertama kali — jana docker/data/config.json secara automatik kemudian keluar
+docker compose -f docker/docker-compose.yml --profile launcher up
+
+# 3. Tetapkan kunci API anda
+vim docker/data/config.json
+
+# 4. Mulakan
+docker compose -f docker/docker-compose.yml --profile launcher up -d
+# Buka http://localhost:18800
+```
+
+> **Pengguna Docker / VM:** Gateway mendengar pada `127.0.0.1` secara lalai. Tetapkan `PICOCLAW_GATEWAY_HOST=0.0.0.0` atau gunakan bendera `-public` untuk membolehkan akses dari hos.
+
+```bash
+# Semak log
+docker compose -f docker/docker-compose.yml logs -f
+
+# Henti
+docker compose -f docker/docker-compose.yml --profile launcher down
+
+# Kemas kini
+docker compose -f docker/docker-compose.yml pull
+docker compose -f docker/docker-compose.yml --profile launcher up -d
+```
+
+</details>
+
+
+<details>
+<summary><b>macOS — Amaran Keselamatan Pelancaran Pertama</b></summary>
+
+macOS mungkin menyekat `picoclaw-launcher` pada pelancaran pertama kerana ia dimuat turun dari internet dan tidak disahkan melalui Mac App Store.
+
+**Langkah 1:** Klik dua kali `picoclaw-launcher`. Anda akan melihat amaran keselamatan:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Amaran macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" Tidak Dibuka — Apple tidak dapat mengesahkan "picoclaw-launcher" bebas daripada perisian hasad yang mungkin membahayakan Mac anda atau menjejaskan privasi anda.*
+
+**Langkah 2:** Buka **Tetapan Sistem** → **Privasi & Keselamatan** → tatal ke bawah ke bahagian **Keselamatan** → klik **Buka Juga** → sahkan dengan mengklik **Buka Juga** dalam dialog.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Privasi & Keselamatan — Buka Juga" width="600">
+</p>
+
+Selepas langkah sekali ini, `picoclaw-launcher` akan dibuka secara normal pada pelancaran seterusnya.
+
+</details>
+
+### 💻 Pelancar TUI (Disyorkan untuk Headless / SSH)
+
+Pelancar TUI menyediakan antara muka terminal lengkap untuk konfigurasi dan pengurusan. Sesuai untuk pelayan, Raspberry Pi, dan persekitaran tanpa kepala lain.
+
+```bash
+picoclaw-launcher-tui
+```
+
+<p align="center">
+<img src="assets/launcher-tui.jpg" alt="Pelancar TUI" width="600">
+</p>
+
+**Memulakan:**
+
+Gunakan menu TUI untuk: **1)** Konfigurasikan Penyedia -> **2)** Konfigurasikan Saluran -> **3)** Mulakan Gateway -> **4)** Sembang!
+
+Untuk dokumentasi TUI terperinci, lihat [docs.picoclaw.io](https://docs.picoclaw.io).
+
+### 📱 Android
+
+Berikan telefon lama anda kehidupan baru! Jadikannya Pembantu AI pintar dengan PicoClaw.
+
+**Pilihan 1: Termux (tersedia sekarang)**
+
+1. Pasang [Termux](https://github.com/termux/termux-app) (muat turun dari [GitHub Releases](https://github.com/termux/termux-app/releases), atau cari di F-Droid / Google Play)
+2. Jalankan arahan berikut:
+
+```bash
+# Muat turun keluaran terkini
+wget https://github.com/sipeed/picoclaw/releases/latest/download/picoclaw_Linux_arm64.tar.gz
+tar xzf picoclaw_Linux_arm64.tar.gz
+pkg install proot
+termux-chroot ./picoclaw onboard   # chroot menyediakan susun atur sistem fail Linux standard
+```
+
+Kemudian ikuti bahagian Pelancar Terminal di bawah untuk melengkapkan konfigurasi.
+
+<img src="assets/termux.jpg" alt="PicoClaw pada Termux" width="512">
+
+**Pilihan 2: APK (akan datang)**
+
+APK Android bebas dengan WebUI terbina dalam sedang dalam pembangunan. Nantikan!
+
+<details>
+<summary><b>Pelancar Terminal (untuk persekitaran terhad sumber)</b></summary>
+
+Untuk persekitaran minimal di mana hanya binari teras `picoclaw` tersedia (tiada UI Pelancar), anda boleh mengkonfigurasi semua melalui baris arahan dan fail konfigurasi JSON.
+
+**1. Mulakan**
+
+```bash
+picoclaw onboard
+```
+
+Ini mencipta `~/.picoclaw/config.json` dan direktori ruang kerja.
+
+**2. Konfigurasikan** (`~/.picoclaw/config.json`)
+
+```json
+{
+  "agents": {
+    "defaults": {
+      "model_name": "gpt-5.4"
+    }
+  },
+  "model_list": [
+    {
+      "model_name": "gpt-5.4",
+      "model": "openai/gpt-5.4"
+    }
+  ]
+}
+```
+
+> Lihat `config/config.example.json` dalam repo untuk templat konfigurasi lengkap. Nota: kunci API kini disimpan dalam `.security.yml`, bukan `config.json`.
+
+**3. Sembang**
+
+```bash
+picoclaw agent -m "Apa itu 2+2?"
+
+# Mod interaktif
+picoclaw agent
+
+# Mulakan gateway untuk integrasi aplikasi sembang
+picoclaw gateway
+```
+
+</details>
+
+
+## 🔌 Penyedia (LLM)
+
+PicoClaw menyokong 30+ penyedia LLM melalui konfigurasi `model_list`. Gunakan format `protokol/model`:
+
+| Penyedia | Protokol | Kunci API | Nota |
+|----------|----------|-----------|------|
+| [OpenAI](https://platform.openai.com/api-keys) | `openai/` | Diperlukan | GPT-5.4, GPT-4o, o3, dll. |
+| [Anthropic](https://console.anthropic.com/settings/keys) | `anthropic/` | Diperlukan | Claude Opus 4.6, Sonnet 4.6, dll. |
+| [Google Gemini](https://aistudio.google.com/apikey) | `gemini/` | Diperlukan | Gemini 3 Flash, 2.5 Pro, dll. |
+| [OpenRouter](https://openrouter.ai/keys) | `openrouter/` | Diperlukan | 200+ model, API bersatu |
+| [Zhipu (GLM)](https://open.bigmodel.cn/usercenter/proj-mgmt/apikeys) | `zhipu/` | Diperlukan | GLM-4.7, GLM-5, dll. |
+| [DeepSeek](https://platform.deepseek.com/api_keys) | `deepseek/` | Diperlukan | DeepSeek-V3, DeepSeek-R1 |
+| [Volcengine](https://console.volcengine.com) | `volcengine/` | Diperlukan | Doubao, model Ark |
+| [Qwen](https://dashscope.console.aliyun.com/apiKey) | `qwen/` | Diperlukan | Qwen3, Qwen-Max, dll. |
+| [Groq](https://console.groq.com/keys) | `groq/` | Diperlukan | Inferens pantas (Llama, Mixtral) |
+| [Moonshot (Kimi)](https://platform.moonshot.cn/console/api-keys) | `moonshot/` | Diperlukan | Model Kimi |
+| [Minimax](https://platform.minimaxi.com/user-center/basic-information/interface-key) | `minimax/` | Diperlukan | Model MiniMax |
+| [Mistral](https://console.mistral.ai/api-keys) | `mistral/` | Diperlukan | Mistral Large, Codestral |
+| [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Diperlukan | Model hos NVIDIA |
+| [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Diperlukan | Inferens pantas |
+| [Novita AI](https://novita.ai/) | `novita/` | Diperlukan | Pelbagai model terbuka |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Diperlukan | Model MiMo |
+| [Ollama](https://ollama.com/) | `ollama/` | Tidak perlu | Model tempatan, self-hosted |
+| [vLLM](https://docs.vllm.ai/) | `vllm/` | Tidak perlu | Deployment tempatan, serasi OpenAI |
+| [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Berbeza | Proksi untuk 100+ penyedia |
+| [Azure OpenAI](https://portal.azure.com/) | `azure/` | Diperlukan | Deployment Azure perusahaan |
+| [GitHub Copilot](https://github.com/features/copilot) | `github-copilot/` | OAuth | Log masuk kod peranti |
+| [Antigravity](https://console.cloud.google.com/) | `antigravity/` | OAuth | Google Cloud AI |
+| [AWS Bedrock](https://console.aws.amazon.com/bedrock)* | `bedrock/` | Kelayakan AWS | Claude, Llama, Mistral pada AWS |
+
+> \* AWS Bedrock memerlukan tag binaan: `go build -tags bedrock`. Tetapkan `api_base` kepada nama rantau (cth. `us-east-1`) untuk resolusi endpoint automatik merentasi semua partition AWS. Apabila menggunakan URL endpoint penuh, anda juga perlu mengkonfigurasi `AWS_REGION` melalui pemboleh ubah persekitaran.
+
+<details>
+<summary><b>Deployment tempatan (Ollama, vLLM, dll.)</b></summary>
+
+**Ollama:**
+```json
+{
+  "model_list": [
+    {
+      "model_name": "local-llama",
+      "model": "ollama/llama3.1:8b",
+      "api_base": "http://localhost:11434/v1"
+    }
+  ]
+}
+```
+
+**vLLM:**
+```json
+{
+  "model_list": [
+    {
+      "model_name": "local-vllm",
+      "model": "vllm/your-model",
+      "api_base": "http://localhost:8000/v1"
+    }
+  ]
+}
+```
+
+Untuk butiran konfigurasi penyedia penuh, lihat [Penyedia & Model](docs/providers.md).
+
+</details>
+
+
+## 💬 Saluran (Aplikasi Sembang)
+
+Bercakap dengan PicoClaw anda melalui 17+ platform pemesejan:
+
+| Saluran | Persediaan | Protokol | Dok |
+|---------|-----------|----------|-----|
+| **Telegram** | Mudah (token bot) | Long polling | [Panduan](docs/channels/telegram/README.md) |
+| **Discord** | Mudah (token bot + intents) | WebSocket | [Panduan](docs/channels/discord/README.md) |
+| **WhatsApp** | Mudah (imbas QR atau URL jambatan) | Natif / Jambatan | [Panduan](docs/chat-apps.md#whatsapp) |
+| **Weixin** | Mudah (imbas QR natif) | iLink API | [Panduan](docs/chat-apps.md#weixin) |
+| **QQ** | Mudah (AppID + AppSecret) | WebSocket | [Panduan](docs/channels/qq/README.md) |
+| **Slack** | Mudah (token bot + app) | Socket Mode | [Panduan](docs/channels/slack/README.md) |
+| **Matrix** | Sederhana (homeserver + token) | Sync API | [Panduan](docs/channels/matrix/README.md) |
+| **DingTalk** | Sederhana (kelayakan klien) | Stream | [Panduan](docs/channels/dingtalk/README.md) |
+| **Feishu / Lark** | Sederhana (App ID + Secret) | WebSocket/SDK | [Panduan](docs/channels/feishu/README.md) |
+| **LINE** | Sederhana (kelayakan + webhook) | Webhook | [Panduan](docs/channels/line/README.md) |
+| **WeCom** | Mudah (log masuk QR atau manual) | WebSocket | [Panduan](docs/channels/wecom/README.md) |
+| **IRC** | Sederhana (pelayan + nick) | Protokol IRC | [Panduan](docs/chat-apps.md#irc) |
+| **OneBot** | Sederhana (URL WebSocket) | OneBot v11 | [Panduan](docs/channels/onebot/README.md) |
+| **MaixCam** | Mudah (aktifkan) | TCP socket | [Panduan](docs/channels/maixcam/README.md) |
+| **Pico** | Mudah (aktifkan) | Protokol natif | Terbina dalam |
+| **Pico Client** | Mudah (URL WebSocket) | WebSocket | Terbina dalam |
+
+> Semua saluran berasaskan webhook berkongsi satu pelayan HTTP Gateway (`gateway.host`:`gateway.port`, lalai `127.0.0.1:18790`). Feishu menggunakan mod WebSocket/SDK dan tidak menggunakan pelayan HTTP yang dikongsi.
+
+Untuk arahan persediaan saluran terperinci, lihat [Konfigurasi Aplikasi Sembang](docs/my/chat-apps.md).
+
+## 🔧 Alat
+
+### 🔍 Carian Web
+
+PicoClaw boleh mencari web untuk menyediakan maklumat terkini. Konfigurasikan dalam `tools.web`:
+
+| Enjin Carian | Kunci API | Peringkat Percuma | Pautan |
+|-------------|-----------|-------------------|--------|
+| DuckDuckGo | Tidak perlu | Tanpa had | Sandaran terbina dalam |
+| [Baidu Search](https://cloud.baidu.com/doc/qianfan-api/s/Wmbq4z7e5) | Diperlukan | 1000 pertanyaan/hari | Dikuasai AI, dioptimumkan untuk China |
+| [Tavily](https://tavily.com) | Diperlukan | 1000 pertanyaan/bulan | Dioptimumkan untuk AI Agent |
+| [Brave Search](https://brave.com/search/api) | Diperlukan | 2000 pertanyaan/bulan | Pantas dan peribadi |
+| [Perplexity](https://www.perplexity.ai) | Diperlukan | Berbayar | Carian dikuasai AI |
+| [SearXNG](https://github.com/searxng/searxng) | Tidak perlu | Self-hosted | Enjin metasearch percuma |
+| [GLM Search](https://open.bigmodel.cn/) | Diperlukan | Berbeza | Carian web Zhipu |
+
+### ⚙️ Alat Lain
+
+PicoClaw menyertakan alat terbina dalam untuk operasi fail, pelaksanaan kod, penjadualan, dan banyak lagi. Lihat [Konfigurasi Alat](docs/tools_configuration.md) untuk butiran.
+
+## 🎯 Kemahiran
+
+Kemahiran adalah keupayaan modular yang melanjutkan Agent anda. Ia dimuatkan dari fail `SKILL.md` dalam ruang kerja anda.
+
+**Pasang kemahiran dari ClawHub:**
+
+```bash
+picoclaw skills search "web scraping"
+picoclaw skills install <nama-kemahiran>
+```
+
+**Konfigurasikan token ClawHub** (pilihan, untuk had kadar lebih tinggi):
+
+Tambah ke `config.json` anda:
+```json
+{
+  "tools": {
+    "skills": {
+      "registries": {
+        "clawhub": {
+          "auth_token": "your-clawhub-token"
+        }
+      }
+    }
+  }
+}
+```
+
+Untuk butiran lanjut, lihat [Konfigurasi Alat - Kemahiran](docs/tools_configuration.md#skills-tool).
+
+## 🔗 MCP (Protokol Konteks Model)
+
+PicoClaw menyokong [MCP](https://modelcontextprotocol.io/) secara natif — sambungkan mana-mana pelayan MCP untuk melanjutkan keupayaan Agent anda dengan alat dan sumber data luaran.
+
+```json
+{
+  "tools": {
+    "mcp": {
+      "enabled": true,
+      "servers": {
+        "filesystem": {
+          "enabled": true,
+          "command": "npx",
+          "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
+        }
+      }
+    }
+  }
+}
+```
+
+Untuk konfigurasi MCP penuh (pengangkutan stdio, SSE, HTTP, Penemuan Alat), lihat [Konfigurasi Alat - MCP](docs/tools_configuration.md#mcp-tool).

 ## <img src="assets/clawdchat-icon.png" width="24" height="24" alt="ClawdChat"> Sertai Rangkaian Sosial Agent

-Sambungkan Picoclaw ke Rangkaian Sosial Agent hanya dengan menghantar satu mesej melalui CLI atau mana-mana Aplikasi Sembang yang disepadukan.
+Sambungkan PicoClaw ke Rangkaian Sosial Agent dengan menghantar satu mesej melalui CLI atau mana-mana Aplikasi Sembang yang disepadukan.

-**Baca `https://clawdchat.ai/skill.md` dan ikut arahan untuk menyertai [ClawdChat.ai](https://clawdchat.ai)**
+**Baca `https://clawdchat.ai/skill.md` dan ikuti arahan untuk menyertai [ClawdChat.ai](https://clawdchat.ai)**

 ## 🖥️ Rujukan CLI

-| Arahan                    | Penerangan                      |
-| ------------------------- | ------------------------------- |
-| `picoclaw onboard`        | Inisialisasi config & workspace |
-| `picoclaw agent -m "..."` | Berbual dengan agen             |
-| `picoclaw agent`          | Mod sembang interaktif          |
-| `picoclaw gateway`        | Mulakan gateway                 |
-| `picoclaw status`         | Papar status                    |
-| `picoclaw version`        | Papar info versi                |
-| `picoclaw cron list`      | Senaraikan semua job berjadual  |
-| `picoclaw cron add ...`   | Tambah job berjadual            |
-| `picoclaw cron disable`   | Nyahaktifkan job berjadual      |
-| `picoclaw cron remove`    | Buang job berjadual             |
-| `picoclaw skills list`    | Senaraikan skill yang dipasang  |
-| `picoclaw skills install` | Pasang skill                    |
-| `picoclaw migrate`        | Migrasi data dari versi lama    |
-| `picoclaw auth login`     | Autentikasi dengan penyedia     |
+| Arahan | Penerangan |
+| ------ | ---------- |
+| `picoclaw onboard` | Mulakan konfigurasi & ruang kerja |
+| `picoclaw auth weixin` | Sambungkan akaun WeChat melalui QR |
+| `picoclaw agent -m "..."` | Sembang dengan agent |
+| `picoclaw agent` | Mod sembang interaktif |
+| `picoclaw gateway` | Mulakan gateway |
+| `picoclaw status` | Tunjukkan status |
+| `picoclaw version` | Tunjukkan maklumat versi |
+| `picoclaw model` | Lihat atau tukar model lalai |
+| `picoclaw cron list` | Senaraikan semua kerja berjadual |
+| `picoclaw cron add ...` | Tambah kerja berjadual |
+| `picoclaw cron disable` | Lumpuhkan kerja berjadual |
+| `picoclaw cron remove` | Buang kerja berjadual |
+| `picoclaw skills list` | Senaraikan kemahiran yang dipasang |
+| `picoclaw skills install` | Pasang kemahiran |
+| `picoclaw migrate` | Migrasi data dari versi lama |
+| `picoclaw auth login` | Sahkan dengan penyedia |

-### Tugasan Berjadual / Peringatan
+### ⏰ Tugasan Berjadual / Peringatan

-PicoClaw menyokong peringatan berjadual dan tugasan berulang melalui tool `cron`:
+PicoClaw menyokong peringatan berjadual dan tugasan berulang melalui alat `cron`:

-* **Peringatan sekali**: "Ingatkan saya dalam 10 minit" → dicetus sekali selepas 10 minit
-* **Tugasan berulang**: "Ingatkan saya setiap 2 jam" → dicetus setiap 2 jam
-* **Ungkapan cron**: "Ingatkan saya pada 9 pagi setiap hari" → menggunakan ungkapan cron
+* **Peringatan sekali**: "Ingatkan saya dalam 10 minit" -> pencetus sekali selepas 10 minit
+* **Tugasan berulang**: "Ingatkan saya setiap 2 jam" -> pencetus setiap 2 jam
+* **Ungkapan Cron**: "Ingatkan saya pada pukul 9 pagi setiap hari" -> menggunakan ungkapan cron

-## 🤝 Sumbangan & Roadmap
+## 📚 Dokumentasi

-PR amat dialu-alukan! Kod asas ini sengaja kecil dan mudah dibaca. 🤗
+Untuk panduan terperinci melebihi README ini:

-Lihat [Roadmap Komuniti](https://github.com/sipeed/picoclaw/blob/main/ROADMAP.md) penuh kami.
+| Topik | Penerangan |
+|-------|------------|
+| [Docker & Permulaan Pantas](docs/my/docker.md) | Persediaan Docker Compose, mod Launcher/Agent |
+| [Aplikasi Sembang](docs/my/chat-apps.md) | Panduan persediaan 17+ saluran |
+| [Konfigurasi](docs/my/configuration.md) | Pemboleh ubah persekitaran, susun atur ruang kerja |
+| [Penyedia & Model](docs/providers.md) | 30+ penyedia LLM, penghalaan model |
+| [Spawn & Tugasan Async](docs/my/spawn-tasks.md) | Tugasan pantas, tugasan panjang dengan spawn |
+| [Penyelesaian Masalah](docs/my/troubleshooting.md) | Isu biasa dan penyelesaian |
+| [Konfigurasi Alat](docs/tools_configuration.md) | Aktif/nyahaktif alat, dasar exec, MCP, Kemahiran |
+| [Keserasian Perkakasan](docs/hardware-compatibility.md) | Papan yang diuji, keperluan minimum |
+
+## 🤝 Sumbangan & Peta Jalan
+
+PR dialu-alukan! Kod sumber sengaja dibuat kecil dan mudah dibaca.
+
+Lihat [Peta Jalan Komuniti](https://github.com/sipeed/picoclaw/issues/988) dan [CONTRIBUTING.md](CONTRIBUTING.md) untuk panduan.

 Kumpulan pembangun sedang dibina, sertai selepas PR pertama anda digabungkan!

-Kumpulan pengguna:
+Kumpulan Pengguna:

-discord: <https://discord.gg/V4sAZ9XWpN>
+Discord: <https://discord.gg/V4sAZ9XWpN>

-<img src="assets/wechat.png" alt="PicoClaw" width="512">
+WeChat:
+<img src="assets/wechat.png" alt="Kod QR kumpulan WeChat" width="512">
@@ -56,17 +56,19 @@

 ## 📢 Novidades

+2026-03-25 🚀 **v0.2.4 Lançada!** Reformulação da arquitetura Agent (SubTurn, Hooks, Steering, EventBus), integração WeChat/WeCom, fortalecimento de segurança (.security.yml, filtragem de dados sensíveis), novos providers (AWS Bedrock, Azure, Xiaomi MiMo) e 35 correções de bugs. O PicoClaw atingiu **26K Stars**!
+
 2026-03-17 🚀 **v0.2.3 Lançada!** UI na bandeja do sistema (Windows e Linux), consulta de status de sub-agent (`spawn_status`), hot-reload experimental do Gateway, controle de segurança do Cron e 2 correções de segurança. O PicoClaw atingiu **25K Stars**!

 2026-03-09 🎉 **v0.2.1 — Maior atualização até agora!** Suporte ao protocolo MCP, 4 novos channels (Matrix/IRC/WeCom/Discord Proxy), 3 novos providers (Kimi/Minimax/Avian), pipeline de visão, armazenamento de memória JSONL, roteamento de modelos.

 2026-02-28 📦 **v0.2.0** lançada com suporte a Docker Compose e Web UI Launcher.

-2026-02-26 🎉 O PicoClaw atinge **20K Stars** em apenas 17 dias! Orquestração automática de channels e interfaces de capacidade estão disponíveis.
-
 <details>
 <summary>Notícias anteriores...</summary>

+2026-02-26 🎉 O PicoClaw atinge **20K Stars** em apenas 17 dias! Orquestração automática de channels e interfaces de capacidade estão disponíveis.
+
 2026-02-16 🎉 O PicoClaw ultrapassa 12K Stars em uma semana! Funções de mantenedor da comunidade e [Roadmap](ROADMAP.md) lançados oficialmente.

 2026-02-13 🎉 O PicoClaw ultrapassa 5000 Stars em 4 dias! Roadmap do projeto e grupos de desenvolvedores em andamento.
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — Aviso de segurança no primeiro lançamento</b></summary>
+
+O macOS pode bloquear o `picoclaw-launcher` no primeiro lançamento porque ele foi baixado da internet e não é notarizado pela Mac App Store.
+
+**Passo 1:** Dê um duplo clique em `picoclaw-launcher`. Você verá um aviso de segurança:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Aviso do macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" não foi aberto — A Apple não conseguiu verificar se "picoclaw-launcher" está livre de malware que possa prejudicar seu Mac ou comprometer sua privacidade.*
+
+**Passo 2:** Abra **Configurações do Sistema** → **Privacidade e Segurança** → role até a seção **Segurança** → clique em **Abrir Mesmo Assim** → confirme clicando em **Abrir Mesmo Assim** na caixa de diálogo.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Privacidade e Segurança — Abrir Mesmo Assim" width="600">
+</p>
+
+Após esta etapa única, o `picoclaw-launcher` abrirá normalmente nos lançamentos seguintes.
+
+</details>
+
 ### 💻 TUI Launcher (Recomendado para Headless / SSH)

 O TUI (Terminal UI) Launcher fornece uma interface de terminal completa para configuração e gerenciamento. Ideal para servidores, Raspberry Pi e outros ambientes headless.
@@ -367,6 +392,7 @@ O PicoClaw suporta mais de 30 providers de LLM através da configuração `model
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Obrigatória | Modelos hospedados pela NVIDIA |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Obrigatória | Inferência rápida |
 | [Novita AI](https://novita.ai/) | `novita/` | Obrigatória | Vários modelos abertos |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Obrigatória | Modelos MiMo |
 | [Ollama](https://ollama.com/) | `ollama/` | Não necessária | Modelos locais, self-hosted |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Não necessária | Implantação local, compatível com OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Varia | Proxy para 100+ providers |
@@ -423,9 +449,7 @@ Converse com seu PicoClaw por meio de mais de 17 plataformas de mensagens:
 | **DingTalk** | Médio (credenciais do cliente) | Stream | [Guia](docs/channels/dingtalk/README.pt-br.md) |
 | **Feishu / Lark** | Médio (App ID + Secret) | WebSocket/SDK | [Guia](docs/channels/feishu/README.pt-br.md) |
 | **LINE** | Médio (credenciais + webhook) | Webhook | [Guia](docs/channels/line/README.pt-br.md) |
-| **WeCom Bot** | Médio (webhook URL) | Webhook | [Guia](docs/channels/wecom/wecom_bot/README.pt-br.md) |
-| **WeCom App** | Médio (credenciais corporativas) | Webhook | [Guia](docs/channels/wecom/wecom_app/README.pt-br.md) |
-| **WeCom AI Bot** | Médio (token + chave AES) | WebSocket / Webhook | [Guia](docs/channels/wecom/wecom_aibot/README.pt-br.md) |
+| **WeCom** | Fácil (login QR ou manual) | WebSocket | [Guia](docs/channels/wecom/README.md) |
 | **IRC** | Médio (servidor + nick) | Protocolo IRC | [Guia](docs/pt-br/chat-apps.md#irc) |
 | **OneBot** | Médio (WebSocket URL) | OneBot v11 | [Guia](docs/channels/onebot/README.pt-br.md) |
 | **MaixCam** | Fácil (habilitar) | TCP socket | [Guia](docs/channels/maixcam/README.pt-br.md) |
@@ -56,17 +56,19 @@

 ## 📢 Tin tức

+2026-03-25 🚀 **v0.2.4 đã phát hành!** Tái cấu trúc kiến trúc Agent (SubTurn, Hooks, Steering, EventBus), tích hợp WeChat/WeCom, tăng cường bảo mật (.security.yml, lọc dữ liệu nhạy cảm), provider mới (AWS Bedrock, Azure, Xiaomi MiMo) và 35 bản vá lỗi. PicoClaw đã đạt **26K Stars**!
+
 2026-03-17 🚀 **v0.2.3 đã phát hành!** Giao diện system tray (Windows & Linux), truy vấn trạng thái sub-agent (`spawn_status`), thử nghiệm Gateway hot-reload, bảo mật Cron, và 2 bản vá bảo mật. PicoClaw đã đạt **25K Stars**!

 2026-03-09 🎉 **v0.2.1 — Bản cập nhật lớn nhất từ trước đến nay!** Hỗ trợ giao thức MCP, 4 Channel mới (Matrix/IRC/WeCom/Discord Proxy), 3 Provider mới (Kimi/Minimax/Avian), pipeline thị giác, bộ nhớ JSONL, định tuyến mô hình.

 2026-02-28 📦 **v0.2.0** phát hành với hỗ trợ Docker Compose và Web UI Launcher.

-2026-02-26 🎉 PicoClaw đạt **20K Stars** chỉ trong 17 ngày! Tự động điều phối Channel và giao diện khả năng đã hoạt động.
-
 <details>
 <summary>Tin tức trước đó...</summary>

+2026-02-26 🎉 PicoClaw đạt **20K Stars** chỉ trong 17 ngày! Tự động điều phối Channel và giao diện khả năng đã hoạt động.
+
 2026-02-16 🎉 PicoClaw vượt 12K Stars trong một tuần! Vai trò người duy trì cộng đồng và [Lộ trình](ROADMAP.md) chính thức ra mắt.

 2026-02-13 🎉 PicoClaw vượt 5000 Stars trong 4 ngày! Lộ trình dự án và nhóm nhà phát triển đang được xây dựng.
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — Cảnh báo bảo mật khi khởi chạy lần đầu</b></summary>
+
+macOS có thể chặn `picoclaw-launcher` khi khởi chạy lần đầu vì nó được tải từ internet và chưa được công chứng qua Mac App Store.
+
+**Bước 1:** Nhấp đúp vào `picoclaw-launcher`. Bạn sẽ thấy cảnh báo bảo mật:
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="Cảnh báo macOS Gatekeeper" width="400">
+</p>
+
+> *"picoclaw-launcher" Không Mở Được — Apple không thể xác minh "picoclaw-launcher" không chứa phần mềm độc hại có thể gây hại cho Mac hoặc xâm phạm quyền riêng tư của bạn.*
+
+**Bước 2:** Mở **Cài đặt Hệ thống** → **Quyền riêng tư & Bảo mật** → cuộn xuống phần **Bảo mật** → nhấp **Vẫn Mở** → xác nhận bằng cách nhấp **Vẫn Mở** trong hộp thoại.
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS Quyền riêng tư & Bảo mật — Vẫn Mở" width="600">
+</p>
+
+Sau bước này, `picoclaw-launcher` sẽ mở bình thường trong các lần khởi chạy tiếp theo.
+
+</details>
+
 ### 💻 TUI Launcher (Khuyến nghị cho Headless / SSH)

 TUI (Terminal UI) Launcher cung cấp giao diện terminal đầy đủ tính năng để cấu hình và quản lý. Lý tưởng cho máy chủ, Raspberry Pi và các môi trường headless khác.
@@ -367,6 +392,7 @@ PicoClaw hỗ trợ 30+ Provider LLM thông qua cấu hình `model_list`. Sử d
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | Bắt buộc | Mô hình do NVIDIA lưu trữ |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | Bắt buộc | Suy luận nhanh |
 | [Novita AI](https://novita.ai/) | `novita/` | Bắt buộc | Nhiều mô hình mở |
+| [Xiaomi MiMo](https://platform.xiaomimimo.com/) | `mimo/` | Bắt buộc | Mô hình MiMo |
 | [Ollama](https://ollama.com/) | `ollama/` | Không cần | Mô hình cục bộ, tự lưu trữ |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | Không cần | Triển khai cục bộ, tương thích OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | Tùy | Proxy cho 100+ provider |
@@ -423,9 +449,7 @@ Trò chuyện với PicoClaw của bạn qua 17+ nền tảng nhắn tin:
 | **DingTalk** | Trung bình (client credentials) | Stream | [Hướng dẫn](docs/channels/dingtalk/README.vi.md) |
 | **Feishu / Lark** | Trung bình (App ID + Secret) | WebSocket/SDK | [Hướng dẫn](docs/channels/feishu/README.vi.md) |
 | **LINE** | Trung bình (credentials + webhook) | Webhook | [Hướng dẫn](docs/channels/line/README.vi.md) |
-| **WeCom Bot** | Trung bình (webhook URL) | Webhook | [Hướng dẫn](docs/channels/wecom/wecom_bot/README.vi.md) |
-| **WeCom App** | Trung bình (corp credentials) | Webhook | [Hướng dẫn](docs/channels/wecom/wecom_app/README.vi.md) |
-| **WeCom AI Bot** | Trung bình (token + AES key) | WebSocket / Webhook | [Hướng dẫn](docs/channels/wecom/wecom_aibot/README.vi.md) |
+| **WeCom** | Dễ (đăng nhập QR hoặc thủ công) | WebSocket | [Hướng dẫn](docs/channels/wecom/README.md) |
 | **IRC** | Trung bình (server + nick) | IRC protocol | [Hướng dẫn](docs/vi/chat-apps.md#irc) |
 | **OneBot** | Trung bình (WebSocket URL) | OneBot v11 | [Hướng dẫn](docs/channels/onebot/README.vi.md) |
 | **MaixCam** | Dễ (bật) | TCP socket | [Hướng dẫn](docs/channels/maixcam/README.vi.md) |
@@ -56,17 +56,19 @@

 ## 📢 新闻

+2026-03-25 🚀 **v0.2.4 发布！** Agent 架构全面重构（SubTurn、Hook、Steering、EventBus）、微信/企业微信深度集成、安全体系升级（.security.yml、敏感数据过滤）、新增 Provider（AWS Bedrock、Azure、小米 MiMo），以及 35 项 Bug 修复。PicoClaw 已达 **26K ⭐**！
+
 2026-03-17 🚀 **v0.2.3 发布！** 系统托盘 UI（Windows & Linux）、子 Agent 状态查询 (`spawn_status`)、实验性 Gateway 热重载、Cron 安全门控，以及 2 项安全修复。PicoClaw 已达 **25K ⭐**！

 2026-03-09 🎉 **v0.2.1 — 史上最大更新！** MCP 协议支持、4 个新频道 (Matrix/IRC/WeCom/Discord Proxy)、3 个新 Provider (Kimi/Minimax/Avian)、视觉管线、JSONL 记忆存储、模型路由。

 2026-02-28 📦 **v0.2.0** 发布，支持 Docker Compose 和 Web UI 启动器。

-2026-02-26 🎉 PicoClaw 仅 17 天突破 **20K Stars**！频道自动编排和能力接口上线。
-
 <details>
 <summary>更早的新闻...</summary>

+2026-02-26 🎉 PicoClaw 仅 17 天突破 **20K Stars**！频道自动编排和能力接口上线。
+
 2026-02-16 🎉 PicoClaw 一周内突破 12K Stars！社区维护者角色和 [路线图](ROADMAP.md) 正式发布。

 2026-02-13 🎉 PicoClaw 4 天内突破 5000 Stars！项目路线图和开发者群组筹建中。
@@ -254,6 +256,29 @@ docker compose -f docker/docker-compose.yml --profile launcher up -d

 </details>

+<details>
+<summary><b>macOS — 首次启动安全警告</b></summary>
+
+macOS 可能会在首次启动时拦截 `picoclaw-launcher`，因为它从互联网下载，未经 Mac App Store 公证。
+
+**第一步：** 双击 `picoclaw-launcher`，会出现安全警告：
+
+<p align="center">
+<img src="assets/macos-gatekeeper-warning.jpg" alt="macOS Gatekeeper 警告" width="400">
+</p>
+
+> *"picoclaw-launcher" 无法打开 — Apple 无法验证 "picoclaw-launcher" 不含可能损害 Mac 或危及隐私的恶意软件。*
+
+**第二步：** 打开**系统设置** → **隐私与安全性** → 向下滚动找到**安全性**部分 → 点击**仍要打开** → 在弹窗中再次点击**打开**。
+
+<p align="center">
+<img src="assets/macos-gatekeeper-allow.jpg" alt="macOS 隐私与安全性 — 仍要打开" width="600">
+</p>
+
+完成这一次操作后，后续启动 `picoclaw-launcher` 将不再弹出警告。
+
+</details>
+
 ### 💻 TUI Launcher（推荐无头环境 / SSH）

 TUI（终端 UI）Launcher 提供功能完整的终端配置与管理界面，适合服务器、树莓派等无显示器环境。
@@ -367,6 +392,7 @@ PicoClaw 通过 `model_list` 配置支持 30+ LLM Provider，使用 `协议/模
 | [NVIDIA NIM](https://build.nvidia.com/) | `nvidia/` | 必填 | NVIDIA 托管模型 |
 | [Cerebras](https://cloud.cerebras.ai/) | `cerebras/` | 必填 | 快速推理 |
 | [Novita AI](https://novita.ai/) | `novita/` | 必填 | 多种开源模型 |
+| [小米 MiMo](https://platform.xiaomimimo.com/) | `mimo/` | 必填 | MiMo 系列模型 |
 | [Ollama](https://ollama.com/) | `ollama/` | 无需 | 本地模型，自托管 |
 | [vLLM](https://docs.vllm.ai/) | `vllm/` | 无需 | 本地部署，兼容 OpenAI |
 | [LiteLLM](https://docs.litellm.ai/) | `litellm/` | 视情况 | 100+ Provider 代理 |
@@ -423,9 +449,7 @@ PicoClaw 通过 `model_list` 配置支持 30+ LLM Provider，使用 `协议/模
 | **钉钉** | 中等（client credentials） | Stream | [指南](docs/channels/dingtalk/README.zh.md) |
 | **飞书 / Lark** | 中等（App ID + Secret） | WebSocket/SDK | [指南](docs/channels/feishu/README.zh.md) |
 | **LINE** | 中等（credentials + webhook） | Webhook | [指南](docs/channels/line/README.zh.md) |
-| **企业微信机器人** | 中等（webhook URL） | Webhook | [指南](docs/channels/wecom/wecom_bot/README.zh.md) |
-| **企业微信应用** | 中等（corp credentials） | Webhook | [指南](docs/channels/wecom/wecom_app/README.zh.md) |
-| **企业微信 AI 机器人** | 中等（token + AES key） | WebSocket / Webhook | [指南](docs/channels/wecom/wecom_aibot/README.zh.md) |
+| **企业微信** | 简单（扫码登录或手动配置） | WebSocket | [指南](docs/channels/wecom/README.zh.md) |
 | **IRC** | 中等（server + nick） | IRC 协议 | [指南](docs/zh/chat-apps.md#irc) |
 | **OneBot** | 中等（WebSocket URL） | OneBot v11 | [指南](docs/channels/onebot/README.zh.md) |
 | **MaixCam** | 简单（启用即可） | TCP socket | [指南](docs/channels/maixcam/README.zh.md) |
@@ -0,0 +1,148 @@
+> Retour au [README](../../../README.fr.md)
+
+# WeCom
+
+PicoClaw expose WeCom en tant que canal unique `channels.wecom`, basé sur l'API WebSocket officielle WeCom AI Bot.
+Ce canal remplace l'ancienne séparation `wecom`, `wecom_app` et `wecom_aibot` par un modèle de configuration unifié.
+
+> Aucune URL de callback webhook publique n'est requise. PicoClaw établit une connexion WebSocket sortante vers WeCom.
+
+## Fonctionnalités prises en charge
+
+- Chat privé et chat de groupe
+- Réponses en streaming côté canal via le protocole WeCom AI Bot
+- Messages entrants : texte, voix, image, fichier, vidéo et messages mixtes
+- Réponses sortantes : texte et médias (`image`, `file`, `voice`, `video`)
+- Onboarding par QR code via l'interface Web ou le CLI
+- Liste blanche partagée et routage `reasoning_channel_id`
+
+---
+
+## Démarrage rapide
+
+### Option 1 : Liaison QR via l'interface Web (recommandé)
+
+Ouvrez l'interface Web, accédez à **Channels → WeCom** et cliquez sur le bouton de liaison QR. Scannez le QR code avec WeCom et confirmez dans l'application — les identifiants sont enregistrés automatiquement.
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="Liaison QR WeCom dans l'interface Web" width="600">
+</p>
+
+### Option 2 : Connexion QR via le CLI
+
+Exécutez :
+
+```bash
+picoclaw auth wecom
+```
+
+La commande :
+1. Demande un QR code à WeCom et l'affiche dans le terminal
+2. Affiche également un **lien QR code** que vous pouvez ouvrir dans un navigateur si le QR du terminal est difficile à scanner
+3. Attend la confirmation — après le scan, vous devez également **confirmer la connexion dans l'application WeCom**
+4. En cas de succès, écrit `bot_id` et `secret` dans `channels.wecom` et sauvegarde la configuration
+
+Le délai d'expiration par défaut est de **5 minutes**. Utilisez `--timeout` pour l'étendre :
+
+```bash
+picoclaw auth wecom --timeout 10m
+```
+
+> ⚠️ Scanner le QR code ne suffit pas — vous devez également appuyer sur **Confirmer** dans l'application WeCom, sinon la commande expirera.
+
+### Option 3 : Configuration manuelle
+
+Si vous disposez déjà d'un `bot_id` et d'un `secret` depuis la plateforme WeCom AI Bot, configurez directement :
+
+```json
+{
+  "channels": {
+    "wecom": {
+      "enabled": true,
+      "bot_id": "YOUR_BOT_ID",
+      "secret": "YOUR_SECRET",
+      "websocket_url": "wss://openws.work.weixin.qq.com",
+      "send_thinking_message": true,
+      "allow_from": [],
+      "reasoning_channel_id": ""
+    }
+  }
+}
+```
+
+---
+
+## Configuration
+
+| Champ | Type | Défaut | Description |
+| ----- | ---- | ------ | ----------- |
+| `enabled` | bool | `false` | Activer le canal WeCom. |
+| `bot_id` | string | — | Identifiant WeCom AI Bot. Requis lorsque le canal est activé. |
+| `secret` | string | — | Secret WeCom AI Bot. Stocké chiffré dans `.security.yml`. Requis lorsque le canal est activé. |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | Point de terminaison WebSocket WeCom. |
+| `send_thinking_message` | bool | `true` | Envoyer un message `Processing...` avant le début de la réponse en streaming. |
+| `allow_from` | array | `[]` | Liste blanche des expéditeurs. Vide signifie autoriser tous les expéditeurs. |
+| `reasoning_channel_id` | string | `""` | ID de chat optionnel pour router la sortie de raisonnement vers une conversation séparée. |
+
+### Variables d'environnement
+
+Tous les champs peuvent être remplacés par des variables d'environnement avec le préfixe `PICOCLAW_CHANNELS_WECOM_` :
+
+| Variable d'environnement | Champ correspondant |
+| ------------------------ | ------------------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---
+
+## Comportement à l'exécution
+
+- PicoClaw maintient un tour WeCom actif pour que les réponses en streaming puissent continuer sur le même flux lorsque c'est possible.
+- Les réponses en streaming ont une durée maximale de **5,5 minutes** et un intervalle d'envoi minimum de **500 ms**.
+- Si le streaming n'est plus disponible, les réponses basculent vers la livraison par push actif.
+- Les associations de routes de chat expirent après **30 minutes** d'inactivité.
+- Les médias entrants sont téléchargés dans le stockage média local avant d'être transmis à l'agent.
+- Les médias sortants sont uploadés vers WeCom en tant que fichier temporaire, puis envoyés comme message média.
+- Les messages en double sont détectés et supprimés (tampon circulaire des 1000 derniers identifiants de messages).
+
+---
+
+## Migration depuis l'ancienne configuration WeCom
+
+| Configuration précédente | Migration |
+| ------------------------ | --------- |
+| `channels.wecom` (bot webhook) | Remplacer par `channels.wecom` avec `bot_id` + `secret`. |
+| `channels.wecom_app` | Supprimer. Utiliser `channels.wecom` à la place. |
+| `channels.wecom_aibot` | Déplacer `bot_id` et `secret` vers `channels.wecom`. |
+| `token`, `encoding_aes_key`, `webhook_url`, `webhook_path` | Plus utilisés. Supprimer de la configuration. |
+| `corp_id`, `corp_secret`, `agent_id` | Plus utilisés. Supprimer de la configuration. |
+| `welcome_message`, `processing_message`, `max_steps` | Ne font plus partie de la configuration du canal WeCom. |
+
+---
+
+## Dépannage
+
+### La liaison QR expire
+
+- Après avoir scanné le QR code, vous devez également **confirmer la connexion dans l'application WeCom**. Le scan seul ne suffit pas.
+- Relancez avec un `--timeout` plus long : `picoclaw auth wecom --timeout 10m`
+- Si le QR code dans le terminal est difficile à scanner, utilisez le **lien QR code** affiché en dessous pour l'ouvrir dans un navigateur.
+
+### QR code expiré
+
+- Le QR code a une durée de validité limitée. Relancez `picoclaw auth wecom` pour en obtenir un nouveau.
+
+### Échec de la connexion WebSocket
+
+- Vérifiez que `bot_id` et `secret` sont corrects.
+- Confirmez que l'hôte peut atteindre `wss://openws.work.weixin.qq.com` (WebSocket sortant, aucun port entrant nécessaire).
+
+### Les réponses n'arrivent pas
+
+- Vérifiez si `allow_from` bloque l'expéditeur.
+- Vérifiez que `channels.wecom.bot_id` et `channels.wecom.secret` sont définis et non vides.
@@ -0,0 +1,148 @@
+> [README](../../../README.ja.md) に戻る
+
+# WeCom
+
+PicoClaw は WeCom を公式 WeCom AI Bot WebSocket API に基づく単一の `channels.wecom` チャンネルとして公開します。
+従来の `wecom`、`wecom_app`、`wecom_aibot` の分割を統一された設定モデルに置き換えました。
+
+> パブリックな Webhook コールバック URL は不要です。PicoClaw は WeCom へのアウトバウンド WebSocket 接続を確立します。
+
+## サポートされる機能
+
+- ダイレクトチャットとグループチャット
+- WeCom AI Bot プロトコルによるチャンネル側ストリーミング返信
+- テキスト、音声、画像、ファイル、動画、ミックスメッセージの受信
+- テキストおよびメディア返信の送信（`image`、`file`、`voice`、`video`）
+- Web UI または CLI による QR コードオンボーディング
+- 共有許可リストと `reasoning_channel_id` ルーティング
+
+---
+
+## クイックスタート
+
+### オプション 1：Web UI QR バインディング（推奨）
+
+Web UI を開き、**Channels → WeCom** に移動して、QR バインディングボタンをクリックします。WeCom で QR コードをスキャンし、アプリ内で確認すると、認証情報が自動的に保存されます。
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="Web UI での WeCom QR バインディング" width="600">
+</p>
+
+### オプション 2：CLI QR ログイン
+
+実行：
+
+```bash
+picoclaw auth wecom
+```
+
+コマンドの動作：
+1. WeCom に QR コードをリクエストし、ターミナルに表示します
+2. ターミナルの QR コードがスキャンしにくい場合に備え、ブラウザで開ける **QR コードリンク** も表示します
+3. 確認をポーリングします — スキャン後、**WeCom アプリ内でログインを確認** する必要があります
+4. 成功すると、`bot_id` と `secret` を `channels.wecom` に書き込み、設定を保存します
+
+デフォルトのタイムアウトは **5 分** です。`--timeout` で延長できます：
+
+```bash
+picoclaw auth wecom --timeout 10m
+```
+
+> ⚠️ QR コードのスキャンだけでは不十分です — WeCom アプリ内で **確認** をタップする必要があります。そうしないとコマンドがタイムアウトします。
+
+### オプション 3：手動設定
+
+WeCom AI Bot プラットフォームから `bot_id` と `secret` を既にお持ちの場合、直接設定できます：
+
+```json
+{
+  "channels": {
+    "wecom": {
+      "enabled": true,
+      "bot_id": "YOUR_BOT_ID",
+      "secret": "YOUR_SECRET",
+      "websocket_url": "wss://openws.work.weixin.qq.com",
+      "send_thinking_message": true,
+      "allow_from": [],
+      "reasoning_channel_id": ""
+    }
+  }
+}
+```
+
+---
+
+## 設定
+
+| フィールド | 型 | デフォルト | 説明 |
+| ---------- | -- | ---------- | ---- |
+| `enabled` | bool | `false` | WeCom チャンネルを有効にする。 |
+| `bot_id` | string | — | WeCom AI Bot 識別子。有効時に必須。 |
+| `secret` | string | — | WeCom AI Bot シークレット。`.security.yml` に暗号化して保存。有効時に必須。 |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | WeCom WebSocket エンドポイント。 |
+| `send_thinking_message` | bool | `true` | ストリーミング返信の開始前に `Processing...` メッセージを送信する。 |
+| `allow_from` | array | `[]` | 送信者許可リスト。空の場合はすべての送信者を許可。 |
+| `reasoning_channel_id` | string | `""` | 推論・思考出力を別の会話にルーティングするためのオプションのチャット ID。 |
+
+### 環境変数
+
+すべてのフィールドは `PICOCLAW_CHANNELS_WECOM_` プレフィックスの環境変数で上書きできます：
+
+| 環境変数 | 対応フィールド |
+| -------- | -------------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---
+
+## ランタイム動作
+
+- PicoClaw はアクティブな WeCom ターンを維持し、可能な限り同じストリームでストリーミング返信を継続します。
+- ストリーミング返信の最大持続時間は **5.5 分**、最小送信間隔は **500ms** です。
+- ストリーミングが利用できなくなった場合、返信はアクティブプッシュ配信にフォールバックします。
+- チャットルートの関連付けは **30 分** の非アクティブ後に期限切れになります。
+- 受信メディアはエージェントに渡される前にローカルメディアストアにダウンロードされます。
+- 送信メディアは WeCom に一時ファイルとしてアップロードされ、メディアメッセージとして送信されます。
+- 重複メッセージは検出され抑制されます（最新 1000 件のメッセージ ID のリングバッファ）。
+
+---
+
+## レガシー WeCom 設定からの移行
+
+| 以前の設定 | 移行方法 |
+| ---------- | -------- |
+| `channels.wecom`（Webhook ボット） | `bot_id` + `secret` を使用する `channels.wecom` に置き換える。 |
+| `channels.wecom_app` | 削除して `channels.wecom` を使用する。 |
+| `channels.wecom_aibot` | `bot_id` と `secret` を `channels.wecom` に移動する。 |
+| `token`、`encoding_aes_key`、`webhook_url`、`webhook_path` | 使用されなくなりました。設定から削除してください。 |
+| `corp_id`、`corp_secret`、`agent_id` | 使用されなくなりました。設定から削除してください。 |
+| `welcome_message`、`processing_message`、`max_steps` | WeCom チャンネル設定の一部ではなくなりました。 |
+
+---
+
+## トラブルシューティング
+
+### QR バインディングがタイムアウトする
+
+- QR コードをスキャンした後、**WeCom アプリ内でログインを確認** する必要があります。スキャンだけでは不十分です。
+- より長い `--timeout` で再実行してください：`picoclaw auth wecom --timeout 10m`
+- ターミナルの QR コードがスキャンしにくい場合は、その下に表示される **QR コードリンク** を使用してブラウザで開いてください。
+
+### QR コードの有効期限切れ
+
+- QR コードには有効期限があります。`picoclaw auth wecom` を再実行して新しいものを取得してください。
+
+### WebSocket 接続の失敗
+
+- `bot_id` と `secret` が正しいことを確認してください。
+- ホストが `wss://openws.work.weixin.qq.com` に到達できることを確認してください（アウトバウンド WebSocket、インバウンドポートは不要）。
+
+### 返信が届かない
+
+- `allow_from` が送信者をブロックしていないか確認してください。
+- `channels.wecom.bot_id` と `channels.wecom.secret` が設定されており、空でないことを確認してください。
@@ -2,8 +2,10 @@

 # WeCom

-PicoClaw now exposes WeCom as a single `channels.wecom` channel built on the official WeCom AI Bot WebSocket API.
-This replaces the legacy `wecom`, `wecom_app`, and `wecom_aibot` split with one configuration model.
+PicoClaw exposes WeCom as a single `channels.wecom` channel built on the official WeCom AI Bot WebSocket API.
+This replaces the legacy `wecom`, `wecom_app`, and `wecom_aibot` split with one unified configuration model.
+
+> No public webhook callback URL is required. PicoClaw opens an outbound WebSocket connection to WeCom.

 ## What This Channel Supports

@@ -11,14 +13,22 @@ This replaces the legacy `wecom`, `wecom_app`, and `wecom_aibot` split with one
 - Channel-side streaming replies over WeCom's AI Bot protocol
 - Incoming text, voice, image, file, video, and mixed messages
 - Outbound text and media replies (`image`, `file`, `voice`, `video`)
- QR-based CLI onboarding with `picoclaw auth wecom`
+- QR-based onboarding via Web UI or CLI
 - Shared allowlist and `reasoning_channel_id` routing

-> No public webhook callback URL is required for this channel. PicoClaw opens an outbound WebSocket connection to WeCom.
+---

 ## Quick Start

-### Option 1: QR Login From CLI
+### Option 1: Web UI QR Binding (Recommended)
+
+Open the Web UI, navigate to **Channels → WeCom**, and click the QR binding button. Scan the QR code with WeCom and confirm in the app — credentials are saved automatically.
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="WeCom QR binding in Web UI" width="600">
+</p>
+
+### Option 2: CLI QR Login

 Run:

@@ -26,16 +36,23 @@ Run:
 picoclaw auth wecom
 ```

-The command prints a QR code in the terminal, waits for confirmation in WeCom, and then writes the resulting
-`bot_id` and `secret` into `channels.wecom`.
+The command:
+1. Requests a QR code from WeCom and prints it in the terminal
+2. Also prints a **QR Code Link** you can open in a browser if the terminal QR is hard to scan
+3. Polls for confirmation — after scanning, you must also **confirm the login inside the WeCom app**
+4. On success, writes `bot_id` and `secret` into `channels.wecom` and saves the config

-Use `--timeout` if you want to wait longer:
+The default timeout is **5 minutes**. Use `--timeout` to extend it:

 ```bash
 picoclaw auth wecom --timeout 10m
 ```

-### Option 2: Configure Manually
+> ⚠️ Scanning the QR code is not enough — you must also tap **Confirm** inside the WeCom app, otherwise the command will time out.
+
+### Option 3: Configure Manually
+
+If you already have a `bot_id` and `secret` from the WeCom AI Bot platform, configure directly:

 ```json
 {
@@ -53,52 +70,79 @@ picoclaw auth wecom --timeout 10m
 }
 ```

+---
+
 ## Configuration

-| Field | Type | Required | Description |
-| ----- | ---- | -------- | ----------- |
-| `enabled` | bool | No | Enables the WeCom channel. |
-| `bot_id` | string | Yes | WeCom AI Bot identifier. Required when the channel is enabled. |
-| `secret` | string | Yes | WeCom AI Bot secret. Required when the channel is enabled. |
-| `websocket_url` | string | No | WebSocket endpoint. Defaults to `wss://openws.work.weixin.qq.com`. |
-| `send_thinking_message` | bool | No | Sends an initial `Processing...` chunk before the final streamed reply. Defaults to `true`. |
-| `allow_from` | array | No | Sender allowlist. Empty means allow all senders. |
-| `reasoning_channel_id` | string | No | Optional destination for reasoning/thinking output. |
+| Field | Type | Default | Description |
+| ----- | ---- | ------- | ----------- |
+| `enabled` | bool | `false` | Enable the WeCom channel. |
+| `bot_id` | string | — | WeCom AI Bot identifier. Required when enabled. |
+| `secret` | string | — | WeCom AI Bot secret. Stored encrypted in `.security.yml`. Required when enabled. |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | WeCom WebSocket endpoint. |
+| `send_thinking_message` | bool | `true` | Send a `Processing...` message before the streamed reply begins. |
+| `allow_from` | array | `[]` | Sender allowlist. Empty means allow all senders. |
+| `reasoning_channel_id` | string | `""` | Optional chat ID to route reasoning/thinking output to a separate conversation. |
+
+### Environment Variables
+
+All fields can be overridden via environment variables with the prefix `PICOCLAW_CHANNELS_WECOM_`:
+
+| Environment Variable | Corresponding Field |
+| -------------------- | ------------------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---

 ## Runtime Behavior

- PicoClaw keeps the active WeCom turn so normal replies can continue the same stream when possible.
- If streaming is no longer available, replies fall back to active push delivery to the resolved chat route.
- Incoming media is downloaded into the media store before being handed to the agent.
- Outbound media is uploaded to WeCom in temporary chunks and then sent as a regular media message.
+- PicoClaw maintains an active WeCom turn so streaming replies can continue on the same stream when possible.
+- Streaming replies have a maximum duration of **5.5 minutes** and a minimum send interval of **500ms**.
+- If streaming is no longer available, replies fall back to active push delivery.
+- Chat route associations expire after **30 minutes** of inactivity.
+- Incoming media is downloaded into the local media store before being passed to the agent.
+- Outbound media is uploaded to WeCom as a temporary file and then sent as a media message.
+- Duplicate messages are detected and suppressed (ring buffer of last 1000 message IDs).

-## Migration Notes
+---

-This branch removes the old multi-channel WeCom model.
+## Migration from Legacy WeCom Config

-| Previous config | Now |
-| --------------- | --- |
-| `channels.wecom` webhook bot | Replace with `channels.wecom` using `bot_id` + `secret`. |
-| `channels.wecom_app` | Remove it and use `channels.wecom`. |
-| `channels.wecom_aibot` | Move the config to `channels.wecom`. |
-| `token`, `encoding_aes_key`, `webhook_url`, `webhook_path` | No longer used by the WeCom channel. |
-| `corp_id`, `corp_secret`, `agent_id` | No longer used by the WeCom channel. |
-| `welcome_message`, `processing_message`, `max_steps` under WeCom | No longer part of the WeCom channel config. |
+| Previous config | Migration |
+| --------------- | --------- |
+| `channels.wecom` (webhook bot) | Replace with `channels.wecom` using `bot_id` + `secret`. |
+| `channels.wecom_app` | Remove. Use `channels.wecom` instead. |
+| `channels.wecom_aibot` | Move `bot_id` and `secret` to `channels.wecom`. |
+| `token`, `encoding_aes_key`, `webhook_url`, `webhook_path` | No longer used. Remove from config. |
+| `corp_id`, `corp_secret`, `agent_id` | No longer used. Remove from config. |
+| `welcome_message`, `processing_message`, `max_steps` | No longer part of the WeCom channel config. |
+
+---

 ## Troubleshooting

-### `picoclaw auth wecom` times out
+### QR binding times out

- Re-run with a larger `--timeout`.
- Make sure the QR code was confirmed inside WeCom, not only scanned.
+- After scanning the QR code, you must also **confirm the login inside the WeCom app**. Scanning alone is not enough.
+- Re-run with a larger `--timeout`: `picoclaw auth wecom --timeout 10m`
+- If the QR code in the terminal is hard to scan, use the **QR Code Link** printed below it to open in a browser.
+
+### QR code expired
+
+- The QR code has a limited validity. Re-run `picoclaw auth wecom` to get a fresh one.

 ### WebSocket connection fails

- Verify `bot_id` and `secret`.
- Confirm the host can reach `wss://openws.work.weixin.qq.com`.
+- Verify `bot_id` and `secret` are correct.
+- Confirm the host can reach `wss://openws.work.weixin.qq.com` (outbound WebSocket, no inbound port needed).

 ### Replies do not arrive

- Check whether `allow_from` blocks the sender.
- Check launcher or startup validation for missing `channels.wecom.bot_id` / `channels.wecom.secret`.
-
+- Check whether `allow_from` is blocking the sender.
+- Check that `channels.wecom.bot_id` and `channels.wecom.secret` are set and non-empty.
@@ -0,0 +1,148 @@
+> Voltar ao [README](../../../README.pt-br.md)
+
+# WeCom
+
+O PicoClaw expõe o WeCom como um único canal `channels.wecom`, construído sobre a API WebSocket oficial do WeCom AI Bot.
+Isso substitui a antiga separação `wecom`, `wecom_app` e `wecom_aibot` por um modelo de configuração unificado.
+
+> Nenhuma URL de callback webhook pública é necessária. O PicoClaw estabelece uma conexão WebSocket de saída para o WeCom.
+
+## Funcionalidades Suportadas
+
+- Chat direto e chat em grupo
+- Respostas em streaming pelo protocolo WeCom AI Bot
+- Mensagens recebidas: texto, voz, imagem, arquivo, vídeo e mensagens mistas
+- Respostas enviadas: texto e mídia (`image`, `file`, `voice`, `video`)
+- Onboarding por QR code via Web UI ou CLI
+- Lista de permissões compartilhada e roteamento `reasoning_channel_id`
+
+---
+
+## Início Rápido
+
+### Opção 1: Vinculação QR via Web UI (Recomendado)
+
+Abra a Web UI, navegue até **Channels → WeCom** e clique no botão de vinculação QR. Escaneie o QR code com o WeCom e confirme no aplicativo — as credenciais são salvas automaticamente.
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="Vinculação QR do WeCom na Web UI" width="600">
+</p>
+
+### Opção 2: Login QR via CLI
+
+Execute:
+
+```bash
+picoclaw auth wecom
+```
+
+O comando:
+1. Solicita um QR code ao WeCom e o exibe no terminal
+2. Também exibe um **Link do QR Code** que você pode abrir no navegador se o QR do terminal for difícil de escanear
+3. Aguarda a confirmação — após escanear, você também deve **confirmar o login dentro do aplicativo WeCom**
+4. Em caso de sucesso, grava `bot_id` e `secret` em `channels.wecom` e salva a configuração
+
+O timeout padrão é de **5 minutos**. Use `--timeout` para estendê-lo:
+
+```bash
+picoclaw auth wecom --timeout 10m
+```
+
+> ⚠️ Escanear o QR code não é suficiente — você também deve tocar em **Confirmar** dentro do aplicativo WeCom, caso contrário o comando expirará.
+
+### Opção 3: Configuração Manual
+
+Se você já possui um `bot_id` e `secret` da plataforma WeCom AI Bot, configure diretamente:
+
+```json
+{
+  "channels": {
+    "wecom": {
+      "enabled": true,
+      "bot_id": "YOUR_BOT_ID",
+      "secret": "YOUR_SECRET",
+      "websocket_url": "wss://openws.work.weixin.qq.com",
+      "send_thinking_message": true,
+      "allow_from": [],
+      "reasoning_channel_id": ""
+    }
+  }
+}
+```
+
+---
+
+## Configuração
+
+| Campo | Tipo | Padrão | Descrição |
+| ----- | ---- | ------ | --------- |
+| `enabled` | bool | `false` | Ativar o canal WeCom. |
+| `bot_id` | string | — | Identificador do WeCom AI Bot. Obrigatório quando ativado. |
+| `secret` | string | — | Secret do WeCom AI Bot. Armazenado criptografado em `.security.yml`. Obrigatório quando ativado. |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | Endpoint WebSocket do WeCom. |
+| `send_thinking_message` | bool | `true` | Enviar uma mensagem `Processing...` antes do início da resposta em streaming. |
+| `allow_from` | array | `[]` | Lista de permissões de remetentes. Vazio significa permitir todos os remetentes. |
+| `reasoning_channel_id` | string | `""` | ID de chat opcional para rotear a saída de raciocínio para uma conversa separada. |
+
+### Variáveis de Ambiente
+
+Todos os campos podem ser substituídos via variáveis de ambiente com o prefixo `PICOCLAW_CHANNELS_WECOM_`:
+
+| Variável de Ambiente | Campo Correspondente |
+| -------------------- | -------------------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---
+
+## Comportamento em Tempo de Execução
+
+- O PicoClaw mantém um turno WeCom ativo para que as respostas em streaming possam continuar no mesmo fluxo quando possível.
+- As respostas em streaming têm uma duração máxima de **5,5 minutos** e um intervalo mínimo de envio de **500ms**.
+- Se o streaming não estiver mais disponível, as respostas recorrem à entrega por push ativo.
+- As associações de rotas de chat expiram após **30 minutos** de inatividade.
+- A mídia recebida é baixada para o armazenamento de mídia local antes de ser passada ao agente.
+- A mídia enviada é carregada para o WeCom como um arquivo temporário e então enviada como uma mensagem de mídia.
+- Mensagens duplicadas são detectadas e suprimidas (buffer circular dos últimos 1000 IDs de mensagens).
+
+---
+
+## Migração da Configuração Legada do WeCom
+
+| Configuração anterior | Migração |
+| --------------------- | -------- |
+| `channels.wecom` (bot webhook) | Substituir por `channels.wecom` usando `bot_id` + `secret`. |
+| `channels.wecom_app` | Remover. Usar `channels.wecom` no lugar. |
+| `channels.wecom_aibot` | Mover `bot_id` e `secret` para `channels.wecom`. |
+| `token`, `encoding_aes_key`, `webhook_url`, `webhook_path` | Não mais utilizados. Remover da configuração. |
+| `corp_id`, `corp_secret`, `agent_id` | Não mais utilizados. Remover da configuração. |
+| `welcome_message`, `processing_message`, `max_steps` | Não fazem mais parte da configuração do canal WeCom. |
+
+---
+
+## Solução de Problemas
+
+### A vinculação QR expira
+
+- Após escanear o QR code, você também deve **confirmar o login dentro do aplicativo WeCom**. Escanear sozinho não é suficiente.
+- Execute novamente com um `--timeout` maior: `picoclaw auth wecom --timeout 10m`
+- Se o QR code no terminal for difícil de escanear, use o **Link do QR Code** exibido abaixo dele para abrir no navegador.
+
+### QR code expirado
+
+- O QR code tem validade limitada. Execute novamente `picoclaw auth wecom` para obter um novo.
+
+### Falha na conexão WebSocket
+
+- Verifique se `bot_id` e `secret` estão corretos.
+- Confirme que o host pode alcançar `wss://openws.work.weixin.qq.com` (WebSocket de saída, nenhuma porta de entrada necessária).
+
+### As respostas não chegam
+
+- Verifique se `allow_from` está bloqueando o remetente.
+- Verifique se `channels.wecom.bot_id` e `channels.wecom.secret` estão definidos e não vazios.
@@ -0,0 +1,148 @@
+> Quay lại [README](../../../README.vi.md)
+
+# WeCom
+
+PicoClaw cung cấp WeCom dưới dạng một kênh duy nhất `channels.wecom`, được xây dựng trên API WebSocket chính thức của WeCom AI Bot.
+Điều này thay thế việc phân tách cũ `wecom`, `wecom_app` và `wecom_aibot` bằng một mô hình cấu hình thống nhất.
+
+> Không cần URL callback webhook công khai. PicoClaw thiết lập kết nối WebSocket đi ra tới WeCom.
+
+## Tính năng được hỗ trợ
+
+- Chat trực tiếp và chat nhóm
+- Phản hồi streaming qua giao thức WeCom AI Bot
+- Nhận tin nhắn văn bản, giọng nói, hình ảnh, tệp, video và tin nhắn hỗn hợp
+- Gửi phản hồi văn bản và phương tiện (`image`, `file`, `voice`, `video`)
+- Đăng ký qua mã QR bằng Web UI hoặc CLI
+- Danh sách cho phép chung và định tuyến `reasoning_channel_id`
+
+---
+
+## Bắt đầu nhanh
+
+### Tùy chọn 1: Liên kết QR qua Web UI (Khuyến nghị)
+
+Mở Web UI, điều hướng đến **Channels → WeCom** và nhấp vào nút liên kết QR. Quét mã QR bằng WeCom và xác nhận trong ứng dụng — thông tin đăng nhập được lưu tự động.
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="Liên kết QR WeCom trong Web UI" width="600">
+</p>
+
+### Tùy chọn 2: Đăng nhập QR qua CLI
+
+Chạy:
+
+```bash
+picoclaw auth wecom
+```
+
+Lệnh thực hiện:
+1. Yêu cầu mã QR từ WeCom và hiển thị trong terminal
+2. Đồng thời in ra một **Liên kết mã QR** mà bạn có thể mở trong trình duyệt nếu mã QR trên terminal khó quét
+3. Chờ xác nhận — sau khi quét, bạn cũng phải **xác nhận đăng nhập trong ứng dụng WeCom**
+4. Khi thành công, ghi `bot_id` và `secret` vào `channels.wecom` và lưu cấu hình
+
+Thời gian chờ mặc định là **5 phút**. Sử dụng `--timeout` để kéo dài:
+
+```bash
+picoclaw auth wecom --timeout 10m
+```
+
+> ⚠️ Quét mã QR là chưa đủ — bạn cũng phải nhấn **Xác nhận** trong ứng dụng WeCom, nếu không lệnh sẽ hết thời gian chờ.
+
+### Tùy chọn 3: Cấu hình thủ công
+
+Nếu bạn đã có `bot_id` và `secret` từ nền tảng WeCom AI Bot, hãy cấu hình trực tiếp:
+
+```json
+{
+  "channels": {
+    "wecom": {
+      "enabled": true,
+      "bot_id": "YOUR_BOT_ID",
+      "secret": "YOUR_SECRET",
+      "websocket_url": "wss://openws.work.weixin.qq.com",
+      "send_thinking_message": true,
+      "allow_from": [],
+      "reasoning_channel_id": ""
+    }
+  }
+}
+```
+
+---
+
+## Cấu hình
+
+| Trường | Kiểu | Mặc định | Mô tả |
+| ------ | ---- | -------- | ----- |
+| `enabled` | bool | `false` | Kích hoạt kênh WeCom. |
+| `bot_id` | string | — | Mã định danh WeCom AI Bot. Bắt buộc khi được kích hoạt. |
+| `secret` | string | — | Secret của WeCom AI Bot. Được lưu mã hóa trong `.security.yml`. Bắt buộc khi được kích hoạt. |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | Điểm cuối WebSocket của WeCom. |
+| `send_thinking_message` | bool | `true` | Gửi tin nhắn `Processing...` trước khi phản hồi streaming bắt đầu. |
+| `allow_from` | array | `[]` | Danh sách cho phép người gửi. Để trống nghĩa là cho phép tất cả. |
+| `reasoning_channel_id` | string | `""` | ID chat tùy chọn để định tuyến đầu ra suy luận đến một cuộc hội thoại riêng. |
+
+### Biến môi trường
+
+Tất cả các trường có thể được ghi đè bằng biến môi trường với tiền tố `PICOCLAW_CHANNELS_WECOM_`:
+
+| Biến môi trường | Trường tương ứng |
+| ---------------- | ---------------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---
+
+## Hành vi khi chạy
+
+- PicoClaw duy trì một lượt WeCom đang hoạt động để phản hồi streaming có thể tiếp tục trên cùng một luồng khi có thể.
+- Phản hồi streaming có thời lượng tối đa **5,5 phút** và khoảng cách gửi tối thiểu **500ms**.
+- Nếu streaming không còn khả dụng, phản hồi sẽ chuyển sang gửi push chủ động.
+- Các liên kết tuyến chat hết hạn sau **30 phút** không hoạt động.
+- Phương tiện nhận được sẽ được tải xuống bộ lưu trữ phương tiện cục bộ trước khi chuyển cho agent.
+- Phương tiện gửi đi được tải lên WeCom dưới dạng tệp tạm thời, sau đó gửi dưới dạng tin nhắn phương tiện.
+- Tin nhắn trùng lặp được phát hiện và loại bỏ (bộ đệm vòng của 1000 ID tin nhắn gần nhất).
+
+---
+
+## Di chuyển từ cấu hình WeCom cũ
+
+| Cấu hình trước đây | Di chuyển |
+| ------------------- | --------- |
+| `channels.wecom` (bot webhook) | Thay thế bằng `channels.wecom` sử dụng `bot_id` + `secret`. |
+| `channels.wecom_app` | Xóa. Sử dụng `channels.wecom` thay thế. |
+| `channels.wecom_aibot` | Di chuyển `bot_id` và `secret` sang `channels.wecom`. |
+| `token`, `encoding_aes_key`, `webhook_url`, `webhook_path` | Không còn sử dụng. Xóa khỏi cấu hình. |
+| `corp_id`, `corp_secret`, `agent_id` | Không còn sử dụng. Xóa khỏi cấu hình. |
+| `welcome_message`, `processing_message`, `max_steps` | Không còn là một phần của cấu hình kênh WeCom. |
+
+---
+
+## Khắc phục sự cố
+
+### Liên kết QR hết thời gian chờ
+
+- Sau khi quét mã QR, bạn cũng phải **xác nhận đăng nhập trong ứng dụng WeCom**. Chỉ quét là chưa đủ.
+- Chạy lại với `--timeout` lớn hơn: `picoclaw auth wecom --timeout 10m`
+- Nếu mã QR trên terminal khó quét, hãy sử dụng **Liên kết mã QR** được in bên dưới để mở trong trình duyệt.
+
+### Mã QR đã hết hạn
+
+- Mã QR có thời hạn hiệu lực giới hạn. Chạy lại `picoclaw auth wecom` để lấy mã mới.
+
+### Kết nối WebSocket thất bại
+
+- Kiểm tra xem `bot_id` và `secret` có chính xác không.
+- Xác nhận máy chủ có thể kết nối đến `wss://openws.work.weixin.qq.com` (WebSocket đi ra, không cần cổng đến).
+
+### Phản hồi không đến
+
+- Kiểm tra xem `allow_from` có đang chặn người gửi không.
+- Kiểm tra rằng `channels.wecom.bot_id` và `channels.wecom.secret` đã được thiết lập và không trống.
@@ -1,24 +1,34 @@
 > 返回 [README](../../../README.zh.md)

-# 企业微信
+# 企业微信（WeCom）

-PicoClaw 现在将企业微信统一为一个 `channels.wecom` 渠道，并基于企业微信官方 AI Bot WebSocket 协议实现。
-这取代了旧的 `wecom`、`wecom_app`、`wecom_aibot` 三套配置模型。
+PicoClaw 将企业微信整合为单一的 `channels.wecom` 渠道，基于腾讯官方企业微信 AI Bot WebSocket API 实现。
+原有的 `wecom`、`wecom_app`、`wecom_aibot` 三个独立渠道已合并为统一配置模型。

-## 当前渠道能力
+> 本渠道无需公网 Webhook 回调地址。PicoClaw 主动向企业微信建立出站 WebSocket 连接。

- 支持私聊和群聊
- 支持企业微信侧流式回复
- 支持接收文本、语音、图片、文件、视频和 mixed 消息
- 支持发送文本与媒体消息（`image`、`file`、`voice`、`video`）
- 支持通过 `picoclaw auth wecom` 扫码写入配置
- 支持统一白名单与 `reasoning_channel_id`
+## 支持的功能

-> 这个渠道不再需要公网 webhook 回调地址。PicoClaw 会主动向企业微信发起 WebSocket 连接。
+- 单聊和群聊消息收发
+- 基于企业微信 AI Bot 协议的流式回复
+- 接收文本、语音、图片、文件、视频及混合消息
+- 发送文本及媒体消息（`image`、`file`、`voice`、`video`）
+- 通过 Web UI 或 CLI 扫码绑定
+- 发送者白名单和 `reasoning_channel_id` 路由
+
+---

 ## 快速开始

-### 方式 1：命令行扫码登录
+### 方式一：Web UI 扫码绑定（推荐）
+
+打开 Web UI，进入 **Channels → WeCom**，点击扫码绑定按钮。用企业微信扫码并在 App 内确认，凭据自动保存。
+
+<p align="center">
+<img src="../../../assets/wecom-qr-binding.jpg" alt="Web UI 企业微信扫码绑定" width="600">
+</p>
+
+### 方式二：CLI 扫码登录

 运行：

@@ -26,16 +36,23 @@ PicoClaw 现在将企业微信统一为一个 `channels.wecom` 渠道，并基
 picoclaw auth wecom
 ```

-该命令会在终端打印二维码，等待你在企业微信中确认，然后把生成的 `bot_id` 和 `secret` 写入
-`channels.wecom`。
+命令执行流程：
+1. 向企业微信请求二维码并在终端打印
+2. 同时打印一个**二维码链接**，终端二维码不清晰时可在浏览器中打开
+3. 轮询确认状态——扫码后还需要在**企业微信 App 内点击确认**
+4. 成功后将 `bot_id` 和 `secret` 写入 `channels.wecom` 并保存配置

-如果需要更长等待时间，可以加 `--timeout`：
+默认超时为 **5 分钟**，可通过 `--timeout` 延长：

 ```bash
 picoclaw auth wecom --timeout 10m
 ```

-### 方式 2：手动配置
+> ⚠️ 仅扫描二维码还不够——必须在企业微信 App 内点击**确认**，否则命令会超时。
+
+### 方式三：手动配置
+
+如果已有企业微信 AI Bot 的 `bot_id` 和 `secret`，可直接配置：

 ```json
 {
@@ -53,52 +70,79 @@ picoclaw auth wecom --timeout 10m
 }
 ```

-## 配置字段
+---

-| 字段 | 类型 | 必填 | 说明 |
-| ---- | ---- | ---- | ---- |
-| `enabled` | bool | 否 | 是否启用企业微信渠道。 |
-| `bot_id` | string | 是 | 企业微信 AI Bot 标识。渠道启用时必填。 |
-| `secret` | string | 是 | 企业微信 AI Bot 密钥。渠道启用时必填。 |
-| `websocket_url` | string | 否 | WebSocket 地址，默认 `wss://openws.work.weixin.qq.com`。 |
-| `send_thinking_message` | bool | 否 | 是否在流式最终回复前先发送一段 `Processing...` 开场消息，默认 `true`。 |
-| `allow_from` | array | 否 | 发送者白名单；空数组表示允许所有发送者。 |
-| `reasoning_channel_id` | string | 否 | 可选的 reasoning/thinking 输出目标。 |
+## 配置项说明
+
+| 字段 | 类型 | 默认值 | 说明 |
+| ---- | ---- | ------ | ---- |
+| `enabled` | bool | `false` | 启用企业微信渠道。 |
+| `bot_id` | string | — | 企业微信 AI Bot 标识符。启用时必填。 |
+| `secret` | string | — | 企业微信 AI Bot 密钥。加密存储于 `.security.yml`。启用时必填。 |
+| `websocket_url` | string | `wss://openws.work.weixin.qq.com` | 企业微信 WebSocket 端点。 |
+| `send_thinking_message` | bool | `true` | 在流式回复开始前发送"处理中..."提示消息。 |
+| `allow_from` | array | `[]` | 发送者白名单。为空时允许所有人。 |
+| `reasoning_channel_id` | string | `""` | 可选，将推理/思考内容路由到指定会话 ID。 |
+
+### 环境变量
+
+所有字段均可通过 `PICOCLAW_CHANNELS_WECOM_` 前缀的环境变量覆盖：
+
+| 环境变量 | 对应字段 |
+| -------- | -------- |
+| `PICOCLAW_CHANNELS_WECOM_ENABLED` | `enabled` |
+| `PICOCLAW_CHANNELS_WECOM_BOT_ID` | `bot_id` |
+| `PICOCLAW_CHANNELS_WECOM_SECRET` | `secret` |
+| `PICOCLAW_CHANNELS_WECOM_WEBSOCKET_URL` | `websocket_url` |
+| `PICOCLAW_CHANNELS_WECOM_SEND_THINKING_MESSAGE` | `send_thinking_message` |
+| `PICOCLAW_CHANNELS_WECOM_ALLOW_FROM` | `allow_from` |
+| `PICOCLAW_CHANNELS_WECOM_REASONING_CHANNEL_ID` | `reasoning_channel_id` |
+
+---

 ## 运行时行为

- PicoClaw 会保留当前会话对应的企业微信 turn，优先继续同一个流式回复。
- 如果流式上下文已经失效，回复会自动回退到主动推送消息。
- 收到的媒体会先下载到 media store，再交给 Agent 处理。
- 发出的媒体会先按分片上传到企业微信，再作为普通媒体消息发送。
+- PicoClaw 维护活跃的企业微信 Turn，流式回复尽可能在同一流上继续。
+- 流式回复最大持续时长为 **5.5 分钟**，最小发送间隔为 **500ms**。
+- 流式不可用时，回复降级为主动推送。
+- 会话路由关联在 **30 分钟**无活动后过期。
+- 接收到的媒体文件先下载到本地媒体存储，再传递给 Agent。
+- 发送媒体时先上传为企业微信临时文件，再作为媒体消息发送。
+- 自动检测并过滤重复消息（环形缓冲区，最多记录 1000 条消息 ID）。

-## 迁移说明
+---

-这个分支移除了旧的多通道企业微信模型。
+## 从旧版企业微信配置迁移

-| 旧配置 | 现在怎么做 |
-| ------ | ---------- |
-| `channels.wecom` webhook 机器人 | 改为使用 `bot_id` + `secret` 的 `channels.wecom`。 |
-| `channels.wecom_app` | 删除，统一迁移到 `channels.wecom`。 |
-| `channels.wecom_aibot` | 配置迁移到 `channels.wecom`。 |
-| `token`、`encoding_aes_key`、`webhook_url`、`webhook_path` | 企业微信渠道不再使用这些字段。 |
-| `corp_id`、`corp_secret`、`agent_id` | 企业微信渠道不再使用这些字段。 |
-| 企业微信下的 `welcome_message`、`processing_message`、`max_steps` | 不再属于企业微信渠道配置。 |
+| 旧配置 | 迁移方式 |
+| ------ | -------- |
+| `channels.wecom`（Webhook 机器人） | 改用 `channels.wecom`，填写 `bot_id` + `secret`。 |
+| `channels.wecom_app` | 删除，改用 `channels.wecom`。 |
+| `channels.wecom_aibot` | 将 `bot_id` 和 `secret` 移至 `channels.wecom`。 |
+| `token`、`encoding_aes_key`、`webhook_url`、`webhook_path` | 已废弃，从配置中删除。 |
+| `corp_id`、`corp_secret`、`agent_id` | 已废弃，从配置中删除。 |
+| `welcome_message`、`processing_message`、`max_steps` | 已不属于企业微信渠道配置，删除即可。 |
+
+---

 ## 常见问题

-### `picoclaw auth wecom` 超时
+### 扫码绑定超时

- 用更大的 `--timeout` 重新执行。
- 确认是在企业微信里完成了确认，而不只是扫描二维码。
+- 扫码后必须在**企业微信 App 内点击确认**，仅扫码不够。
+- 使用更长的超时重试：`picoclaw auth wecom --timeout 10m`
+- 终端二维码不清晰时，使用命令打印的**二维码链接**在浏览器中打开。
+
+### 二维码已过期
+
+- 二维码有效期有限，重新运行 `picoclaw auth wecom` 获取新二维码。

 ### WebSocket 连接失败

 - 检查 `bot_id` 和 `secret` 是否正确。
- 确认运行环境可以访问 `wss://openws.work.weixin.qq.com`。
+- 确认设备可以访问 `wss://openws.work.weixin.qq.com`（出站 WebSocket，无需开放入站端口）。

-### 消息没有回到企业微信
-
- 检查 `allow_from` 是否拦截了发送者。
- 检查启动日志或 launcher 校验，确认 `channels.wecom.bot_id` / `channels.wecom.secret` 已填写。
+### 收不到回复

+- 检查 `allow_from` 是否屏蔽了发送者。
+- 确认 `channels.wecom.bot_id` 和 `channels.wecom.secret` 已填写且非空。
@@ -1,118 +0,0 @@
-> Retour au [README](../../../../README.fr.md)
-
-# WeCom AI Bot
-
-Le WeCom AI Bot est une méthode d'intégration de conversation IA officiellement fournie par WeCom. Il prend en charge les conversations privées et de groupe, intègre un protocole de réponse en streaming et supporte l'envoi proactif de la réponse finale via `response_url` en cas de dépassement de délai.
-
-## Comparaison avec les autres canaux WeCom
-
-| Fonctionnalité | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|----------------|-----------|-----------|-----------------|
-| Chat privé | ✅ | ✅ | ✅ |
-| Chat de groupe | ✅ | ❌ | ✅ |
-| Sortie en streaming | ❌ | ❌ | ✅ |
-| Push proactif en cas de timeout | ❌ | ✅ | ✅ |
-| Complexité de configuration | Faible | Élevée | Moyenne |
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-| Champ | Type | Requis | Description |
-| ---------------- | ------ | ------ | -------------------------------------------------- |
-| token | string | Oui | Jeton de vérification du callback, configuré sur la page de gestion de l'AI Bot |
-| encoding_aes_key | string | Oui | Clé AES de 43 caractères, générée aléatoirement sur la page de gestion de l'AI Bot |
-| webhook_path | string | Non | Chemin du webhook (par défaut : /webhook/wecom-aibot) |
-| allow_from | array | Non | Liste blanche d'ID utilisateurs ; un tableau vide autorise tous les utilisateurs |
-| welcome_message | string | Non | Message de bienvenue envoyé à l'ouverture du chat ; laisser vide pour désactiver |
-| reply_timeout | int | Non | Délai de réponse en secondes (par défaut : 5) |
-| max_steps | int | Non | Nombre maximum d'étapes d'exécution de l'agent (par défaut : 10) |
-
-## Procédure de configuration
-
-1. Connectez-vous à la [console d'administration WeCom](https://work.weixin.qq.com/wework_admin)
-2. Accédez à « Gestion des applications » → « AI Bot », puis créez ou sélectionnez un AI Bot
-3. Sur la page de configuration de l'AI Bot, renseignez les informations de « Réception des messages » :
-   - **URL** : `http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token** : Généré aléatoirement ou personnalisé
-   - **EncodingAESKey** : Cliquez sur « Générer aléatoirement » pour obtenir une clé de 43 caractères
-4. Saisissez le Token et l'EncodingAESKey dans le fichier de configuration PicoClaw, démarrez le service, puis revenez à la console d'administration pour enregistrer (WeCom enverra une requête de vérification)
-
-> [!TIP]
-> Le serveur doit être accessible par les serveurs WeCom. Si vous êtes sur un intranet ou en développement local, utilisez [ngrok](https://ngrok.com) ou frp pour le tunneling.
-
-## Protocole de réponse en streaming
-
-Le WeCom AI Bot utilise un protocole de « pull en streaming », différent de la réponse unique d'un webhook standard :
-
-```
-L'utilisateur envoie un message
-  │
-  ▼
-PicoClaw retourne immédiatement {finish: false} (l'agent commence le traitement)
-  │
-  ▼
-WeCom effectue un pull environ toutes les 1 seconde avec {msgtype: "stream", stream: {id: "..."}}
-  │
-  ├─ Agent non terminé → retourne {finish: false} (continuer à attendre)
-  │
-  └─ Agent terminé → retourne {finish: true, content: "contenu de la réponse"}
-```
-
-**Gestion du timeout** (tâche dépassant 30 secondes) :
-
-Si le traitement de l'agent dépasse environ 30 secondes (la fenêtre de polling maximale de WeCom est de 6 minutes), PicoClaw va :
-
-1. Fermer immédiatement le stream et afficher à l'utilisateur : « ⏳ 正在处理中，请稍候，结果将稍后发送。 »
-2. L'agent continue de s'exécuter en arrière-plan
-3. Une fois l'agent terminé, la réponse finale est envoyée proactivement à l'utilisateur via le `response_url` inclus dans le message
-
-> `response_url` est émis par WeCom, valable 1 heure, utilisable une seule fois, sans chiffrement requis — il suffit de POSTer directement le corps du message markdown.
-
-## Message de bienvenue
-
-Lorsque `welcome_message` est configuré, PicoClaw répond automatiquement avec ce message lorsqu'un utilisateur ouvre la fenêtre de chat avec l'AI Bot (événement `enter_chat`). Laisser vide pour ignorer silencieusement.
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## FAQ
-
-### Échec de la vérification de l'URL de callback
-
- Vérifiez que le pare-feu du serveur autorise le port concerné (par défaut 18790)
- Vérifiez que `token` et `encoding_aes_key` sont correctement renseignés
- Consultez les logs PicoClaw pour voir si une requête GET de WeCom a été reçue
-
-### Les messages ne reçoivent pas de réponse
-
- Vérifiez que `allow_from` ne restreint pas accidentellement l'expéditeur
- Recherchez `context canceled` ou des erreurs d'agent dans les logs
- Vérifiez que la configuration de l'agent (ex. `model_name`) est correcte
-
-### Pas de push final reçu pour les tâches longues
-
- Vérifiez que le callback du message inclut `response_url` (uniquement supporté par la nouvelle version du WeCom AI Bot)
- Vérifiez que le serveur peut effectuer des requêtes sortantes (nécessite un POST vers `response_url`)
- Consultez les logs pour les mots-clés `response_url mode` et `Sending reply via response_url`
-
-## Références
-
- [Documentation d'intégration WeCom AI Bot](https://developer.work.weixin.qq.com/document/path/100719)
- [Description du protocole de réponse en streaming](https://developer.work.weixin.qq.com/document/path/100719)
- [Réponse proactive via response_url](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,118 +0,0 @@
-> [README](../../../../README.ja.md) に戻る
-
-# 企業WeChat AIボット
-
-企業WeChat AIボット（AI Bot）は、企業WeChatが公式に提供するAI会話連携方式です。プライベートチャットとグループチャットの両方をサポートし、ストリーミングレスポンスプロトコルを内蔵しており、タイムアウト後に `response_url` を通じて最終返信をプッシュする機能もサポートしています。
-
-## 他のWeCom チャンネルとの比較
-
-| 機能 | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|------|-----------|-----------|-----------------|
-| プライベートチャット | ✅ | ✅ | ✅ |
-| グループチャット | ✅ | ❌ | ✅ |
-| ストリーミング出力 | ❌ | ❌ | ✅ |
-| タイムアウト時のプッシュ | ❌ | ✅ | ✅ |
-| 設定の複雑さ | 低 | 高 | 中 |
-
-## 設定
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-| フィールド | 型 | 必須 | 説明 |
-| ---------------- | ------ | ---- | -------------------------------------------------- |
-| token | string | はい | コールバック検証トークン。AIボット管理ページで設定 |
-| encoding_aes_key | string | はい | 43文字のAESキー。AIボット管理ページでランダム生成 |
-| webhook_path | string | いいえ | Webhookパス（デフォルト：/webhook/wecom-aibot） |
-| allow_from | array | いいえ | ユーザーIDの許可リスト。空配列は全ユーザーを許可 |
-| welcome_message | string | いいえ | ユーザーがチャットを開いたときに送信するウェルカムメッセージ。空白の場合は送信しない |
-| reply_timeout | int | いいえ | 返信タイムアウト（秒、デフォルト：5） |
-| max_steps | int | いいえ | エージェントの最大実行ステップ数（デフォルト：10） |
-
-## セットアップ手順
-
-1. [企業WeChat管理コンソール](https://work.weixin.qq.com/wework_admin) にログイン
-2. 「アプリ管理」→「AIボット」に進み、AIボットを作成または選択
-3. AIボット設定ページで「メッセージ受信」情報を入力：
-   - **URL**：`http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token**：ランダム生成またはカスタム
-   - **EncodingAESKey**：「ランダム生成」をクリックして43文字のキーを取得
-4. TokenとEncodingAESKeyをPicoClawの設定ファイルに入力し、サービスを起動してから管理コンソールに戻って保存（企業WeChatが検証リクエストを送信します）
-
-> [!TIP]
-> サーバーは企業WeChatのサーバーからアクセス可能である必要があります。イントラネットやローカル開発環境の場合は、[ngrok](https://ngrok.com) またはfrpを使用してトンネリングしてください。
-
-## ストリーミングレスポンスプロトコル
-
-WeCom AIボットは「ストリーミングプル」プロトコルを使用しており、通常のWebhookの一回限りの返信とは異なります：
-
-```
-ユーザーがメッセージを送信
-  │
-  ▼
-PicoClawが即座に {finish: false} を返す（エージェントが処理開始）
-  │
-  ▼
-企業WeChatが約1秒ごとに {msgtype: "stream", stream: {id: "..."}} でプル
-  │
-  ├─ エージェント未完了 → {finish: false} を返す（待機継続）
-  │
-  └─ エージェント完了 → {finish: true, content: "返信内容"} を返す
-```
-
-**タイムアウト処理**（タスクが30秒を超える場合）：
-
-エージェントの処理時間が約30秒を超えた場合（企業WeChatの最大ポーリングウィンドウは6分）、PicoClawは：
-
-1. 即座にストリームを閉じ、ユーザーに「⏳ 正在处理中，请稍候，结果将稍后发送。」と表示
-2. エージェントはバックグラウンドで処理を継続
-3. エージェント完了後、メッセージに含まれる `response_url` を通じて最終返信をユーザーにプッシュ
-
-> `response_url` は企業WeChatが発行し、有効期限は1時間、使用は1回限りで、暗号化不要。マークダウンメッセージ本文をそのままPOSTするだけです。
-
-## ウェルカムメッセージ
-
-`welcome_message` を設定すると、ユーザーがAIボットとのチャットウィンドウを開いたとき（`enter_chat` イベント）に、PicoClawが自動的にそのメッセージを返信します。空白の場合は無視されます。
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## よくある質問
-
-### コールバックURL検証の失敗
-
- サーバーのファイアウォールで該当ポートが開放されているか確認（デフォルト18790）
- `token` と `encoding_aes_key` が正しく入力されているか確認
- PicoClawのログに企業WeChatからのGETリクエストが届いているか確認
-
-### メッセージに返信がない
-
- `allow_from` が誤って送信者を制限していないか確認
- ログに `context canceled` またはエージェントエラーが出ていないか確認
- エージェント設定（`model_name` など）が正しいか確認
-
-### 長時間タスクで最終プッシュが届かない
-
- メッセージコールバックに `response_url` が含まれているか確認（新バージョンの企業WeChat AIボットのみ対応）
- サーバーが外部ネットワークへのアウトバウンドリクエストを送信できるか確認（`response_url` へのPOSTが必要）
- ログのキーワード `response_url mode` と `Sending reply via response_url` を確認
-
-## 参考ドキュメント
-
- [企業WeChat AIボット連携ドキュメント](https://developer.work.weixin.qq.com/document/path/100719)
- [ストリーミングレスポンスプロトコルの説明](https://developer.work.weixin.qq.com/document/path/100719)
- [response_url によるプロアクティブ返信](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,118 +0,0 @@
-> Back to [README](../../../../README.md)
-
-# WeCom AI Bot
-
-The WeCom AI Bot is an official AI conversation integration provided by WeCom. It supports both private and group chats, has a built-in streaming response protocol, and supports proactively pushing the final reply via `response_url` after a timeout.
-
-## Comparison with Other WeCom Channels
-
-| Feature | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|---------|-----------|-----------|-----------------|
-| Private Chat | ✅ | ✅ | ✅ |
-| Group Chat | ✅ | ❌ | ✅ |
-| Streaming Output | ❌ | ❌ | ✅ |
-| Proactive Push on Timeout | ❌ | ✅ | ✅ |
-| Configuration Complexity | Low | High | Medium |
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-| Field | Type | Required | Description |
-| ---------------- | ------ | -------- | -------------------------------------------------- |
-| token | string | Yes | Callback verification token, configured on the AI Bot management page |
-| encoding_aes_key | string | Yes | 43-character AES key, randomly generated on the AI Bot management page |
-| webhook_path | string | No | Webhook path (default: /webhook/wecom-aibot) |
-| allow_from | array | No | User ID allowlist; empty array allows all users |
-| welcome_message | string | No | Welcome message sent when a user opens the chat; leave empty to disable |
-| reply_timeout | int | No | Reply timeout in seconds (default: 5) |
-| max_steps | int | No | Maximum agent execution steps (default: 10) |
-
-## Setup
-
-1. Log in to the [WeCom Admin Console](https://work.weixin.qq.com/wework_admin)
-2. Go to "App Management" → "AI Bot", then create or select an AI Bot
-3. On the AI Bot configuration page, fill in the "Message Reception" details:
-   - **URL**: `http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token**: Randomly generated or custom
-   - **EncodingAESKey**: Click "Random Generate" to get a 43-character key
-4. Enter the Token and EncodingAESKey into the PicoClaw config file, start the service, then return to the admin console to save (WeCom will send a verification request)
-
-> [!TIP]
-> The server must be accessible by WeCom's servers. If you are on an intranet or developing locally, use [ngrok](https://ngrok.com) or frp for tunneling.
-
-## Streaming Response Protocol
-
-WeCom AI Bot uses a "streaming pull" protocol, which differs from the one-shot reply of a standard webhook:
-
-```
-User sends a message
-  │
-  ▼
-PicoClaw immediately returns {finish: false} (Agent starts processing)
-  │
-  ▼
-WeCom pulls approximately every 1 second with {msgtype: "stream", stream: {id: "..."}}
-  │
-  ├─ Agent not done → returns {finish: false} (keep waiting)
-  │
-  └─ Agent done → returns {finish: true, content: "reply content"}
-```
-
-**Timeout Handling** (task exceeds 30 seconds):
-
-If the Agent takes longer than approximately 30 seconds (WeCom's maximum polling window is 6 minutes), PicoClaw will:
-
-1. Immediately close the stream and show the user: "⏳ 正在处理中，请稍候，结果将稍后发送。"
-2. The Agent continues running in the background
-3. Once the Agent finishes, the final reply is proactively pushed to the user via the `response_url` included in the message
-
-> `response_url` is issued by WeCom, valid for 1 hour, can only be used once, requires no encryption — just POST the markdown message body directly.
-
-## Welcome Message
-
-When `welcome_message` is configured, PicoClaw will automatically reply with it when a user opens the chat window with the AI Bot (`enter_chat` event). Leave it empty to silently ignore the event.
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## FAQ
-
-### Callback URL Verification Failed
-
- Confirm the server firewall has the relevant port open (default 18790)
- Confirm `token` and `encoding_aes_key` are entered correctly
- Check PicoClaw logs to see if a GET request from WeCom was received
-
-### Messages Not Getting a Reply
-
- Check whether `allow_from` is accidentally restricting the sender
- Look for `context canceled` or Agent errors in the logs
- Confirm the Agent configuration (e.g., `model_name`) is correct
-
-### No Final Push Received for Long-Running Tasks
-
- Confirm the message callback includes `response_url` (only supported by the newer WeCom AI Bot)
- Confirm the server can make outbound requests (needs to POST to `response_url`)
- Check logs for keywords `response_url mode` and `Sending reply via response_url`
-
-## Reference
-
- [WeCom AI Bot Integration Docs](https://developer.work.weixin.qq.com/document/path/100719)
- [Streaming Response Protocol](https://developer.work.weixin.qq.com/document/path/100719)
- [Proactive Reply via response_url](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,118 +0,0 @@
-> Voltar ao [README](../../../../README.pt-br.md)
-
-# WeCom AI Bot
-
-O WeCom AI Bot é uma forma oficial de integração de conversas com IA fornecida pelo WeCom. Suporta conversas privadas e em grupo, possui um protocolo de resposta em streaming integrado e suporta o envio proativo da resposta final via `response_url` após um timeout.
-
-## Comparação com outros canais WeCom
-
-| Recurso | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|---------|-----------|-----------|-----------------|
-| Chat privado | ✅ | ✅ | ✅ |
-| Chat em grupo | ✅ | ❌ | ✅ |
-| Saída em streaming | ❌ | ❌ | ✅ |
-| Push proativo em timeout | ❌ | ✅ | ✅ |
-| Complexidade de configuração | Baixa | Alta | Média |
-
-## Configuração
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-| Campo | Tipo | Obrigatório | Descrição |
-| ---------------- | ------ | ----------- | -------------------------------------------------- |
-| token | string | Sim | Token de verificação de callback, configurado na página de gerenciamento do AI Bot |
-| encoding_aes_key | string | Sim | Chave AES de 43 caracteres, gerada aleatoriamente na página de gerenciamento do AI Bot |
-| webhook_path | string | Não | Caminho do webhook (padrão: /webhook/wecom-aibot) |
-| allow_from | array | Não | Lista de permissão de IDs de usuários; array vazio permite todos os usuários |
-| welcome_message | string | Não | Mensagem de boas-vindas enviada quando o usuário abre o chat; deixe vazio para desativar |
-| reply_timeout | int | Não | Timeout de resposta em segundos (padrão: 5) |
-| max_steps | int | Não | Número máximo de etapas de execução do agente (padrão: 10) |
-
-## Configuração passo a passo
-
-1. Faça login no [Console de Administração do WeCom](https://work.weixin.qq.com/wework_admin)
-2. Acesse "Gerenciamento de Apps" → "AI Bot", depois crie ou selecione um AI Bot
-3. Na página de configuração do AI Bot, preencha as informações de "Recebimento de Mensagens":
-   - **URL**: `http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token**: Gerado aleatoriamente ou personalizado
-   - **EncodingAESKey**: Clique em "Gerar Aleatoriamente" para obter uma chave de 43 caracteres
-4. Insira o Token e o EncodingAESKey no arquivo de configuração do PicoClaw, inicie o serviço e volte ao console de administração para salvar (o WeCom enviará uma requisição de verificação)
-
-> [!TIP]
-> O servidor precisa ser acessível pelos servidores do WeCom. Se estiver em uma intranet ou desenvolvendo localmente, use [ngrok](https://ngrok.com) ou frp para tunelamento.
-
-## Protocolo de resposta em streaming
-
-O WeCom AI Bot usa um protocolo de "pull em streaming", diferente da resposta única de um webhook padrão:
-
-```
-Usuário envia uma mensagem
-  │
-  ▼
-PicoClaw retorna imediatamente {finish: false} (Agente começa a processar)
-  │
-  ▼
-WeCom faz pull aproximadamente a cada 1 segundo com {msgtype: "stream", stream: {id: "..."}}
-  │
-  ├─ Agente não concluído → retorna {finish: false} (continuar aguardando)
-  │
-  └─ Agente concluído → retorna {finish: true, content: "conteúdo da resposta"}
-```
-
-**Tratamento de timeout** (tarefa excede 30 segundos):
-
-Se o processamento do agente demorar mais de aproximadamente 30 segundos (a janela máxima de polling do WeCom é de 6 minutos), o PicoClaw irá:
-
-1. Fechar imediatamente o stream e exibir ao usuário: "⏳ 正在处理中，请稍候，结果将稍后发送。"
-2. O agente continua executando em segundo plano
-3. Após a conclusão do agente, a resposta final é enviada proativamente ao usuário via `response_url` incluído na mensagem
-
-> `response_url` é emitido pelo WeCom, válido por 1 hora, pode ser usado apenas uma vez, sem necessidade de criptografia — basta fazer um POST com o corpo da mensagem em markdown diretamente.
-
-## Mensagem de boas-vindas
-
-Quando `welcome_message` está configurado, o PicoClaw responde automaticamente com essa mensagem quando um usuário abre a janela de chat com o AI Bot (evento `enter_chat`). Deixe vazio para ignorar silenciosamente.
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## Perguntas frequentes
-
-### Falha na verificação da URL de callback
-
- Confirme que o firewall do servidor tem a porta correspondente aberta (padrão 18790)
- Confirme que `token` e `encoding_aes_key` estão preenchidos corretamente
- Verifique os logs do PicoClaw para ver se uma requisição GET do WeCom foi recebida
-
-### Mensagens sem resposta
-
- Verifique se `allow_from` está restringindo acidentalmente o remetente
- Procure por `context canceled` ou erros do agente nos logs
- Confirme que a configuração do agente (ex.: `model_name`) está correta
-
-### Nenhum push final recebido para tarefas longas
-
- Confirme que o callback da mensagem inclui `response_url` (suportado apenas pelo novo WeCom AI Bot)
- Confirme que o servidor consegue fazer requisições de saída (precisa fazer POST para `response_url`)
- Verifique nos logs as palavras-chave `response_url mode` e `Sending reply via response_url`
-
-## Referências
-
- [Documentação de integração do WeCom AI Bot](https://developer.work.weixin.qq.com/document/path/100719)
- [Descrição do protocolo de resposta em streaming](https://developer.work.weixin.qq.com/document/path/100719)
- [Resposta proativa via response_url](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,118 +0,0 @@
-> Quay lại [README](../../../../README.vi.md)
-
-# WeCom AI Bot
-
-WeCom AI Bot là phương thức tích hợp hội thoại AI chính thức do WeCom cung cấp. Hỗ trợ cả chat riêng tư và chat nhóm, tích hợp giao thức phản hồi streaming, và hỗ trợ chủ động đẩy phản hồi cuối cùng qua `response_url` sau khi hết thời gian chờ.
-
-## So sánh với các kênh WeCom khác
-
-| Tính năng | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|-----------|-----------|-----------|-----------------|
-| Chat riêng tư | ✅ | ✅ | ✅ |
-| Chat nhóm | ✅ | ❌ | ✅ |
-| Đầu ra streaming | ❌ | ❌ | ✅ |
-| Đẩy chủ động khi timeout | ❌ | ✅ | ✅ |
-| Độ phức tạp cấu hình | Thấp | Cao | Trung bình |
-
-## Cấu hình
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-| Trường | Kiểu | Bắt buộc | Mô tả |
-| ---------------- | ------ | --------- | -------------------------------------------------- |
-| token | string | Có | Token xác minh callback, cấu hình trên trang quản lý AI Bot |
-| encoding_aes_key | string | Có | Khóa AES 43 ký tự, được tạo ngẫu nhiên trên trang quản lý AI Bot |
-| webhook_path | string | Không | Đường dẫn webhook (mặc định: /webhook/wecom-aibot) |
-| allow_from | array | Không | Danh sách cho phép ID người dùng; mảng rỗng cho phép tất cả người dùng |
-| welcome_message | string | Không | Tin nhắn chào mừng gửi khi người dùng mở chat; để trống để tắt |
-| reply_timeout | int | Không | Thời gian chờ phản hồi tính bằng giây (mặc định: 5) |
-| max_steps | int | Không | Số bước thực thi tối đa của agent (mặc định: 10) |
-
-## Hướng dẫn thiết lập
-
-1. Đăng nhập vào [Bảng điều khiển quản trị WeCom](https://work.weixin.qq.com/wework_admin)
-2. Vào "Quản lý ứng dụng" → "AI Bot", sau đó tạo hoặc chọn một AI Bot
-3. Trên trang cấu hình AI Bot, điền thông tin "Nhận tin nhắn":
-   - **URL**: `http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token**: Tạo ngẫu nhiên hoặc tùy chỉnh
-   - **EncodingAESKey**: Nhấp "Tạo ngẫu nhiên" để lấy khóa 43 ký tự
-4. Nhập Token và EncodingAESKey vào file cấu hình PicoClaw, khởi động dịch vụ rồi quay lại bảng điều khiển quản trị để lưu (WeCom sẽ gửi yêu cầu xác minh)
-
-> [!TIP]
-> Máy chủ cần có thể truy cập được từ các máy chủ WeCom. Nếu bạn đang ở mạng nội bộ hoặc phát triển cục bộ, hãy sử dụng [ngrok](https://ngrok.com) hoặc frp để tạo tunnel.
-
-## Giao thức phản hồi streaming
-
-WeCom AI Bot sử dụng giao thức "pull streaming", khác với phản hồi một lần của webhook thông thường:
-
-```
-Người dùng gửi tin nhắn
-  │
-  ▼
-PicoClaw trả về ngay {finish: false} (Agent bắt đầu xử lý)
-  │
-  ▼
-WeCom pull khoảng mỗi 1 giây với {msgtype: "stream", stream: {id: "..."}}
-  │
-  ├─ Agent chưa xong → trả về {finish: false} (tiếp tục chờ)
-  │
-  └─ Agent xong → trả về {finish: true, content: "nội dung phản hồi"}
-```
-
-**Xử lý timeout** (tác vụ vượt quá 30 giây):
-
-Nếu thời gian xử lý của agent vượt quá khoảng 30 giây (cửa sổ polling tối đa của WeCom là 6 phút), PicoClaw sẽ:
-
-1. Đóng stream ngay lập tức và hiển thị cho người dùng: "⏳ 正在处理中，请稍候，结果将稍后发送。"
-2. Agent tiếp tục chạy ở nền
-3. Sau khi agent hoàn thành, phản hồi cuối cùng được chủ động đẩy đến người dùng qua `response_url` có trong tin nhắn
-
-> `response_url` do WeCom cấp, có hiệu lực 1 giờ, chỉ dùng được một lần, không cần mã hóa — chỉ cần POST trực tiếp nội dung tin nhắn markdown.
-
-## Tin nhắn chào mừng
-
-Khi `welcome_message` được cấu hình, PicoClaw sẽ tự động phản hồi bằng tin nhắn đó khi người dùng mở cửa sổ chat với AI Bot (sự kiện `enter_chat`). Để trống để bỏ qua im lặng.
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## Câu hỏi thường gặp
-
-### Xác minh URL callback thất bại
-
- Xác nhận tường lửa máy chủ đã mở cổng tương ứng (mặc định 18790)
- Xác nhận `token` và `encoding_aes_key` được điền đúng
- Kiểm tra log PicoClaw xem có nhận được yêu cầu GET từ WeCom không
-
-### Tin nhắn không nhận được phản hồi
-
- Kiểm tra xem `allow_from` có vô tình hạn chế người gửi không
- Tìm `context canceled` hoặc lỗi agent trong log
- Xác nhận cấu hình agent (ví dụ: `model_name`) là đúng
-
-### Không nhận được push cuối cùng cho tác vụ dài
-
- Xác nhận callback tin nhắn có chứa `response_url` (chỉ hỗ trợ bởi WeCom AI Bot phiên bản mới)
- Xác nhận máy chủ có thể thực hiện yêu cầu ra ngoài (cần POST đến `response_url`)
- Kiểm tra log với từ khóa `response_url mode` và `Sending reply via response_url`
-
-## Tài liệu tham khảo
-
- [Tài liệu tích hợp WeCom AI Bot](https://developer.work.weixin.qq.com/document/path/100719)
- [Mô tả giao thức phản hồi streaming](https://developer.work.weixin.qq.com/document/path/100719)
- [Phản hồi chủ động qua response_url](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,185 +0,0 @@
-> 返回 [README](../../../../README.zh.md)
-
-# 企业微信智能机器人 (AI Bot)
-
-企业微信智能机器人（AI Bot）是企业微信官方提供的 AI 对话接入方式，支持私聊与群聊，内置流式响应协议。PicoClaw 当前同时支持两种接入模式：
-
- WebSocket 长连接模式：使用 `bot_id` + `secret`，优先级更高，推荐使用
- Webhook 短连接模式：使用 `token` + `encoding_aes_key`，兼容传统回调，并支持超时后通过 `response_url` 主动推送最终回复
-
-## 与其他 WeCom 通道的对比
-
-| 特性 | WeCom Bot | WeCom App | **WeCom AI Bot** |
-|------|-----------|-----------|-----------------|
-| 私聊 | ✅ | ✅ | ✅ |
-| 群聊 | ✅ | ❌ | ✅ |
-| 流式输出 | ❌ | ❌ | ✅ |
-| 超时主动推送 | ❌ | ✅ | ✅ |
-| 配置复杂度 | 低 | 高 | 中 |
-
-## 配置
-
-### WebSocket 长连接模式（推荐）
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "bot_id": "YOUR_BOT_ID",
-      "secret": "YOUR_SECRET",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-### Webhook 短连接模式
-
-```json
-{
-  "channels": {
-    "wecom_aibot": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-aibot",
-      "allow_from": [],
-      "welcome_message": "你好！有什么可以帮助你的吗？",
-      "processing_message": "⏳ Processing, please wait. The results will be sent shortly.",
-      "max_steps": 10
-    }
-  }
-}
-```
-
-### WebSocket 模式字段
-
-| 字段   | 类型   | 必填 | 描述                                       |
-|--------|--------|------|--------------------------------------------|
-| bot_id | string | 是   | AI Bot 的唯一标识，在 AI Bot 管理页面配置 |
-| secret | string | 是   | AI Bot 的密钥，在 AI Bot 管理页面配置     |
-
-### Webhook 模式字段
-
-| 字段             | 类型   | 必填 | 描述                                         |
-|------------------|--------|------|----------------------------------------------|
-| token            | string | 是   | 回调验证令牌，在 AI Bot 管理页面配置         |
-| encoding_aes_key | string | 是   | 43 字符 AES 密钥，在 AI Bot 管理页面随机生成 |
-| webhook_path     | string | 否   | Webhook 路径，默认 `/webhook/wecom-aibot`    |
-| processing_message | string | 否 | 流式超时后返回给用户的提示语                 |
-
-### 通用字段
-
-| 字段            | 类型   | 必填 | 描述                                     |
-|-----------------|--------|------|------------------------------------------|
-| allow_from      | array  | 否   | 用户 ID 白名单，空数组表示允许所有用户   |
-| welcome_message | string | 否   | 用户进入聊天时发送的欢迎语，留空则不发送 |
-| reply_timeout   | int    | 否   | 回复超时时间（秒，默认：5）              |
-| max_steps       | int    | 否   | Agent 最大执行步骤数（默认：10）         |
-
-## 模式选择
-
- 当 `bot_id` 和 `secret` 同时存在时，PicoClaw 会优先使用 WebSocket 长连接模式
- 否则，当 `token` 和 `encoding_aes_key` 同时存在时，PicoClaw 会使用 Webhook 短连接模式
-
-## 设置流程
-
-### WebSocket 长连接模式
-
-1. 登录 [企业微信管理后台](https://work.weixin.qq.com/wework_admin)
-2. 进入"应用管理" → "智能机器人"，创建或选择一个 AI Bot
-3. 在 AI Bot 配置页面，配置 Bot 的名称、头像等信息，获取 `Bot ID` 和 `Secret`
-4. 在 PicoClaw 配置文件中添加上述配置，重启 PicoClaw
-
-### Webhook 短连接模式
-
-1. 登录 [企业微信管理后台](https://work.weixin.qq.com/wework_admin)
-2. 进入"应用管理" → "智能机器人"，创建或选择一个 AI Bot
-3. 在 AI Bot 配置页面，填写"消息接收"信息：
-   - **URL**：`http://<your-server-ip>:18790/webhook/wecom-aibot`
-   - **Token**：随机生成或自定义
-   - **EncodingAESKey**：点击"随机生成"，得到 43 字符密钥
-4. 将 Token 和 EncodingAESKey 填入 PicoClaw 配置文件，启动服务后回到管理后台保存
-
-> [!TIP]
-> 服务器需要能被企业微信服务器访问。如在内网或本地开发，可使用 [ngrok](https://ngrok.com) 或 frp 做内网穿透。
-
-## Webhook 模式的流式响应协议
-
-Webhook 模式使用"流式拉取"协议，区别于普通 Webhook 的一次性回复：
-
-```
-用户发消息
-  │
-  ▼
-PicoClaw 立即返回 {finish: false}（Agent 开始处理）
-  │
-  ▼
-企业微信每隔约 1 秒拉取一次 {msgtype: "stream", stream: {id: "..."}}
-  │
-  ├─ Agent 未完成 → 返回 {finish: false}（继续等待）
-  │
-  └─ Agent 完成 → 返回 {finish: true, content: "回答内容"}
-```
-
-**超时处理**（任务超过约 30 秒）：
-
-若 Agent 处理时间超过轮询窗口，PicoClaw 会：
-
-1. 立即关闭流，向用户显示 `processing_message` 提示语
-2. Agent 继续在后台运行
-3. Agent 完成后，通过消息中携带的 `response_url` 将最终回复主动推送给用户
-
-> `response_url` 由企业微信颁发，有效期 1 小时，只可使用一次，无需加密，直接 POST markdown 消息体即可。
-
-## 超时提示语
-
-配置 `processing_message` 后，当 Webhook 模式的流式轮询超时并切换到 `response_url` 主动推送模式时，PicoClaw 会先返回这段提示语来结束当前流。
-
-```json
-"processing_message": "⏳ Processing, please wait. The results will be sent shortly."
-```
-
-## 欢迎语
-
-配置 `welcome_message` 后，当用户打开与 AI Bot 的聊天窗口时（`enter_chat` 事件），PicoClaw 会自动回复该欢迎语。留空则静默忽略。
-
-```json
-"welcome_message": "你好！我是 PicoClaw AI 助手，有什么可以帮你？"
-```
-
-## 常见问题
-
-### WebSocket 模式无法连接
-
- 检查 `bot_id` 和 `secret` 是否填写正确
- 查看日志中是否有 WebSocket 连接或鉴权失败信息
- 确认服务器可以访问企业微信长连接接口
-
-### 回调 URL 验证失败
-
-
- 确认 `token` 与 `encoding_aes_key` 填写正确
- 确认服务器防火墙已开放对应端口
- 检查 PicoClaw 日志是否收到了来自企业微信的验证请求
-
-### 消息没有回复
-
- 检查 `allow_from` 是否意外限制了发送者
- 查看日志中是否出现 `context canceled` 或 Agent 错误
- 确认 Agent 配置（`model_name` 等）正确
-
-### 超长任务没有收到最终推送
-
- 确认消息回调中携带了 `response_url`
- 确认服务器能主动访问外网
- 查看日志关键词 `response_url mode` 和 `Sending reply via response_url`
-
-## 参考文档
-
- [企业微信 AI Bot 接入文档](https://developer.work.weixin.qq.com/document/path/101463)
- [流式响应协议说明](https://developer.work.weixin.qq.com/document/path/100719)
- [response_url 主动回复](https://developer.work.weixin.qq.com/document/path/101138)
@@ -1,47 +0,0 @@
-> Retour au [README](../../../../README.fr.md)
-
-# Application interne WeCom
-
-Une application interne WeCom est une application créée par une entreprise au sein de WeCom, principalement destinée à un usage interne. Grâce aux applications internes WeCom, les entreprises peuvent assurer une communication et une collaboration efficaces avec leurs employés, améliorant ainsi la productivité.
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Champ | Type | Requis | Description |
-| ---------------- | ------ | ------ | ---------------------------------------- |
-| corp_id | string | Oui | ID de l'entreprise |
-| corp_secret | string | Oui | Secret de l'application |
-| agent_id | int | Oui | ID de l'agent de l'application |
-| token | string | Oui | Jeton de vérification du callback |
-| encoding_aes_key | string | Oui | Clé AES de 43 caractères |
-| webhook_path | string | Non | Chemin du webhook (par défaut : /webhook/wecom-app) |
-| allow_from | array | Non | Liste blanche d'ID utilisateurs |
-| reply_timeout | int | Non | Délai de réponse en secondes |
-
-## Procédure de configuration
-
-1. Connectez-vous à la [console d'administration WeCom](https://work.weixin.qq.com/)
-2. Accédez à « Gestion des applications » -> « Créer une application »
-3. Obtenez l'ID d'entreprise (CorpID) et le Secret de l'application
-4. Configurez « Réception des messages » dans les paramètres de l'application pour obtenir le Token et l'EncodingAESKey
-5. Définissez l'URL de callback sur `http://<your-server-ip>:<port>/webhook/wecom-app`
-6. Saisissez le CorpID, le Secret, l'AgentID et les autres informations dans le fichier de configuration
-
-   Remarque : PicoClaw utilise désormais un serveur HTTP Gateway partagé pour recevoir les callbacks webhook de tous les canaux. L'adresse d'écoute par défaut est 127.0.0.1:18790. Pour recevoir des callbacks depuis l'internet public, configurez un reverse proxy de votre domaine externe vers le Gateway (port par défaut 18790).
@@ -1,47 +0,0 @@
-> [README](../../../../README.ja.md) に戻る
-
-# 企業WeChat 自社開発アプリ
-
-企業WeChat 自社開発アプリとは、企業が企業WeChat内で作成するアプリケーションで、主に社内利用を目的としています。企業WeChat 自社開発アプリを通じて、企業は従業員との効率的なコミュニケーションと協業を実現し、業務効率を向上させることができます。
-
-## 設定
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| フィールド | 型 | 必須 | 説明 |
-| ---------------- | ------ | ---- | ---------------------------------------- |
-| corp_id | string | はい | 企業ID |
-| corp_secret | string | はい | アプリケーションシークレット |
-| agent_id | int | はい | アプリケーションエージェントID |
-| token | string | はい | コールバック検証トークン |
-| encoding_aes_key | string | はい | 43文字のAESキー |
-| webhook_path | string | いいえ | Webhookパス（デフォルト：/webhook/wecom-app） |
-| allow_from | array | いいえ | ユーザーIDの許可リスト |
-| reply_timeout | int | いいえ | 返信タイムアウト（秒） |
-
-## セットアップ手順
-
-1. [企業WeChat管理コンソール](https://work.weixin.qq.com/) にログイン
-2. 「アプリ管理」→「アプリを作成」に進む
-3. 企業ID（CorpID）とアプリのSecretを取得
-4. アプリ設定で「メッセージ受信」を設定し、TokenとEncodingAESKeyを取得
-5. コールバックURLを `http://<your-server-ip>:<port>/webhook/wecom-app` に設定
-6. CorpID、Secret、AgentIDなどの情報を設定ファイルに入力
-
-   注意：PicoClawは現在、すべてのチャンネルのwebhookコールバックを受信するために共有のGateway HTTPサーバーを使用しています。デフォルトのリスニングアドレスは127.0.0.1:18790です。公共インターネットからコールバックを受信するには、外部ドメインをGateway（デフォルトポート18790）にリバースプロキシしてください。
@@ -1,47 +0,0 @@
-> Back to [README](../../../../README.md)
-
-# WeCom Internal App
-
-A WeCom Internal App is an application created by an enterprise within WeCom, primarily intended for internal use. Through WeCom Internal Apps, enterprises can achieve efficient communication and collaboration with employees, improving productivity.
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Field | Type | Required | Description |
-| ---------------- | ------ | -------- | ---------------------------------------- |
-| corp_id | string | Yes | Enterprise ID |
-| corp_secret | string | Yes | Application secret |
-| agent_id | int | Yes | Application agent ID |
-| token | string | Yes | Callback verification token |
-| encoding_aes_key | string | Yes | 43-character AES key |
-| webhook_path | string | No | Webhook path (default: /webhook/wecom-app) |
-| allow_from | array | No | User ID allowlist |
-| reply_timeout | int | No | Reply timeout in seconds |
-
-## Setup
-
-1. Log in to the [WeCom Admin Console](https://work.weixin.qq.com/)
-2. Go to "App Management" -> "Create App"
-3. Obtain the Enterprise ID (CorpID) and App Secret
-4. Configure "Receive Messages" in the app settings to get the Token and EncodingAESKey
-5. Set the callback URL to `http://<your-server-ip>:<port>/webhook/wecom-app`
-6. Enter the CorpID, Secret, AgentID, and other details into the config file
-
-   Note: PicoClaw now uses a shared Gateway HTTP server to receive webhook callbacks for all channels. The default listening address is 127.0.0.1:18790. To receive callbacks from the public internet, reverse-proxy your external domain to the Gateway (default port 18790).
@@ -1,47 +0,0 @@
-> Voltar ao [README](../../../../README.pt-br.md)
-
-# App Interno WeCom
-
-Um App Interno WeCom é um aplicativo criado por uma empresa dentro do WeCom, destinado principalmente ao uso interno. Por meio dos Apps Internos WeCom, as empresas podem alcançar comunicação e colaboração eficientes com os funcionários, melhorando a produtividade.
-
-## Configuração
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Campo | Tipo | Obrigatório | Descrição |
-| ---------------- | ------ | ----------- | ---------------------------------------- |
-| corp_id | string | Sim | ID da empresa |
-| corp_secret | string | Sim | Segredo da aplicação |
-| agent_id | int | Sim | ID do agente da aplicação |
-| token | string | Sim | Token de verificação de callback |
-| encoding_aes_key | string | Sim | Chave AES de 43 caracteres |
-| webhook_path | string | Não | Caminho do webhook (padrão: /webhook/wecom-app) |
-| allow_from | array | Não | Lista de permissão de IDs de usuários |
-| reply_timeout | int | Não | Timeout de resposta em segundos |
-
-## Configuração passo a passo
-
-1. Faça login no [Console de Administração do WeCom](https://work.weixin.qq.com/)
-2. Acesse "Gerenciamento de Apps" -> "Criar App"
-3. Obtenha o ID da Empresa (CorpID) e o Secret do App
-4. Configure "Receber Mensagens" nas configurações do app para obter o Token e o EncodingAESKey
-5. Defina a URL de callback como `http://<your-server-ip>:<port>/webhook/wecom-app`
-6. Insira o CorpID, Secret, AgentID e outras informações no arquivo de configuração
-
-   Nota: O PicoClaw agora usa um servidor HTTP Gateway compartilhado para receber callbacks de webhook de todos os canais. O endereço de escuta padrão é 127.0.0.1:18790. Para receber callbacks da internet pública, configure um reverse proxy do seu domínio externo para o Gateway (porta padrão 18790).
@@ -1,47 +0,0 @@
-> Quay lại [README](../../../../README.vi.md)
-
-# Ứng dụng nội bộ WeCom
-
-Ứng dụng nội bộ WeCom là ứng dụng được doanh nghiệp tạo ra trong WeCom, chủ yếu dùng cho mục đích nội bộ. Thông qua ứng dụng nội bộ WeCom, doanh nghiệp có thể thực hiện giao tiếp và cộng tác hiệu quả với nhân viên, nâng cao hiệu suất làm việc.
-
-## Cấu hình
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Trường | Kiểu | Bắt buộc | Mô tả |
-| ---------------- | ------ | --------- | ---------------------------------------- |
-| corp_id | string | Có | ID doanh nghiệp |
-| corp_secret | string | Có | Secret của ứng dụng |
-| agent_id | int | Có | ID agent của ứng dụng |
-| token | string | Có | Token xác minh callback |
-| encoding_aes_key | string | Có | Khóa AES 43 ký tự |
-| webhook_path | string | Không | Đường dẫn webhook (mặc định: /webhook/wecom-app) |
-| allow_from | array | Không | Danh sách cho phép ID người dùng |
-| reply_timeout | int | Không | Thời gian chờ phản hồi tính bằng giây |
-
-## Hướng dẫn thiết lập
-
-1. Đăng nhập vào [Bảng điều khiển quản trị WeCom](https://work.weixin.qq.com/)
-2. Vào "Quản lý ứng dụng" -> "Tạo ứng dụng"
-3. Lấy ID doanh nghiệp (CorpID) và Secret của ứng dụng
-4. Cấu hình "Nhận tin nhắn" trong cài đặt ứng dụng để lấy Token và EncodingAESKey
-5. Đặt URL callback thành `http://<your-server-ip>:<port>/webhook/wecom-app`
-6. Nhập CorpID, Secret, AgentID và các thông tin khác vào file cấu hình
-
-   Lưu ý: PicoClaw hiện sử dụng máy chủ HTTP Gateway dùng chung để nhận callback webhook cho tất cả các kênh. Địa chỉ lắng nghe mặc định là 127.0.0.1:18790. Để nhận callback từ internet công cộng, hãy cấu hình reverse proxy từ tên miền bên ngoài của bạn đến Gateway (cổng mặc định 18790).
@@ -1,47 +0,0 @@
-> 返回 [README](../../../../README.zh.md)
-
-# 企业微信自建应用
-
-企业微信自建应用是指企业在企业微信中创建的应用，主要用于企业内部使用。通过企业微信自建应用，企业可以实现与员工的高效沟通和协作，提高工作效率。
-
-## 配置
-
-```json
-{
-  "channels": {
-    "wecom_app": {
-      "enabled": true,
-      "corp_id": "wwxxxxxxxxxxxxxxxx",
-      "corp_secret": "YOUR_CORP_SECRET",
-      "agent_id": 1000002,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_path": "/webhook/wecom-app",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| 字段             | 类型   | 必填 | 描述                                     |
-| ---------------- | ------ | ---- | ---------------------------------------- |
-| corp_id          | string | 是   | 企业 ID                                  |
-| corp_secret      | string | 是   | 应用程序密钥                             |
-| agent_id         | int    | 是   | 应用程序代理 ID                          |
-| token            | string | 是   | 回调验证令牌                             |
-| encoding_aes_key | string | 是   | 43 字符 AES 密钥                         |
-| webhook_path     | string | 否   | Webhook 路径（默认：/webhook/wecom-app） |
-| allow_from       | array  | 否   | 用户 ID 白名单                           |
-| reply_timeout    | int    | 否   | 回复超时时间（秒）                       |
-
-## 设置流程
-
-1. 登录 [企业微信管理后台](https://work.weixin.qq.com/)
-2. 进入“应用管理” -> “创建应用”
-3. 获取企业 ID (CorpID) 和应用 Secret
-4. 在应用设置中配置“接收消息”，获取 Token 和 EncodingAESKey
-5. 设置回调 URL 为 `http://<your-server-ip>:<port>/webhook/wecom-app`
-6. 将 CorpID, Secret, AgentID 等信息填入配置文件
-
-   注意: PicoClaw 现在使用共享的 Gateway HTTP 服务器来接收所有渠道的 webhook 回调，默认监听地址为 127.0.0.1:18790。如需从公网接收回调，请把外部域名反向代理到 Gateway（默认端口 18790）。
@@ -1,41 +0,0 @@
-> Retour au [README](../../../../README.fr.md)
-
-# WeCom Bot
-
-Le WeCom Bot est une méthode d'intégration rapide fournie par WeCom, permettant de recevoir des messages via une URL Webhook.
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Champ | Type | Requis | Description |
-| ---------------- | ------ | ------ | -------------------------------------------- |
-| token | string | Oui | Jeton de vérification de signature |
-| encoding_aes_key | string | Oui | Clé AES de 43 caractères utilisée pour le déchiffrement |
-| webhook_url | string | Oui | URL Webhook du bot de groupe WeCom utilisée pour envoyer les réponses |
-| webhook_path | string | Non | Chemin de l'endpoint webhook (par défaut : /webhook/wecom) |
-| allow_from | array | Non | Liste blanche d'ID utilisateurs (vide = autoriser tous les utilisateurs) |
-| reply_timeout | int | Non | Délai de réponse en secondes (par défaut : 5) |
-
-## Procédure de configuration
-
-1. Ajouter un bot à un groupe WeCom
-2. Obtenir l'URL Webhook
-3. (Pour recevoir des messages) Configurer l'adresse API de réception des messages (URL de callback), le Token et l'EncodingAESKey sur la page de configuration du bot
-4. Saisir les informations pertinentes dans le fichier de configuration
-
-   Remarque : PicoClaw utilise désormais un serveur HTTP Gateway partagé pour recevoir les callbacks webhook de tous les canaux. L'adresse d'écoute par défaut est 127.0.0.1:18790. Pour recevoir des callbacks depuis l'internet public, configurez un reverse proxy de votre domaine externe vers le Gateway (port par défaut 18790).
@@ -1,41 +0,0 @@
-> [README](../../../../README.ja.md) に戻る
-
-# 企業WeChat ボット
-
-企業WeChat ボットは、企業WeChatが提供するWebhook URLを通じてメッセージを受信できる迅速な連携方式です。
-
-## 設定
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| フィールド | 型 | 必須 | 説明 |
-| ---------------- | ------ | ---- | -------------------------------------------- |
-| token | string | はい | 署名検証トークン |
-| encoding_aes_key | string | はい | 復号化に使用する43文字のAESキー |
-| webhook_url | string | はい | 返信送信に使用する企業WeChatグループボットのWebhook URL |
-| webhook_path | string | いいえ | Webhookエンドポイントパス（デフォルト：/webhook/wecom） |
-| allow_from | array | いいえ | ユーザーIDの許可リスト（空 = 全ユーザーを許可） |
-| reply_timeout | int | いいえ | 返信タイムアウト（秒、デフォルト：5） |
-
-## セットアップ手順
-
-1. 企業WeChatグループにボットを追加
-2. Webhook URLを取得
-3. （メッセージを受信する場合）ボット設定ページでメッセージ受信APIアドレス（コールバックURL）、Token、EncodingAESKeyを設定
-4. 関連情報を設定ファイルに入力
-
-   注意：PicoClawは現在、すべてのチャンネルのwebhookコールバックを受信するために共有のGateway HTTPサーバーを使用しています。デフォルトのリスニングアドレスは127.0.0.1:18790です。公共インターネットからコールバックを受信するには、外部ドメインをGateway（デフォルトポート18790）にリバースプロキシしてください。
@@ -1,41 +0,0 @@
-> Back to [README](../../../../README.md)
-
-# WeCom Bot
-
-WeCom Bot is a quick integration method provided by WeCom that can receive messages via a Webhook URL.
-
-## Configuration
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Field | Type | Required | Description |
-| ---------------- | ------ | -------- | -------------------------------------------- |
-| token | string | Yes | Signature verification token |
-| encoding_aes_key | string | Yes | 43-character AES key used for decryption |
-| webhook_url | string | Yes | WeCom group bot webhook URL used to send replies |
-| webhook_path | string | No | Webhook endpoint path (default: /webhook/wecom) |
-| allow_from | array | No | User ID allowlist (empty = allow all users) |
-| reply_timeout | int | No | Reply timeout in seconds (default: 5) |
-
-## Setup
-
-1. Add a bot to a WeCom group
-2. Obtain the Webhook URL
-3. (To receive messages) Configure the message receiving API address (callback URL), Token, and EncodingAESKey on the bot configuration page
-4. Enter the relevant information into the config file
-
-   Note: PicoClaw now uses a shared Gateway HTTP server to receive webhook callbacks for all channels. The default listening address is 127.0.0.1:18790. To receive callbacks from the public internet, reverse-proxy your external domain to the Gateway (default port 18790).
@@ -1,41 +0,0 @@
-> Voltar ao [README](../../../../README.pt-br.md)
-
-# WeCom Bot
-
-O WeCom Bot é um método de integração rápida fornecido pelo WeCom que pode receber mensagens via URL de Webhook.
-
-## Configuração
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Campo | Tipo | Obrigatório | Descrição |
-| ---------------- | ------ | ----------- | -------------------------------------------- |
-| token | string | Sim | Token de verificação de assinatura |
-| encoding_aes_key | string | Sim | Chave AES de 43 caracteres usada para descriptografia |
-| webhook_url | string | Sim | URL do webhook do bot de grupo WeCom usada para enviar respostas |
-| webhook_path | string | Não | Caminho do endpoint webhook (padrão: /webhook/wecom) |
-| allow_from | array | Não | Lista de permissão de IDs de usuários (vazio = permitir todos) |
-| reply_timeout | int | Não | Timeout de resposta em segundos (padrão: 5) |
-
-## Configuração passo a passo
-
-1. Adicione um bot a um grupo WeCom
-2. Obtenha a URL do Webhook
-3. (Para receber mensagens) Configure o endereço da API de recebimento de mensagens (URL de callback), Token e EncodingAESKey na página de configuração do bot
-4. Insira as informações relevantes no arquivo de configuração
-
-   Nota: O PicoClaw agora usa um servidor HTTP Gateway compartilhado para receber callbacks de webhook de todos os canais. O endereço de escuta padrão é 127.0.0.1:18790. Para receber callbacks da internet pública, configure um reverse proxy do seu domínio externo para o Gateway (porta padrão 18790).
@@ -1,41 +0,0 @@
-> Quay lại [README](../../../../README.vi.md)
-
-# WeCom Bot
-
-WeCom Bot là phương thức tích hợp nhanh do WeCom cung cấp, có thể nhận tin nhắn qua URL Webhook.
-
-## Cấu hình
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| Trường | Kiểu | Bắt buộc | Mô tả |
-| ---------------- | ------ | --------- | -------------------------------------------- |
-| token | string | Có | Token xác minh chữ ký |
-| encoding_aes_key | string | Có | Khóa AES 43 ký tự dùng để giải mã |
-| webhook_url | string | Có | URL webhook của bot nhóm WeCom dùng để gửi phản hồi |
-| webhook_path | string | Không | Đường dẫn endpoint webhook (mặc định: /webhook/wecom) |
-| allow_from | array | Không | Danh sách cho phép ID người dùng (rỗng = cho phép tất cả) |
-| reply_timeout | int | Không | Thời gian chờ phản hồi tính bằng giây (mặc định: 5) |
-
-## Hướng dẫn thiết lập
-
-1. Thêm bot vào một nhóm WeCom
-2. Lấy URL Webhook
-3. (Để nhận tin nhắn) Cấu hình địa chỉ API nhận tin nhắn (URL callback), Token và EncodingAESKey trên trang cấu hình bot
-4. Nhập thông tin liên quan vào file cấu hình
-
-   Lưu ý: PicoClaw hiện sử dụng máy chủ HTTP Gateway dùng chung để nhận callback webhook cho tất cả các kênh. Địa chỉ lắng nghe mặc định là 127.0.0.1:18790. Để nhận callback từ internet công cộng, hãy cấu hình reverse proxy từ tên miền bên ngoài của bạn đến Gateway (cổng mặc định 18790).
@@ -1,41 +0,0 @@
-> 返回 [README](../../../../README.zh.md)
-
-# 企业微信机器人
-
-企业微信机器人是企业微信提供的一种快速接入方式，可以通过 Webhook URL 接收消息。
-
-## 配置
-
-```json
-{
-  "channels": {
-    "wecom": {
-      "enabled": true,
-      "token": "YOUR_TOKEN",
-      "encoding_aes_key": "YOUR_ENCODING_AES_KEY",
-      "webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
-      "webhook_path": "/webhook/wecom",
-      "allow_from": [],
-      "reply_timeout": 5
-    }
-  }
-}
-```
-
-| 字段             | 类型   | 必填 | 描述                                         |
-| ---------------- | ------ | ---- | -------------------------------------------- |
-| token            | string | 是   | 签名验证代币                                 |
-| encoding_aes_key | string | 是   | 用于解密的 43 字符 AES 密钥                  |
-| webhook_url      | string | 是   | 用于发送回复的企业微信群聊机器人 Webhook URL |
-| webhook_path     | string | 否   | Webhook 端点路径（默认：/webhook/wecom）     |
-| allow_from       | array  | 否   | 用户 ID 白名单（空值 = 允许所有用户）        |
-| reply_timeout    | int    | 否   | 回复超时时间（单位：秒，默认值：5）          |
-
-## 设置流程
-
-1. 在企业微信群中添加机器人
-2. 获取 Webhook URL
-3. (如需接收消息) 在机器人配置页面设置接收消息的 API 地址（回调地址）以及 Token 和 EncodingAESKey
-4. 将相关信息填入配置文件
-
-   注意: PicoClaw 现在使用共享的 Gateway HTTP 服务器来接收所有渠道的 webhook 回调，默认监听地址为 127.0.0.1:18790。如需从公网接收回调，请把外部域名反向代理到 Gateway（默认端口 18790）。