Build, delegate, and steer right from your browser

Kiro IDE is for active, local development with real-time agent collaboration. Kiro CLI is for terminal-based workflows, custom agents, and deployment pipelines. [Kiro on the web](/docs/web/) is for delegating and steering from the browser, with sessions that run in isolated cloud [sandboxes](/docs/web/sandbox/), keep going when you close your laptop, and coordinate changes across [GitHub](/docs/web/github/) and [GitLab](/docs/web/gitlab/) repos in a single session. All three modes ([autonomous](/docs/web/autonomous-mode/), [spec](/docs/web/specs/), and default) are available together in Kiro on the web. Autonomous mode and [cloud automations](/docs/web/automations/) are only available in Kiro on the web today. Use whichever Kiro interface fits the work; they work best together. [Steering files](/docs/web/steering/) and learnings carry across all three so context builds no matter where you work.

An autonomous agent works independently on tasks without requiring constant human guidance. In the context of development, agentic development means the AI can take a high-level task description, figure out the implementation plan, write code across multiple repositories, run tests, and create pull requests—all while you work on other things. The agent operates asynchronously in the background rather than requiring you to stay in an active session.

Kiro on the web is where you build, delegate, and steer development work with Kiro from your browser. Connect your GitHub or GitLab repositories, describe what you need, and Kiro writes code, coordinates changes across repos, and opens pull requests. Set up [automations](/docs/web/automations/) to run recurring work on a schedule. Available in preview for Kiro Pro, Pro+, Pro Max, and Power subscribers.

Start a session, select your repositories, and chat with Kiro about your codebase. You can iterate on code together and ask Kiro to open a pull request when you’re satisfied. Each session runs in an isolated sandbox. Turn on spec mode to shape requirements, technical design, and implementation plans before execution starts. Toggle Autonomous to have Kiro own a task end-to-end. Kiro builds a plan, coordinates sub-agents, and delivers a pull request. Or, create an [automation](/docs/web/automations/) to run work on a recurring schedule without starting a session manually.

