Introducing Kiro Web

Not every task starts in an IDE. You spot a bug in a PR review, a teammate flags an issue in Slack while you are between meetings, or you want to kick off a migration before you head out for the day.

At re:Invent we announced our vision for autonomous software development. Since then, we have been working closely with customers to iterate on the experience. From your feedback it became clear that autonomy should not be a separate product — it belongs in the core Kiro experience. We are starting with Kiro Web, and Kiro IDE and Kiro CLI will add support for autonomous workflows in the coming weeks.

Today we are launching Kiro Web in preview for all paid subscribers — Pro, Pro+, and Power. Go to app.kiro.dev, tell Kiro what you want to build, and it writes code, coordinates changes across your repositories, and opens pull requests. Kiro Web credits are 50% off until May 29, 2026 so you can explore how Kiro can help you build.

Start a session, select your repositories, and tell Kiro what you need. Chat about implementation approaches, ask questions about your codebase, iterate on the code together, and ask Kiro to open a pull request when you are satisfied. Kiro brings context from your repositories, web search, and learnings from previous code reviews to every response.

When you have a task you want Kiro to own end-to-end, toggle on Autonomous. Kiro asks clarifying questions upfront, builds a plan, and coordinates specialized sub-agents to plan, code, and verify changes. When the work is complete, you get a pull request — not a status update.

Kiro Web can work across multiple repositories in a single session. Select the repos you want to work with, describe the change, and the agent coordinates edits and pull requests across all of them. Update a shared library and migrate the services that depend on it. Add an API endpoint in the backend and update the frontend client to call it. One conversation, multiple repos, coordinated PRs.

• Assign work from GitHub — Add the kiro label to an issue or mention /kiro in a comment, and Kiro picks up the task.

• Review like any other PR — When Kiro opens a pull request, leave comments with feedback. Kiro addresses them and pushes updates. Use /kiro all to address all reviewer comments at once, or /kiro fix with specific instructions to focus on a particular thread.

Kiro Web reads steering files that define your team's coding conventions, architecture patterns, technology preferences, and testing standards. You can set these up in the Kiro's agent settings — upload files directly or import them from a GitHub repository. Kiro also picks up steering files from the .kiro/steering/ folder in your repositories automatically. Steering files work the same way across Kiro IDE, Kiro CLI, and Kiro Web. If you already have them set up, they carry over automatically.

Kiro learns from your feedback during sessions or on PRs. Comments like "always use our standard error handling" shape how it works on future tasks across all your repositories. Between steering files and cross-repo learnings from your code reviews, Kiro gets better the more you work with it.

Every task runs in its own isolated sandbox — a fresh environment that is created for the session and destroyed when it ends. The agent clones your repositories into the sandbox and executes the work with access only to resources you have explicitly permitted. Sessions are isolated from each other and from your local environment, so one task cannot affect another. When Kiro finishes its work, it can open a pull request, and you review the changes, leave feedback, and merge when ready.

You control what the sandbox can reach — network access, MCP tool configurations, and base image settings — from the settings page. If your organization uses AWS Identity Center, administrators can enable or restrict Kiro Web access for their organization without affecting other Kiro clients. See the Identity Center guide for details.

1. Go to app.kiro.dev and sign in

2. Connect your GitHub account in Settings

3. Select repositories and start a session

If your organization uses AWS Identity Center, your administrator will need to enable Kiro Web before you can access it. See the Identity Center guide for details.

We are bringing specs to Kiro Web — iterate on your next feature’s requirements and design, then hand it off to the autonomous agent to implement. Autonomous workflows are also coming to Kiro IDE and Kiro CLI in the coming weeks, so you can work the same way regardless of where you start.

Try it on a real task, something from your backlog, a bug you have been putting off, a set of tests you have been meaning to write, and tell us how it goes. Kiro Web is in preview, and your feedback shapes what we build next.