# Kiro makes coding-agent sessions portable across the IDE, CLI, web and mobile Kiro Web and cloud sessions are generally available on paid plans, turning the coding agent from a process tied to one machine into a resumable cloud session that can keep running after disconnect and be picked up from the IDE, CLI, browser or mobile. The workflow shift is continuity rather than another model upgrade: one Kiro agent session can outlive the laptop that started it. Cloud configuration can also carry agent setup across environments, although enterprise governance is not identical between local and web/cloud surfaces. - Status: Active - Published: 2026-09-07T15:04:53+12:00 - Updated: 2026-09-07T15:04:53+12:00 - Categories: Artificial Intelligence, Web Development, AI Agents, AI Coding, Developer Tools - Tags: agent sessions, AI agents, cloud development, Coding agents, Kiro - Canonical HTML: https://beyondthe.news/dossiers/kiro-cloud-sessions-ga-cross-device-coding-agent ## 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. ## Key details - Kiro Web and cloud sessions became generally available September 3, 2026. - Cloud sessions can be started from the IDE or CLI and resumed across CLI, IDE, web and mobile. - A cloud session keeps running when the originating local machine disconnects. - Cloud Configuration can synchronize `.kiro` configuration into cloud sessions and optionally new local sessions. - Cloud sessions are currently available in US East (N. Virginia). - They are included with Pro, Pro+, Pro Max and Power subscriptions and use shared credits. - Enterprise administrators have a separate cloud-session enablement control. - Some organization-wide settings do not apply identically to Kiro Web/cloud sessions. ## Builder takeaways - Treat cloud sessions as remote execution: review repository access, secrets, network tools and generated side effects before delegating long-running tasks. - Use cloud configuration deliberately rather than assuming every local file or governance setting will be mirrored. - For teams, verify the Kiro Web governance limitations before enabling cloud sessions organization-wide. - Design long-running agent jobs around commits, pull requests and resumable checkpoints so cross-device continuity remains auditable. - Budget shared credits for unattended sessions because cloud compute is not billed separately but agent work still consumes the subscription pool. ## What to watch - Expansion beyond US East (N. Virginia). - Whether Kiro closes the governance gaps between local, IDE and web/cloud sessions. - More granular controls for synced MCP servers, models, secrets and customer-managed encryption keys. - Usage data showing whether persistent sessions shift coding agents toward scheduled and unattended maintenance. - Changes to credit economics as longer-running cloud sessions become common. ## Uncertainties - Kiro’s claims about developer usage and productivity are first-party and workload dependent. - GA describes product availability, not a guarantee that every enterprise control is feature-equivalent across surfaces. - Shared-credit economics can vary substantially depending on model choice and task duration. ## Sources - [Agentic engineering in the cloud](https://kiro.dev/blog/agentic-engineering-in-the-cloud/) — Kiro · primary product announcement · 2026-09-03T00:00:00+12:00. GA announcement, cross-surface continuity, availability, plans and credit model. - [Session Dashboard, Configuration Panel, and Cloud Sync](https://kiro.dev/changelog/cli/2-21/) — Kiro · primary changelog · 2026-09-01T00:00:00+12:00. CLI session management and cloud-configuration synchronization details. - [Governance](https://kiro.dev/docs/enterprise/governance/) — Kiro · primary documentation. Enterprise cloud-session enablement and governance boundaries. - [AWS Identity Center for Kiro Web](https://kiro.dev/docs/web/identity-center/) — Kiro · primary documentation. Regional requirements and settings that do not carry into Kiro Web.