Build, delegate, and steer right from your browser

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 Web is where you build, delegate, and steer development work with Kiro from your browser. Connect your GitHub repositories, describe what you need, and Kiro writes code, coordinates changes across repos, and opens pull requests. Available in preview for Kiro Pro, Pro+, 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. Toggle on Autonomous to have Kiro own a task end-to-end, it builds a plan, coordinates sub-agents, and delivers a pull request.

Go to [app.kiro.dev](https://app.kiro.dev/agent), sign in, and connect your GitHub repositories in Settings, describe what you need, 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. If your organization uses AWS IAM Identity Center, your administrator needs to enable Kiro Web first.

Work interactively with the agent. You steer, it executes, you review. Explore ideas, talk through an approach, or work through a problem step by step. You can run custom agents or have the agent spin up sub-agents in parallel.

Assign a goal (implement a feature, triage a bug, research a topic) and the agent 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.

Yes. Select multiple repos in a single session, describe the change, and Kiro coordinates edits and pull requests across all of them.

[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 IDE is for active, local development with real-time agent collaboration. Kiro CLI is for terminal-based workflows, custom agents, and deployment pipelines. Kiro Web runs in the browser with cloud sandboxes, and is the only interface where autonomous mode is available today.

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 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 Web agent 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/agent/settings)] 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 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 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 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+, and Power users. [Sign in to try it](https://app.kiro.dev/agent).

Kiro 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+, and Power users. Your Kiro credits are consumed at half of the standard rate when using Kiro Web, and this promotional pricing is available through May 29, 2026.

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 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 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 Web is available in AWS US-East-1 (Northern Virginia) region only. MCP and other governance controls are not yet supported.

Kiro Web is not active until you connect your GitHub 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+, 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 Web is now in public preview for all Kiro subscribers for preview, no waitlist. Autonomous mode is one of two modes you can choose when starting a task. If you received a notification, head to [app.kiro.dev](https://app.kiro.dev/agent) to get started.