Web changelog

Workflows are now available as an opt-in feature in Kiro Web cloud sessions. They run reusable, multi-step agent plans in the background while you continue working in the parent conversation.

Describe the outcome and how much structure or review you want. Kiro proposes a Workflow, names its steps, agents, and effort, and launches it in the background. Ask Kiro to investigate a codebase for risks, deliver a feature with independent reviewers, or make a failing build green. Each step runs in its own agent session, which you open from the Workflows panel; it sees only what earlier steps hand it, and the run pauses when a step needs your input.

Start with one of three bundled recipes: investigate for read-only investigation, feature-pipeline for staged feature delivery, or publish-pr for opening a pull request and handling review feedback.

Learn more ->

Once a Workflow is running, open Workflows from the side panel in the parent conversation and select a run to inspect its nested steps. Select a step to see its status, elapsed time, agent, model, effort, and tool activity. You can Answer this step when it pauses, Steer the agent while it runs, or Message this step's agent for other guidance. You can also pause, resume, or stop a run. After a failure, you can retry the failed steps. Summary, Files, and Artifacts also share the side panel to keep outcomes and evidence in the session.

Learn more ->

Open Settings > Workflows and turn on Enable workflows. Use Upload workflow for one .workflow.json, .workflow.yaml, or .workflow.yml recipe, or use Configuration Sync to import a complete .kiro/workflows/ folder. Turning Workflows off hides its surfaces and prevents new launches.

Learn more ->

Kiro Web now lets you choose reasoning effort for supported models, and folds reasoning and tool activity into a collapsible timeline so the agent's response stays in view. Document attachments hold up across long sessions, sessions reconnect when you return to a background tab, and Reviews and What's new are easier to find.

For models that offer reasoning levels, choose a lower effort for quick edits or a higher one for work that needs more care. The selector appears only when the model supports it, holds its place while levels load, and supports keyboard navigation. Learn more ->

Consecutive reasoning steps and tool calls now fold into one collapsible block, keeping the agent's response in view. Expand it for the details. Startup actions group under a single Session setup row. Steering, Configuration Sync, and task lists present their results in a more readable form. Learn more ->

Uploading a sixth document partway through a long session no longer blocks new attachments. The five-document limit applies to each message instead of accumulating across the session, so earlier uploads no longer block later messages. Affected sessions recover on the next message without a reset or restart.

A Kiro Web tab left in the background now reconnects when you return and replays session activity that arrived while you were away. This restores the latest session state after sleep or a network change without requiring another message. Learn more ->

Build, delegate, and steer development work with Kiro Web from your browser. Explore ideas collaboratively, shape work with Specs, or hand off a task end to end. Learn more ->

Configuration Sync can now carry your cloud configuration into new local Kiro IDE and CLI sessions. On the Configuration Sync page, enable Apply your cloud configuration to local sessions to load your cloud Steering files, custom agents, Skills, Powers, and Hooks when a session starts. Cloud content stays in the cloud and does not replace files in your local .kiro directory. Learn more ->

You no longer have to start from the default branch. When you select a GitHub or GitLab repository for a session, choose the branch to work from right in the selector. The agent clones that branch and builds on it.

New sessions now get a descriptive, agent-generated title based on what you're working on, replacing the generic default. The title appears in the session header and sidebar as soon as it's ready. Rename a session yourself and that name sticks. The agent never overwrites a title you've set.

Keep a growing session list manageable by grouping related sessions. Create a group in the sidebar or on the sessions page, move sessions in and out, and rename or dissolve a group at any time.

The repository selector now shows a Recent section at the top once you've used a couple of repositories, so getting back to one you were just working in takes a click instead of scrolling the full list. Recent repositories are grouped per provider and drop out of view while you search.

Your team can now access Kiro Web through the Okta or Microsoft Entra ID integration you already use. After an administrator configures access, users only need to sign in. This capability is available with Kiro Pro and above subscriptions.

Add https://app.kiro.dev/signin/oauth to your existing Kiro OpenID Connect (OIDC) application. In Okta, add another Sign-in redirect URI. In Microsoft Entra ID, add the URI under Single-page application, separate from the Mobile and desktop application redirects. Then enable Cloud Sessions (Preview). You can enable Cloud Sessions and API key generation independently.

Learn more: Okta -> | Microsoft Entra ID ->

You can now bring your personal .kiro configuration into Kiro Web. From Settings > Configuration Sync, upload local Steering, custom agents, Hooks, Skills, Powers, or MCP settings for use in every cloud session. Learn more ->

Select or drag one supported top-level folder, such as skills/ or agents/, from your local .kiro directory. Kiro checks each file against its cloud copy before uploading. New files are selected by default, while updates that replace cloud content require your input. Steering files and MCP servers include a side-by-side comparison.

Uploaded items appear on their matching settings pages, where you can view, edit, download, or delete each one. Steering, Skills, Agents, Hooks, and Powers each have their own page under Settings, and uploaded MCP servers appear with your MCP server settings. Catalog Powers are installed by name, and custom Powers upload as text files.