-
Notifications
You must be signed in to change notification settings - Fork 187
Description
Before opening, please confirm:
Operating System
latest Mac
Kiro Version
0.11.63
Bug Description
Environment:
Kiro IDE (replicated on latest)
macOS
zsh
Workspace with Python venv active
Description: When Kiro's agent executes bash commands (git, cp, sed, python3, etc.), three issues occur simultaneously:
False error reporting — The UI displays "An unexpected error occurred, please retry" even when the command succeeds. For example, git push completes successfully (remote confirms receipt), but the UI shows an error.
Output garbling — Terminal output has characters doubled at the start of lines. Examples:
ccd instead of cd
ssed instead of sed
ggit instead of git
ffind instead of find
Incorrect exit code — Exit Code: -1 is reported for commands that succeed. A successful command should return Exit Code: 0.
Impact on User Experience:
User cannot trust whether a command succeeded without manually verifying
Creates an unnecessary feedback loop: user asks "did that work?" → Kiro confirms it did → wastes 1-2 additional prompts per command
Over a long session (50+ commands), this adds up to significant wasted tokens and time
The cwd parameter in bash execution appears to trigger the garbling (the cd command prepended to every execution gets doubled)
Painpoint: Ugly output, causes unnecessary user confusion, and wasted prompts/tokens
Steps to Reproduce
Steps to Reproduce:
Open a workspace with a git repo
Ask Kiro to run git status via the agent (or any specific change)
Observe: output is correct but garbled, exit code shows -1, and "unexpected error" may appear
Expected Behavior
Expected Behavior:
Successful commands show Exit Code: 0
No "unexpected error" message when output is correct
Terminal output is not garbled/doubled
User can trust the result without follow-up verification
Workaround: Ignore the error display and exit code. Check the actual output content — if it shows the expected result (e.g., git push shows "main -> main"), the command succeeded.
Conversation ID
6e646df5-b26f-4da5-afed-47546680f19f
6e646df5-b26f-4da5-afed-47546680f19f
6e646df5-b26f-4da5-afed-47546680f19f
6e646df5-b26f-4da5-afed-47546680f19f
Additional Context
