AI bash tool fails with Exit Code -1 in WSL, while manual terminal commands work

[NagaokaTaishi]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Windows 11 + WSL2 Ubuntu

Kiro Version

0.12.333

Bug Description

After updating to Kiro IDE 0.12.333, terminal command execution from the AI chat/bash tool started failing consistently in a WSL environment.

The integrated terminal itself works correctly when commands are typed manually, but commands executed by Kiro's AI tool fail with Exit Code: -1. The command output is not captured properly; only the shell prompt appears.

Environment:

• OS: Windows 11 + WSL2 Ubuntu
• Shell: /bin/bash
• bash path: /usr/bin/bash
• Project path: ~/project
• Remote status: WSL: Ubuntu

What works:
Manual commands in the Kiro integrated terminal work correctly.

Examples:

pwd
# ~/project

which bash
# /usr/bin/bash

ls -l /bin/bash
# /bin/bash exists

bash -lc 'echo KIRO_TERMINAL_OK'
# KIRO_TERMINAL_OK

Shell integration also appears to be enabled:

echo "$TERM_PROGRAM"
# kiro

echo "$VSCODE_SHELL_INTEGRATION"
# 1

declare -p PROMPT_COMMAND
# declare -- PROMPT_COMMAND="__vsc_prompt_cmd"

What fails:
When the AI chat tries to execute commands using the bash tool, all commands fail with Exit Code: -1.

Examples of failed commands:

git status
whoami
ls
pwd

The output only shows the shell prompt instead of the actual command output.

Expected behavior:
The AI bash tool should execute commands in the active WSL terminal and capture stdout/stderr correctly, the same as manual execution in the integrated terminal.

Actual behavior:
The AI bash tool fails with Exit Code: -1 and does not capture the command output, even though the integrated terminal itself is working.

Troubleshooting already attempted:

• Restarted Kiro
• Reloaded Window
• Killed all terminals and opened a new terminal
• Recreated ~/.kiro-server
• Verified bash exists and works
• Verified Shell Integration is enabled
• Removed a local alias that was shadowing the WSL Kiro CLI
• Confirmed kiro --locate-shell-integration-path bash returns a valid shell integration path
• Downgraded Kiro

Result:
After downgrading from Kiro IDE 0.12.333 to 0.12.318, the AI bash tool started working again. git status executed successfully from the AI chat.

This suggests the issue is likely a regression in Kiro IDE 0.12.333 related to AI bash tool execution or WSL terminal output capture.

Steps to Reproduce

1. Install Kiro IDE 0.12.333 on Windows.
2. Open a project inside WSL2 Ubuntu using WSL: Ubuntu.
3. Confirm that the integrated terminal works manually.
4. In the AI chat, ask Kiro to run a simple command such as:

git status

or

pwd

5. Observe that the AI bash tool fails with Exit Code: -1 and does not capture the command output.

Expected Behavior

The AI bash tool should execute commands in the active WSL terminal and correctly capture stdout, stderr, and the exit code.

For example, when asking the AI chat to run:

git status

Kiro should return the normal git status output, the same as when the command is run manually in the integrated terminal.

Conversation ID

No response

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #9496: execute_bash tool reports exit code 1 for all commands after Kiro IDE update (92% similar)
• #9483: execute_bash tool returns empty stdout on all commands mid-session (92% similar)
• #9501: Kiro 1.0.0 — agent shell commands (execute_pwsh) no longer run in a visible, interactive terminal (88% similar)
• #9512: execute_pwsh tool unavailable after Kiro update (85% similar)
• #8992: Shell tool cannot handle interactive stdin input on macOS (kinit, ssh-add, etc.) (85% similar)
• #8090: Kiro CLI Shell Tool — Environment Isolation Regression (85% similar)
• #7491: fsWrite and executeBash drop parameters after context compaction (85% similar)
• #7431: [Bug] Shell tool fails on Windows native kiro-cli 2.0 (85% similar)
• #6717: executeBash: Terminal hangs after successful command, agent receives "Signal was cancelled" (85% similar)
• #9499: Shell execution produces character-by-character echo and incorrect exit code since v1.0.0 (82% 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 execute_bash tool failing with exit code -1 after Kiro IDE update, with commands working manually but failing through AI bash tool

[github-actions]

This issue has been automatically closed as it appears to be a duplicate of #9496.

If you believe this is incorrect, please comment on this issue and a maintainer will review it.