[CLI] WSL OS Error 13

[nbrooks-maxex]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Windows 11

Kiro Version

1.28.2

Bug Description

After following the https://dev.to/aws/the-essential-guide-to-installing-amazon-q-developer-cli-on-windows-lmh guide I am running into the following issue after successfully logging in using the CLI error: Permission denied (os error 13)

Command which errors:
kiro-cli

I have verified that the command kiro-cli --help works correctly, and kiro-cli works up until after successful auth log in before throwing error.

Steps to Reproduce

1. Install kiro-cli on WSL
2. Run kiro-cli command and login using pro license
3. You should see the OS Error after successful login

Expected Behavior

Continues after login to terminal chat session.

Conversation ID

No response

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #6199: After enabling an experimental feature in Windows/WSL environment, running kiro-cli chat gives "Failed to sync resources for active agent: IO Error: Failed to create store" error and hangs. (85% similar)
• #4694: Using WSL2 Terminals but Kiro is confused and has executePwsh errors all the time (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both report WSL-specific kiro-cli errors that occur after authentication/login steps, with similar failure patterns in Windows/WSL environment