Kiro Web's default mode is collaborative. You work with the agent interactively, iterating on a problem together. The agent helps you think through approaches, write code, and open pull requests when you're ready.
For tasks where you want the agent to own the outcome end-to-end, see autonomous mode.
For structured planning, where you want requirements, a design, and a task list before any code is written, use Specs.
For reusable multi-step orchestration that runs in the background while the main conversation stays available, use Workflows. A workflow can coordinate isolated agents, loops, reviews, and external waits; inspect or message its individual steps under Workflows in the session details.
If you don't select repositories upfront, you'll be prompted to choose them when you ask the agent to work on something.
In the default mode, you drive the conversation. Chat with the agent to:
The agent has access to web search, context from your repositories, and learnings from previous code reviews to provide informed responses.
Consecutive reasoning steps and tool calls appear in one collapsible block while the agent works. Expand the block to inspect the details.
Startup actions are grouped under Session setup. Steering, Configuration Sync, and task lists present their results as readable summaries.
When you're happy with the changes, ask the agent to open a pull request. The agent creates a feature branch, commits the changes, and opens a PR with a description of what was done.
You can continue to provide feedback on the PR. The agent responds to your comments and pushes updates.
When a session has reviews, open Summary, where Reviews appears alongside Files and Artifacts. Expand Reviews to see the list in place; selecting Files or Artifacts switches to that tab instead.
Select a review to inspect its details, including its changed files, commits, and review comments. Back returns to the review list.
You can work across multiple repositories in a single session. When you select repos, the agent clones them into its sandbox and can coordinate changes across all of them.
Each session has a single conversation thread. You can:
To work on a different topic, start a new session.
If your machine sleeps or your network changes while a session is in a background tab, returning to the tab reconnects the session and replays any activity that arrived while you were disconnected. You don't need to send another message to refresh the session. A session whose connection stayed open has nothing to replay, so returning to it changes nothing.
As your list of sessions grows, you can sort them into groups to keep related work together. Groups are optional; a session that isn't in a group stays under Ungrouped.
Before starting a session, select Add to group in the composer to choose an existing group or create one. You can also organize sessions later from the sidebar or Sessions page.
In the sidebar's Sessions panel, switch to the group view and select Create group to add one. Name it and confirm, and the empty group appears right away, before you add any sessions to it.
To move a session into a group, open the session's menu and select a group under Move to group, or select New group to create one and move the session in a single step. To take a session out of a group, open its menu and select Remove from group; it returns to Ungrouped.
From a group's menu you can:
On the Sessions page, you can act on several sessions at once. Select the sessions you want, then use Move to group to move them all into the same group. To narrow the list instead, use Filter by group to show only the sessions in the groups you pick; filtering works on its own and doesn't require selecting any sessions first.
Kiro generates a title for each session from your task and shows it in the session header and the sidebar. If you rename a session yourself, Kiro keeps your title and does not overwrite it with a generated one.
Sessions expire after 90 days, at which point chat messages and logs are deleted. Pull requests, merge requests, code changes, and conversations on GitHub or GitLab are not affected.
Kiro Web can search the web to access current information in real-time, enabling up-to-date answers about topics that may have changed since the model's training data was created.
Web search is designed to not reproduce meaningful chunks of text and works with publicly accessible pages. Web searches are logged in the session with citations, so you can see what sources the agent referenced.
Working with the agent