Creating tasks

You can create tasks for the Kiro Web agent in several ways, depending on your workflow.

Navigate to app.kiro.dev to start a new session:

1. Optionally select multiple repositories when starting the session
2. Describe what you want the agent to do
3. If you didn't select repositories at the start, you'll be prompted to choose them when you ask the agent to work on something

The agent analyzes your request, breaks down the work, and begins execution.

Kiro Web can work across multiple repositories in a single task. When you assign work that spans multiple repos, it coordinates all changes and opens pull requests in each one. Only select repositories you trust, especially when mixing public and private repos, as the agent learns from and follows instructions in the repository code even if those instructions are malicious.

You'll need to connect GitHub first.

Using the /kiro command Mention /kiro in a comment on any issue to assign that specific task to the agent.

Using the Kiro label Add the kiro label to any issue. The agent starts working on the task and listens to all comments on the issue for additional context or feedback.

Tasks move through different states as the agent works:

Queued — The task is waiting to start. This happens when you've reached the limit of 10 concurrent tasks.

In progress — The agent is actively working on the task, analyzing requirements, writing code, or running tests.

Needs attention — The task needs input or the agent has a clarification question. Review the agent's message and provide the requested information to unblock the task.

Completed — The agent has finished the work and opened pull requests. Review the changes and provide feedback. Providing feedback moves the task to queued and then to in progress when a slot becomes available.

Cancelled — The task was cancelled and will not be completed. Cancelled tasks cannot be resumed.

Be specific about the outcome — Clearly describe what you want the end result to look like. Instead of "improve the login flow," say "add password reset functionality to the login page with email verification."

Describe the problem you're trying to solve — Explain the context and why the work is needed. This helps the agent understand constraints and make better implementation decisions.

Provide relevant context — Link to related documentation, examples, or existing code that should inform the implementation.

Define acceptance criteria — List specific conditions that must be met for the task to be considered complete.

Use steering files — The agent automatically looks for steering files in the .kiro/steering/ folder at the root of your repository. These markdown files define your team's standards, architecture, and conventions, ensuring the agent consistently follows your established patterns without needing to explain them in every task.