Using Kiro-cli on a Windows laptop requires caution. While the tool itself is a legitimate AI-powered developer assistant (heavily integrated with AWS and agentic workflows), there are significant security and stability considerations specifically for Windows users. 1. Compatibility and Native Support The most important thing to know is that Kiro-cli does not currently have a native Windows version. * The Gap: Official documentation and GitHub issues confirm support is primarily for macOS and Linux. The Risk: Windows users typically have to run it via WSL (Windows Subsystem for Linux) . Running a CLI tool that has “agentic” powers (the ability to run commands on your behalf) through a compatibility layer can lead to path-resolution errors. 2. The “Nuke” Risk (Command Hallucination) There have been documented cases of Kiro-cli causing severe system damage on Windows due to how it interprets file paths. Path Confusion: Because Windows uses backslashes (\) and Linux/WSL uses forward slashes (/), the AI can occasionally "hallucinate" or misformat a command. Recursive Deletion: In a widely reported incident, an escaping error in a tool call caused Kiro to attempt a recursive delete that hit critical system directories (like C:\Windows\WinSxS) instead of a local project folder. 3. Permission and Security Controls Kiro-cli is “agentic,” meaning it can read files and execute terminal commands. By default, it has certain “trusted” permissions that you should harden immediately: 4. How to use it SAFELY on Windows If you decide to use it, follow these “best practices” to protect your laptop: Use WSL with Isolation: Run Kiro-cli inside a WSL2 instance. Do not mount your entire C: drive to that instance. Only map the specific project folder you are working on. The “Untrust” Habit: Manually set the CLI to “untrust” file reads by adding alias kiro-cli="kiro-cli --untrust-fs-read" to your shell profile. Review Every Tool Call: Kiro will often show you a “plan” or a command it wants to run. Do not skim this. Look for any rm -rf, del, or chmod commands that look broader than they should be. Prefer the IDE: Kiro’s IDE (Desktop App) actually has native Windows support and is generally considered more stable on Windows than the CLI version. The Verdict: It is “secure” in the sense that it isn’t malware, but it is operationally risky on Windows. Use it inside a restricted WSL environment rather than trying to force it to run natively or with high-level system permissions. Q: Can I install Kiro-CLI directly on windows 11? Ans: Technically, no , you cannot install Kiro-CLI directly as a native Windows application (like a .exe or via PowerShell) as of April 2026. While the Kiro IDE supports Windows 11 natively, the CLI version is currently restricted to Linux and macOS. However, you can still use it on Windows 11 by using WSL2 (Windows Subsystem for Linux) . References Installation - IDE - Docs - Kiro https://dev.to/aws/the-essential-guide-to-installing-amazon-q-developer-cli-on-windows-lmh#:~:text=Update,Linux%2C%20or%20wsl%20for%20short . Privacy and security - CLI - Docs - Kiro Downloads “Writing can sometimes feel like shouting into a void, but your support is the echo that keeps me going. If my words have ever sparked a thought or a smile, drop a comment below. Your encouragement is the fuel that keeps my pen moving! ✍️✨” — Sanjeev A message from our Founder Hey, Sunil here. I wanted to take a moment to thank you for reading until the end and for being a part of this community. Did you know that our team run these publications as a volunteer effort to over 3.5m monthly readers? We don’t receive any funding, we do this to support the community. If you want to show some love, please take a moment to follow me on LinkedIn , TikTok , Instagram . You can also subscribe to our weekly newsletter . And before you go, don’t forget to clap and follow the writer️! Kiro-cli on Windows: Security Risks and Safety Best Practices was originally published in Artificial Intelligence in Plain English on Medium, where people are continuing the conversation by highlighting and responding to this story.