Feature Description
Currently, the Kiro CLI only supports macOS and Linux. This creates a barrier for developers working natively on Windows who want to integrate Kiro into their standard environment without relying on virtualization or compatibility layers. A native Windows version (via a .exe or PowerShell-compatible build) would ensure feature parity across all major operating systems and streamline the onboarding process for Windows users
Use Case
I would use this to manage and deploy AI services directly from my Windows terminal (PowerShell/Command Prompt). Specifically, I want to use it for:
Local Development: Running Kiro commands natively alongside my existing Windows-based IDE and Docker setup.
CI/CD Integration: Using the CLI in Windows-based CI/CD runners or automation scripts without needing to configure a Linux subsystem first.
Seamless Tooling: Avoiding the overhead of context-switching between WSL and Windows filesystems just to execute CLI commands.
Additional Context
No response
Feature Description
Currently, the Kiro CLI only supports macOS and Linux. This creates a barrier for developers working natively on Windows who want to integrate Kiro into their standard environment without relying on virtualization or compatibility layers. A native Windows version (via a .exe or PowerShell-compatible build) would ensure feature parity across all major operating systems and streamline the onboarding process for Windows users
Use Case
I would use this to manage and deploy AI services directly from my Windows terminal (PowerShell/Command Prompt). Specifically, I want to use it for:
Local Development: Running Kiro commands natively alongside my existing Windows-based IDE and Docker setup.
CI/CD Integration: Using the CLI in Windows-based CI/CD runners or automation scripts without needing to configure a Linux subsystem first.
Seamless Tooling: Avoiding the overhead of context-switching between WSL and Windows filesystems just to execute CLI commands.
Additional Context
No response