Kiro CLI installer conflicts with unrelated /usr/bin/q binary as Amazon Q CLI

[ambasta]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Gentoo

Kiro Version

Any/Latest

Bug Description

The Kiro CLI install script incorrectly assumes that any existing q binary on PATH is Amazon Q CLI.

On Gentoo, /usr/bin/q already exists as the q utility from portage-utils, which is unrelated to Amazon Q CLI. In that case, the installer reports:

Kiro CLI installer:

Detected existing Amazon Q CLI installation
Kiro CLI is the new version of Amazon Q CLI. Updating to latest version.


⚠️ Q CLI at /usr/bin/q does not support auto-update. Please uninstall it and rerun this script to install Kiro CLI.

The installer should verify that the discovered q executable is actually Amazon Q CLI before treating it as an existing installation or update target.

As written, the script blocks installation of Kiro CLI on systems where some unrelated program named q is installed.

Steps to Reproduce

1. Use a Linux system where /usr/bin/q exists but is not Amazon Q CLI. For example, on Gentoo:

• emerge portage-utils
• confirm /usr/bin/q is the portage-utils package

2. Run curl -fsSL https://cli.kiro.dev/install | bash
3. Observe that installation aborts with error.

Expected Behavior

The installer should confirm that the detected q binary is actually Amazon Q CLI before deciding that an existing installation is present.

If /usr/bin/q is some unrelated executable, the installer should ignore it and continue installing Kiro CLI normally, or use a more reliable detection method such as:

• checking version output for Amazon Q/Kiro-specific identifiers
• using a dedicated binary name or explicit signature instead of only q on PATH

Conversation ID

No response

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #4649: Unable to q update on Linux (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 issues relate to problems with the 'q update' command and CLI functionality on Linux systems, though the new issue focuses specifically on installer conflicts while #4649 appears to be about update functionality

[github-actions]

Thank you for your feedback! 🙏

The 👎 reaction has been noted. The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.