Go to [app.kiro.dev](https://app.kiro.dev/agent), sign in, describe what you need, connect your repositories from GitHub or GitLab in Settings if your task needs it, and Kiro writes code and opens pull requests across one or multiple repos. You can chat and iterate together, or toggle Autonomous to let Kiro own a task end-to-end, use [spec mode](/docs/web/specs/) to shape the work before execution starts, or create an automation to run recurring tasks on a schedule. If your organization uses AWS IAM Identity Center, your administrator needs to enable Kiro on the web first.

Work interactively with the agent, explore ideas, talk through an approach, or work through a problem step by step. Or turn on spec mode to shape structured requirements and a technical design before code starts. You steer, it executes, you review. You can also run autonomous execution on a recurring schedule with cloud automations.

Assign a goal (implement a feature, triage a bug, or research a topic) and Kiro owns the outcome. It writes code, runs tests, diagnoses failures, and iterates until the work is done. When it opens a pull request, it monitors CI results and addresses failures. When a reviewer leaves feedback, the agent picks it up and pushes updates. You review a merge-ready result, not a first draft.

[Autonomous mode](/docs/web/autonomous-mode/) and [spec mode](/docs/web/specs/) are two separate end-to-end workflows in Kiro on the web. Autonomous mode is for delegating: describe a goal, and Kiro owns planning and execution through to a pull request for your review. Spec mode is for structuring intent first: Kiro expands your prompt into requirements, technical design, and an implementation plan, you review and approve, then execution follows the spec. Each runs independently from start to finish.

Yes. Select multiple repos from GitHub or GitLab, or you can mix GitLab and GitHub repositories in a single session. Describe the change, Kiro reads across all of them and coordinates the change, opening a pull request on GitHub and a merge request on GitLab 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.

[Connect to GitHub](/docs/web/setup/). You can assign work to Kiro directly from GitHub issues. Add the `kiro` label to an issue or mention `/kiro` in a comment, Kiro picks up the task. When Kiro opens a pull request, you can review it like any other PR, leave comments. Use `/kiro all` to address all feedback at once, or `/kiro fix` with specific instructions for a particular thread. Your review feedback also teaches Kiro, patterns you point out shape how it works on future tasks across your repositories.

Kiro on the web now works with [GitLab](/docs/web/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](/docs/web/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.

[Cloud automations](/docs/web/automations/) let you run recurring work on a schedule. Create an automation, select repos from GitHub, GitLab, or both, and set a schedule. Kiro runs it on that cadence in its own sandbox and opens pull requests with the results. Each run uses the same autonomous execution as an on-demand session.

Go to the [Automations](https://app.kiro.dev/automations) page in Kiro on the web, click Create New Automation. Give it a name, write what you want done, select one or more repos, and set a schedule (choose a preset like hourly or daily, or write a cron expression). Toggle Status to Enabled, then click Create. Kiro picks it up at the next scheduled time. You can add up to 5 schedules.

Yes. On the [Automations](https://app.kiro.dev/automations) page, each automation shows its status (Active or Inactive). Click Edit on any automation, this opens the details: name, task description, repos, schedules, and status are all editable. Edit to change anything, toggle status to Disabled to pause it, or Delete it entirely. Changes apply to the next scheduled run.

Kiro IDE, CLI, and Web share steering files and learnings, but sessions don’t carry over between interfaces right now. Start a session on whichever interface fits the work. We’re starting with autonomous mode in Kiro on the web today, Kiro IDE and Kiro CLI will add support for autonomous workflows in the coming weeks.

The sandbox provides a secure, isolated environment where the Kiro agent on the web executes tasks. Each task runs in its own sandbox with configurable access controls, ensuring your code and resources remain protected. You can configure sandbox access and behavior for your tasks from the [Agent settings](https://app.kiro.dev/settings/agent) page under Sandbox, including network access, environment variables, secrets, and connect MCP servers or Kiro Powers per sandbox.

Steering gives the agent persistent knowledge about your codebase through markdown files. Part of Kiro on the web, [steering files](/docs/web/steering/) ensure the agent consistently follows your established patterns, libraries, and standards instead of explaining your conventions in every session. The agent automatically looks for [steering files] in the `.kiro/steering/` folder at the root of your repository. These are markdown files that define your team’s standards, architecture decisions, and conventions. For detailed guidance on creating steering files, see the [steering documentation](/docs/ide/steering). Steering files work the same way across Kiro IDE, Kiro CLI, and Kiro on the web. During any session, you can steer the agent in real time by providing direction in the chat. The agent also learns from your pull request feedback and applies those patterns to future work across your repositories, see [Steering the agent](/docs/web/steering/) for details. In [autonomous mode](/docs/web/autonomous-mode), the agent asks clarifying questions upfront, your answers act as steering for that task. In [spec mode](/docs/web/specs/), the spec itself is your steering: requirements, acceptance criteria, and the technical design you approve define what gets built and how. In the [default mode](/docs/web/using-the-agent), you can steer continuously as you iterate together.

No. Kiro creates pull requests for your review and never merges automatically.

Kiro Pro, Pro+, Pro Max, and Power users. [Sign in to try it](https://app.kiro.dev/agent).

Kiro on the web uses the existing credit model. Credits are consumed regardless of which interface the work runs on (IDE, CLI, or web). No separate charge for cloud compute. Available in preview to Kiro Pro, Pro+, Pro Max, and Power users.

The agent reads `.kiro/steering` files from your connected repos and applies global instructions you set on Kiro.dev. You can also teach the agent through explicit instructions (e.g. “always wrap API calls in our retry utility”). It applies what you teach it to every session after. You can view, edit, and delete learnings on Kiro.dev.

Kiro powers are specialized packages that enhance the agent with prebuilt expertise for specific tasks. They contain curated MCP servers, steering files, and hooks that load on demand. Connect them to your sandbox on Kiro on the web. They work the same way as in the IDE and CLI.

Yes, if your organization uses AWS IAM Identity Center, your administrator needs to [enable Kiro on the web](/docs/web/identity-center/) before you can access it. Enabling applies to all users in the profile and uses the same Identity Center start URL as your existing Kiro settings. During preview, Kiro on the web is available in AWS US-East-1 (Northern Virginia) region only. MCP and other governance controls are not yet supported.

Kiro on the web is not active until you connect your GitHub or GitLab account and start a task. If you prefer not to use it, skip the setup. It does not affect your existing IDE or CLI workflows.

We do not use content from Kiro Pro, Pro+, Pro Max, or Power users that access Kiro through AWS IAM Identity Center or external identity provider. We may use certain content from Kiro individual subscribers (those that access Kiro through a social login provider or AWS Builder ID) for service improvement. You can opt out of content collection at any time using the opt-out mechanism described in our [documentation](/docs/web/data-protection/#opt-out-of-data-sharing). For more information, see [Service Improvement](/docs/privacy-and-security/data-protection/#service-improvement).

The wait is over. Kiro on the web is now in public preview for all Kiro subscribers, no waitlist. Autonomous mode is one of three modes you can choose when starting a task in Kiro on the web. If you received a notification, head to [app.kiro.dev](https://app.kiro.dev/agent) to get started.