PARAS MADAN
All writing

Latest in AI

Amazon Q Developer for GitHub Is Closing: Plan the Kiro Handoff

New Amazon Q Developer GitHub App installs stopped November 18. Check the January support deadline, Kiro access requirements and repository migration steps.

If your team uses Amazon Q Developer inside GitHub, do not use the IDE retirement date to plan that integration's replacement. The GitHub App has its own, earlier deadline.

AWS's current documentation says new installations stopped on November 18, 2026, and support for the GitHub App ends on January 30, 2027. It points customers toward Kiro and the Kiro GitHub App for similar capabilities. Read the GitHub-specific notice.

I would treat this as a workflow migration, not a simple rename. Repository access, task triggers, billing eligibility and review expectations all deserve a separate check.

Keep the two retirement dates separate

AWS's broader end-of-support announcement gives April 30, 2027 for Q Developer IDE plugins and paid subscriptions. It says Q Developer in the AWS Management Console and first-party AWS experiences, including chat applications, is not affected by that sunset. Read the broader announcement.

For a team inventory, list the actual surface beside its owner. “We use Q” is too vague to establish a deadline.

Start with repositories where the GitHub App performs recurring work. Note any issue labels, slash commands, review habits or onboarding documents that assume it will remain available.

Check Kiro eligibility before promising a replacement

Kiro Web's setup guide requires a paid Pro-or-higher subscription for social-login users; the free tier does not include Web. With AWS Identity Center, an administrator must enable Cloud Sessions, and the service requires a Kiro Profile rather than a Q Developer Profile. Check the setup requirements.

Those are access prerequisites, not evidence that an existing Q entitlement transfers automatically.

I would ask the account owner to confirm the intended subscription, identity route and spending controls before the engineering team changes its routine. A successful personal trial does not establish that everyone in the organization can use the same workflow.

Connect the app and the user deliberately

Kiro's GitHub integration shows a repository only when both the app and the individual GitHub user have access. Users need write permission to assign tasks. The app is installed once per organization or account, with repository scope controlled by the organization owner. Read the repository access rules.

My pilot would authorize one low-risk repository rather than all repositories. Use an existing maintainer as the first operator, but also test the intended day-to-day user. Otherwise, an administrator's broader access can hide an onboarding problem.

Keep the old and new access inventories separate until the migration is complete.

Verify issue triggers and organization setup

Kiro documents two ways to assign work from an issue: the kiro label or a /kiro comment. An already-installed organization may still need its owner to finish setup. Until then, comments, labels, reviews or app-created pull requests may not work even though repositories are visible in Kiro Web. See the integration instructions.

This is why I would test the entry point your team actually uses. Opening a repository in the web interface is not enough if engineers normally delegate work from GitHub issues.

Update your internal examples only after that path works. Do not assume old commands or labels are translated automatically.

Run one complete task before retiring the old workflow

My proposed acceptance task is a small change with clear tests and a human reviewer. Follow it from the issue through the generated branch, pull request, test results and review feedback.

Record who owns the task, which account created the pull request and whether existing repository protections still behave as intended. These are suggested checks, not tests I have performed against Kiro.

Before removing the old app, account for unfinished work and replace any documentation that still points engineers toward it. Then review whether its repository permissions are still needed.

The goal is not merely to install a successor before January 30. It is to preserve a useful, understood development workflow without quietly broadening access or discovering subscription requirements during the cutover.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help developer-tool teams explain product changes and migrations through clear technical writing and storytelling.

Book a 30-minute call.