Skip to content

Conversation

@fefedimoraes
Copy link

Description

Amazon Q Developer CLI is no long being actively maintained and will only receive critical security fixes. It is now available as Kiro CLI, a closed-source product.

This change replaces current Amazon Q integration with Kiro CLI.

Related Issue(s)

Screenshots

Kiro CLI selection Kiro CLI session integration

@github-actions github-actions bot added the size/m Medium PR (<50 lines changed) label Dec 12, 2025
## Description

Amazon Q Developer CLI is no long being actively maintained and will
only receive critical security fixes. It is now available as Kiro CLI, a
closed-source product.

This change replaces current Amazon Q integration with Kiro CLI.
@fefedimoraes fefedimoraes changed the title fix(cli): Replace amazon_q with kiro fix(cli): replace amazon_q with kiro Dec 12, 2025
@knmac
Copy link

knmac commented Dec 19, 2025

Is this really needed? Please correct me if I'm wrong, but simply adding kiro to opts should work, right?

Minimal setup for reproducibility:

return {
    "folke/sidekick.nvim",
    opts = {
        cli = {
            tools = {
                kiro = { cmd = { "kiro-cli" } },
            },
        },
    },
}

@fefedimoraes
Copy link
Author

While you're correct in terms of how this can be added as opts, we still need to either replace or remove support for Amazon Q.

From this latter perspective, this is still needed. This change takes the conservative approach of replacing Amazon Q with its new iteration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/m Medium PR (<50 lines changed)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: AmazonQ is now kiro. Cannot find amazon_q

2 participants