New in Kiro Web: Build with Spec, GitLab, and more - Kiro

Back to all posts<br>We launched Kiro Web in preview last month, extending Kiro to more of the places you already work. From your browser, you can explore an idea and shape a change with Kiro, then open a pull request without setting up a local environment first. Or hand a task off in Autonomous mode, and Kiro takes it end to end. Either way, a single session can coordinate one change across several GitHub repositories. Since launch, we have shipped a round of workflow improvements. This update brings two capabilities developers have asked for. The structured spec workflow now runs in the browser, and Kiro Web now works with GitLab, including sessions that span both GitLab and GitHub.<br>Specs on to the web

A spec puts the important decisions first. Rather than going from prompt to code directly, you work with Kiro to shape what to build, how it should work, and what to leave out before any code is written, when ambiguities and conflicts are cheapest to catch. Because implementation starts from a spec you have reviewed, the pull request reflects what you approved rather than a first guess you redirect after the fact. Kiro Web supports the same spec types as the Kiro IDE, so you can write a Feature Spec, work through a Bugfix Spec, or use Quick Plan when the work is well understood and you want requirements, technical design, and tasks in a single pass.<br>Kiro produces documents for each spec. The requirements capture what to build, the design describes the approach, and the task list breaks the work into discrete steps. You review them right in the browser and chat with Kiro to refine them, whether that means adding a requirement, rethinking part of the design, or adjusting how the work breaks down. When the spec is ready, you can have Kiro work through all the tasks or specific tasks in the sandbox, and it opens a pull request when the work is done. If you want to keep the spec or continue it elsewhere, you can download the documents to your local machine.<br>Work with GitLab from Kiro Web

Kiro Web now works with GitLab in addition to GitHub. You connect GitLab with a personal access token, then add a GitLab project to a session and ask Kiro to do the work. Kiro clones the project into its sandbox, makes the changes, and opens a merge request on your behalf. It can also inspect merge requests and issues when you ask, so you can list and read them without leaving the session.<br>Kiro Web has coordinated changes across several repositories in one session from the start. What is new is that those repositories no longer have to live on the same provider. You can mix GitLab and GitHub repositories in a single session, and Kiro reads across all of them and coordinates the change, opening a merge request on GitLab and a pull request on GitHub as appropriate for each. That matters when a change touches a shared library in one place and the service that depends on it in another, even when those projects live on different providers.<br>Recent updates

We have also shipped several improvements since launch. You can now start a session without connecting a repository first, describe what you want, and add a repository later if you need one. You can stop Kiro mid task, see progress while your workspace spins up, and read relative timestamps on messages. The view also stays where you are reading instead of jumping, so longer runs are easier to follow. We also made it clearer which network mode your sandbox is using, increased the default sandbox disk to 128 GB, and cleaned up the layout on smaller screens.<br>Try it today

Kiro Web is in preview at app.kiro.dev for Kiro Pro, Pro+, and Power subscribers. To go deeper, see the Specs and GitLab guides, and follow the Web changelog to see what ships next.

{PREVIOUS}<br>Introducing Kiro Pro Max ($100/mo): more credits, less guesswork

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences