What changed
Kiro Web and cloud sessions moved to general availability on September 3, 2026. A session started from the IDE or CLI can execute in Kiro’s cloud sandbox, continue after the local client disconnects and later be resumed from another Kiro surface including the CLI, IDE, web or mobile. Kiro also added cloud configuration so a developer can upload their `.kiro` setup and reuse configuration across cloud and optionally new local sessions. Cloud sessions are currently available in US East (N. Virginia), are included with Pro, Pro+, Pro Max and Power subscriptions, and consume shared Kiro credits without a separate cloud-compute charge.
Why it matters
Persistent agent execution changes coding tools from interactive assistants into delegated workers. Long migrations, review-fix loops and scheduled maintenance no longer need the developer’s laptop to stay online, and switching devices does not require starting a new conversational job. That convenience also moves source code, configuration and tool execution across a cloud boundary, so teams need to understand which local settings and enterprise controls actually follow the session.
The agent session now outlives the local client
Kiro’s cloud agent harness runs in a sandbox rather than on the originating machine. Disconnecting the IDE or CLI does not terminate the job, and the same session can later be resumed from another supported surface.
Configuration can follow the session
Cloud Configuration lets developers upload their `.kiro` setup for cloud sessions and optionally apply cloud-managed configuration to new local sessions. The configuration surface includes items such as agents, MCP servers, steering, skills, powers and hooks depending on scope.
GA removes the preview boundary but not regional limits
Kiro Web and cloud sessions are now GA for paid plans, but current documentation places cloud execution in US East (N. Virginia). Teams with data-location requirements need to treat that as an architectural constraint rather than assume global execution.
Enterprise governance is not perfectly symmetric
Organizations can control whether cloud sessions are enabled, but Kiro’s documentation says some shared administrator settings do not apply to Kiro Web, including certain MCP, model and customer-managed-key settings. Teams should review the web/cloud governance table rather than assuming local policy automatically transfers.
Cloud compute is folded into the existing credit model
Kiro says cloud sessions use shared subscription credits and do not carry a separate cloud-compute charge. That simplifies billing, but delegated workloads still consume the same finite credit pool as interactive agent work.