Answer: Enabling the WeChat interface carries risks because the iLink bot API is not a published Tencent developer product, its behavior can change without notice, and using a personal account as a bot may violate WeChat's terms of service, so accounts can be limited or banned. Group chat is unsupported, only one gateway may long-poll a given bot credential at a time, and WeCom is preferred for anything business-critical. Status: Confirmed Entry: tool/kiro/permissions-and-security/wechat-risks Revision: 3 Digest: sha256:8a9a700404fe2758 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:24Z Last changed: 2026-11-20T13:24:17Z (Behavior change: — → can change without notice) Last verified: 2026-11-20T13:24:17Z Next check: 2026-11-21T13:24:17Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of API status | not a published Tencent developer product | [1] | 2026-11-20 Behavior change | can change without notice | [1] | 2026-11-20 Terms of service risk | may violate WeChat's terms of service | [1] | 2026-11-20 Account risk | limited or banned | [1] | 2026-11-20 Group chat support | Group chat is unsupported | [1] | 2026-11-20 Poller limit | Only a single gateway may long-poll a given bot credential at a time | [1] | 2026-11-20 Recommendation | Prefer WeCom for anything business-critical | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "WeChat (Weixin) - Interfaces - Crew - Docs - Kiro". https://kiro.dev/docs/crew/interfaces/wechat/ Role: primary. Accessed: 2026-11-20T13:24:17Z Quote: "The iLink bot API is not a published Tencent developer product." (Supports: API status) Quote: "Behavior can change without notice" (Supports: Behavior change) Quote: "using a personal account as a bot may violate WeChat's terms of service" (Supports: Terms of service risk) Quote: "Accounts can be limited or banned." (Supports: Account risk) Quote: "Group chat is unsupported." (Supports: Group chat support) Quote: "Only a single gateway may long-poll a given bot credential at a time." (Supports: Poller limit) Quote: "Prefer WeCom for anything business-critical." (Supports: Recommendation) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: cdd0b17ea551c0c94e283df44a0bc5781c3e3cfed36ef37540dbbd75b1a6a78c (captured 2026-11-20T13:24:18Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:24:17Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:17Z Last attempt: 2026-11-20T13:24:17Z Notes and limitations: Extracted automatically from a single official source (section "Risks — read before enabling"). Related: https://latestn.com/tool/kiro/pricing-and-limits/cloud-sessions-limitations What are the current limitations of Kiro cloud sessions? https://latestn.com/tool/kiro/pricing-and-limits/compaction-limitations What are the limitations of compaction in Kiro? https://latestn.com/tool/kiro/pricing-and-limits/composer-limits-context-warnings What are the composer limits and context-window warnings in Kiro Crew chat? https://latestn.com/tool/kiro/permissions-and-security/vpc-iam-roles What IAM roles does Kiro need to connect cloud sessions to a VPC? https://latestn.com/tool/kiro/permissions-and-security/webex-who-can-reach Who can reach the Kiro Crew Webex bot? https://latestn.com/tool/kiro/permissions-and-security/wechat-access-policy How do I configure the access policy for the WeChat interface in Kiro Crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:17Z | changed | Behavior change: — → can change without notice | [1] 2026-11-20T13:24:17Z | changed | Account risk: Accounts can be limited or banned → limited or banned | [1] 2026-11-20T13:24:17Z | changed | Behavior stability: Behavior can change without notice → — | [1] 2026-11-20T13:24:17Z | changed | API product status: not a published Tencent developer product → — | [1] 2026-11-20T13:24:17Z | changed | API status: Unofficial surface → not a published Tencent developer product | [1] 2026-11-18T13:20:04Z | changed | Recommendation: — → Prefer WeCom for anything business-critical | [1] 2026-11-18T13:20:04Z | changed | Chat scope: DM only → — | [1] 2026-11-13T03:39:24Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/wechat-risks/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/permissions-and-security/wechat-risks POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/wechat-risks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/wechat-risks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the risks of enabling the WeChat interface in Kiro Crew? Revision 3, last verified 2026-11-20T13:24:17Z. https://latestn.com/tool/kiro/permissions-and-security/wechat-risks (accessed 2026-11-21T09:57:33Z). @misc{LatestN_tool_kiro_permissions_and_security_wechat_risks_r3, title = {What are the risks of enabling the WeChat interface in Kiro Crew?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/wechat-risks}}, note = {Revision 3; digest sha256:8a9a700404fe2758; last verified 2026-11-20T13:24:17Z; accessed 2026-11-21T09:57:33Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/permissions-and-security/wechat-risks