Agentic engineering in the cloud

Sometimes work starts locally and moves into the cloud.

What begins as a quick change can turn into something bigger, take longer than expected, keep moving after you’ve stepped away, or spread across more of the codebase than you first thought.

Over the past few months, cloud execution has become a bigger part of how you can work with Kiro. Today, Kiro Web and cloud sessions are generally available, alongside cloud configuration, which makes the Kiro setup you already built available across local and cloud sessions. Together, these mean more of your engineering work can naturally run in the cloud with Kiro.

Since the preview in May, a growing number of developers have made Kiro Web part of how they work daily: from quick fixes to multi-repo migrations to work that runs while they walk away or sleep. A PR comes back with review threads, and /kiro fix clears them in one pass. A single session coordinates changes across multiple repositories, even across GitHub and GitLab. Recurring maintenance runs on a schedule with Automations, without anyone starting the same work again. Playwright reproduces browser-based bugs and validates UI changes before anything lands.

In August, we shipped cloud sessions in preview. Kiro Web always ran in a cloud sandbox, cloud sessions extend that to the CLI and IDE. A cloud session started in the CLI or IDE runs the same Kiro agent harness in the cloud instead of on your machine. Disconnect and the agent keeps going. The session stays with your Kiro account, so you can return to the same session from the browser, editor, terminal, mobile, or pick it up on a different machine entirely.

Kiro Web and cloud sessions are now generally available. All developers and teams under paid plans can build and delegate from the browser, start cloud sessions from the IDE or CLI, and pick them up from any Kiro surface including mobile. For teams, Kiro Web also supports IAM roles for sandbox access and authentication through Okta and Microsoft Entra ID, giving teams more control over access to their development environment.

We’re also introducing cloud configuration. You can now bring the Kiro setup you’ve already built locally into your cloud sessions, including steering, custom agents, skills, powers, and hooks. The personal configuration works alongside project configuration that already travels with your repository. Configuration sync can also load your cloud configuration into new local IDE and CLI sessions, while your local files stay in place and take precedence where the two overlap.

The more interesting part is what happens when you put them together.

Together, Kiro Web, cloud sessions in IDE and CLI, and cloud configuration give your engineering work more ways to run in the cloud, whether that work starts in the browser or moves to cloud execution from the IDE or CLI. Here are a few ways to try this out.

Move the next stretch of implementation into cloud execution. Work through a change in the IDE or CLI, then start a cloud session from there when the implementation is ready to run independently. The session executes in Kiro’s cloud sandbox, and you can later open that same cloud session in Kiro Web, IDE, CLI, or mobile to check progress, add direction, or continue the work.

Take a browser-facing bug from reproduction through validation. Open the work in Kiro Web and run the application in the cloud sandbox. Kiro reproduces the issue with Playwright, makes the change, and exercises the flow again to verify the fix in a real browser, instead of stopping at a proposed patch.

Push through a broad refactor or upgrade. Start a cloud session from the IDE or CLI for a framework upgrade, dependency migration, large API replacement, or test-heavy refactor. Upload your local .kiro configuration to cloud configuration, and that cloud work uses the same setup you’ve built locally while the work runs.

Carry one production change across repositories. Start the work in Kiro Web when a service or API change spans backend services, SDKs, clients, or frontends. A cloud session works across the repositories involved and carries the implementation through to the pull requests and merge requests, rather than treating each repository as an unrelated job.

Let recurring engineering work run in the cloud without turning it into a recurring manual task. In Kiro Web, create Automations for work such as dependency upkeep, issue triage, changelog updates, documentation drift, or contract checks. Each run executes in a cloud sandbox with your cloud configuration, so the same steering and setup also applies when no one is watching.

Pick up where your IDE and terminal left off, or start something new at app.kiro.dev. See the docs for more details.

You can start a cloud session from Kiro Web, the IDE, or the CLI, and resume it from any surface, including mobile. Creating and attaching from the IDE or CLI requires a recent version.

To set up cloud configuration, upload your local .kiro configuration in Settings, and enable configuration sync to pull it into new local sessions automatically. See the cloud configuration docs for how scopes and sync work.

Kiro Web, cloud sessions, and cloud configuration are available in US East (N. Virginia) and included with Pro, Pro+, Pro Max, and Power subscriptions. Cloud sessions use your shared credits with no separate charge for cloud compute.

For teams and organizations, Kiro Web, cloud sessions, and cloud configuration are accessible through the same SSO your team already uses: AWS IAM Identity Center, Okta, or Microsoft Entra ID, across the IDE, CLI, and Web. Once your administrator turns on Kiro Web and cloud sessions through a single toggle in the Kiro console, developers can start cloud sessions from any surface. See the enterprise docs for setup.

Give Kiro the next thing you’re working on and run it in the cloud at app.kiro.dev.