Schedule a Web Automation

A Kiro Web automation runs the agent on a schedule against a repository and opens a pull request with the result. It is the unattended version of a Web session, and it needs a paid plan.

When to use this

Use an automation for recurring, low-risk, well-defined work: a weekly dependency review, a nightly check that documentation matches the code, a scheduled triage pass. Do not use one for anything that should merge without a human. The output is a pull request precisely because somebody should read it.

Steps

1. Sign in to Kiro Web with a paid plan. Automations are available on Pro and above, not on the Free tier.

2. Pick the repository, or repositories, the automation will work on. Read Kiro’s warning first and take it seriously: choose only repositories you trust, because the agent follows instructions it finds in repository code.

3. Write the prompt. You have up to 10,000 characters, which is enough to be specific. Say what to check, what to change, what to leave alone, and what the pull request should contain.

   Check every endpoint in src/api/ against docs/api.md. If a
   signature or a status code disagrees, update docs/api.md only.
   Do not change code. Open one pull request titled "docs: sync API
   reference" with a bullet list of what changed and why. If nothing
   disagrees, make no changes.

4. Choose the schedule. Hourly and daily intervals are built in, and CRON handles anything else. Remember every time is UTC, so a “9am” job runs at 9am UTC regardless of where your team sits.

5. Add more schedules if the work is genuinely periodic in more than one way. An automation supports up to five.

6. Save it and let one run finish. The run happens in autonomous mode, where Kiro clarifies, plans, and executes through sub-agents in an isolated sandbox, then opens the pull request.

7. Review the first pull request properly before you trust the schedule. Adjust the prompt, not the schedule, when the output is wrong.

Check it worked

Wait for the first scheduled run and open the pull request it created. Read it as a reviewer would. The prompt above includes “if nothing disagrees, make no changes”, so a clean codebase should produce no pull request at all. An automation that opens an empty or trivial pull request every run trains everybody to ignore it.

Common problems

• Automations are not available. They need a paid plan, Pro or above. The Free tier does not include Kiro Web.
• The job runs at the wrong time. Schedules are UTC. Convert your local time before writing the CRON expression.
• The pull request changes too much. The prompt was too open. Name the files it may edit and forbid the rest.
• Nothing happens. Check the repository connection and that the automation is enabled. Kiro Web supports GitHub and GitLab.
• Credits climb quietly. An hourly automation is 24 runs a day, every day, and every run is billed work. Start daily.
• You need output on your machine, not a pull request. That is a headless CLI job instead. See Run Kiro CLI headless in CI.

Related

• Kiro Web covers autonomous mode and the browser surface.
• Start a cloud session from the CLI is the interactive equivalent.
• Credits & Pricing explains what a run costs.