Answer: The native Browser tool in the packaged desktop app needs no separate Node.js or Playwright installation, while an attached browser carries your existing tabs and sign-ins and should be treated as borrowed state. The agent should not navigate your active tab away or close your windows in an attached browser. Status: Check failed Entry: tool/kiro/features/managed-vs-attached-browsers Revision: 1 Digest: sha256:fb58e94ddaef481b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:38:37Z Last changed: 2026-11-13T03:38:37Z Last verified: 2026-11-16T13:06:43Z Last attempt: 2026-11-20T13:23:13Z (failed) Next check: 2026-11-20T14:23:13Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Managed browser requirement | needs no separate Node.js or Playwright installation | [1] | 2026-11-16 Attached browser state | carries your existing tabs and sign-ins | [1] | 2026-11-16 Attached browser restriction | should not navigate your active tab away or close your windows | [1] | 2026-11-16 Sources: [1] Amazon Web Services. "kiro.dev/docs/crew/features/browser/". https://kiro.dev/docs/crew/features/browser/ Role: primary. Accessed: 2026-11-16T13:06:43Z Quote: "The native Browser tool in the packaged desktop app needs no separate Node.js or Playwright installation." (Supports: Managed browser requirement) Quote: "An attached browser carries your existing tabs and sign-ins, so treat it as borrowed state" (Supports: Attached browser state) Quote: "the agent should not navigate your active tab away or close your windows" (Supports: Attached browser restriction) Published: 2026-11-14T03:24:59Z Snapshot SHA-256: b4d69234a44954bb756ee2f35a3c43e3149ab49e55e1f7b8091cbee30c5a828a (captured 2026-11-13T03:38:37Z) 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]. On this check the text of [1] was unchanged since 2026-11-13T03:38:37Z, so the values verified then were kept. Cross-check: not-available at 2026-11-16T13:06:43Z. No independent second source is configured for this entry Last successful check: 2026-11-16T13:06:43Z Last attempt: 2026-11-20T13:23:13Z (failed) Notes and limitations: Extracted automatically from a single official source (section "Managed and attached browsers"). Related: https://latestn.com/tool/kiro/features/manual-vs-legacy-hooks What is the difference between legacy manual hooks and Manual (CLI V3) hooks in Kiro? https://latestn.com/tool/kiro/features/mcp-prompts-with-arguments How do I use MCP prompts and pass arguments to them in Kiro? https://latestn.com/tool/kiro/features/merge-tangent-back How do I merge a tangent back into the main Kiro CLI chat session? https://latestn.com/tool/kiro/features/lts-differences What is different in Kiro Crew LTS compared to the regular Kiro Crew release? https://latestn.com/tool/kiro/features/manage-cloud-sessions How do I manage cloud sessions in Kiro? https://latestn.com/tool/kiro/features/manage-instances How do I manage or remove instances in a Kiro crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:44:35Z | check-failed | Extraction did not pass verification: section "Managed and attached browsers" not found in the source (the page may have been reorganized) | — 2026-11-13T03:38:37Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/managed-vs-attached-browsers/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/features/managed-vs-attached-browsers POST: https://latestn.com/dispute/tool/kiro/features/managed-vs-attached-browsers with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/managed-vs-attached-browsers?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What is the difference between managed and attached browsers in Kiro Crew? Revision 1, last verified 2026-11-16T13:06:43Z. https://latestn.com/tool/kiro/features/managed-vs-attached-browsers (accessed 2026-11-21T09:57:32Z). @misc{LatestN_tool_kiro_features_managed_vs_attached_browsers_r1, title = {What is the difference between managed and attached browsers in Kiro Crew?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/managed-vs-attached-browsers}}, note = {Revision 1; digest sha256:fb58e94ddaef481b; last verified 2026-11-16T13:06:43Z; accessed 2026-11-21T09:57:32Z} } 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/features/managed-vs-attached-browsers