Answer: The Kiro Crew Teams integration is limited to 1:1 personal chat only, with no team channels, group chats, or @mention handling. It also has no token-by-token streaming, no emoji reactions, and Markdown tables are converted before sending. Status: Confirmed Entry: tool/kiro/pricing-and-limits/teams-limitations Revision: 2 Digest: sha256:44fa745113ae0a90 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:16Z Last changed: 2026-11-17T13:45:55Z (markdown tables: — → Markdown tables are converted before sending) Last verified: 2026-11-20T13:24:08Z Next check: 2026-11-21T13:24:08Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of chat scope | 1:1 personal chat only | [1] | 2026-11-20 streaming | No token-by-token streaming | [1] | 2026-11-20 emoji reactions | No emoji reactions | [1] | 2026-11-20 markdown tables | Markdown tables are converted before sending | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Teams - Interfaces - Crew - Docs - Kiro". https://kiro.dev/docs/crew/interfaces/teams/ Role: primary. Accessed: 2026-11-20T13:24:08Z Quote: "1:1 personal chat only — no team channels, group chats, or @mention handling" (Supports: chat scope) Quote: "No token-by-token streaming — typing indicator shown, final answer delivered in one message (chunked if long)" (Supports: streaming) Quote: "No emoji reactions — a steered message is acknowledged with a short message instead" (Supports: emoji reactions) Quote: "Markdown tables are converted before sending (a monospace grid while it fits, one card per row otherwise), since Teams shows pipe tables literally" (Supports: markdown tables) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 3ee94b69c0c19cc2e383d605ee466b350e3b5a19581cb8efb0394a0a58694012 (captured 2026-11-20T13:24:05Z) 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:08Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:08Z Last attempt: 2026-11-20T13:24:08Z Notes and limitations: Extracted automatically from a single official source (section "Limitations"). Related: https://latestn.com/tool/kiro/pricing-and-limits/terminal-limits What are the limits of the terminal in Kiro's web agent? https://latestn.com/tool/kiro/pricing-and-limits/track-credit-expiration How do I track credit expiration in Kiro Enterprise credit pooling? https://latestn.com/tool/kiro/pricing-and-limits/usage-beyond-plan-limits What happens in Kiro when I exceed my plan limits? https://latestn.com/tool/kiro/pricing-and-limits/queue-steering-limitations What are the limitations of queue steering in Kiro CLI? https://latestn.com/tool/kiro/pricing-and-limits/subagent-limits-capacity What are the limits and host capacity for Kiro Crew subagents? https://latestn.com/tool/kiro/pricing-and-limits/supported-currencies-payment-methods What payment currencies and payment methods are supported by AWS Inc. for Kiro purchases? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:45:55Z | changed | markdown tables: — → Markdown tables are converted before sending | [1] 2026-11-17T13:45:55Z | changed | emoji reactions: — → No emoji reactions | [1] 2026-11-17T13:45:55Z | changed | streaming: — → No token-by-token streaming | [1] 2026-11-17T13:45:55Z | changed | chat scope: — → 1:1 personal chat only | [1] 2026-11-17T13:45:55Z | changed | Streaming: No token-by-token streaming → — | [1] 2026-11-17T13:45:55Z | changed | Adaptive Cards: No Adaptive Cards / tappable buttons → — | [1] 2026-11-17T13:45:55Z | changed | Chat scope: 1:1 personal chat only → — | [1] 2026-11-13T03:39:16Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/pricing-and-limits/teams-limitations/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/pricing-and-limits/teams-limitations POST: https://latestn.com/dispute/tool/kiro/pricing-and-limits/teams-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/pricing-and-limits/teams-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the limitations of the Kiro Crew Teams integration? Revision 2, last verified 2026-11-20T13:24:08Z. https://latestn.com/tool/kiro/pricing-and-limits/teams-limitations (accessed 2026-11-21T10:04:17Z). @misc{LatestN_tool_kiro_pricing_and_limits_teams_limitations_r2, title = {What are the limitations of the Kiro Crew Teams integration?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/pricing-and-limits/teams-limitations}}, note = {Revision 2; digest sha256:44fa745113ae0a90; last verified 2026-11-20T13:24:08Z; accessed 2026-11-21T10:04:17Z} } 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/pricing-and-limits/teams-limitations