Work in quiet hours

In your quiet hours, Iterada works on the product by itself: it tests the product through its real screens in a browser, the way a customer would use it, reads the code, and reviews how its agents work. What it is sure how to fix, it fixes in a session you can read; the rest waits for you under Artifacts.

Switch quiet hours on in Settings, under Automation. Set their hours on the Quiet hours workflow in Agent factory. Shares, intensity and whether each of your tasks is iterative or singular stay in Agent factory: quiet hours themselves are the Quiet hours workflow, and the choice per task is on its row under Tasks.

Switch it on#

1. Open Settings, then Automation, and switch on Enabled under Quiet hours.

2. Open Agent factory, then Workflow, choose Quiet hours and press its start on the canvas to pick the hours.

3. Fixes start by themselves. To have every finding wait for you instead, open Agent factory, choose Issue fixes in the workflow dropdown, press the On event start on the canvas and choose Only ones you press Fix now on. With that choice, Platform tidying pauses too. The steps of Issue fixes are yours to change too: once changed, every issue's session runs them.

Say what matters most#

Each task of the Quiet hours workflow is a step with its own Share of quiet hours. The three built in are:

• How the agent works and remembers: tidies project memory and the instructions agents read.

• Codebase: dependencies, refactors, tests that protect nothing, release notes and these docs.

• Product quality: the product used through real screens, looking for what is broken or inconsistent.

Each slider runs from nothing to 200%, its middle mark an ordinary share. Only the proportion counts: sliders at the same height share quiet hours evenly, and a slider at zero beside raised ones gets none of it. The path from the start to each task says what its share comes to.

A task you put in quiet hours - press Quiet hours on its row under Tasks - is Iterative or Singular, chosen on that same row. An iterative task works pass after pass for its share, like the built-in ones. A singular task gets one pass per quiet hours, before the iterative ones, and no share. The agent that saved the task picks the one that suits it - singular for a report or a measurement, iterative for work that goes through one area at a time - and you can change it there. Quiet hours need at least one iterative task, so the last task with a share cannot be made singular. Every task leads to Report issues, which files what they found as issues, and Write report comes last: once the tasks of quiet hours are done it writes the quiet hours report. Press the start of quiet hours to set its Intensity: Efficient leaves what you are forecast to use before each limit resets, Max keeps nothing back and spreads what is left of each limit over the quiet-hours runs before it resets, and Easy spends only what would otherwise expire unused. When your subscriptions give quiet hours more agent time than they have hours, up to three tasks run at the same time so they can use it - never two passes of the same task, and each is told what the others are working on so none repeats their work. Platform tidying and the report run alone. Press Save and quiet hours follow it. To shape quiet hours of your own, choose New, then Runs in quiet hours, save it and press Make main: it runs once a test run has shown the workflow plans quiet hours exactly as Iterada does.

When it runs#

In Agent factory, press the start of the Quiet hours workflow on the canvas. With Worked out from your usage under Quiet hours, Iterada picks the six hours you are least active, in your own time zone. Choose Set by you to pick From and To yourself, as long or short as you like. These are saved as soon as you change them.

How much work quiet hours hold depends on what is left of your agents' plans and the intensity. Iterada estimates it before quiet hours start, from every subscription your agents use. Each login of each agent is counted on its own, and a task runs on the one with the most time left, so one subscription's spare time is never taken from another's. The line under the hours says what the next quiet hours come to, and marks a subscription that has not reported its usage yet as assumed. A free model your project already uses takes over the rest of quiet hours once the plan time is spent.

To start right away - before a holiday, say - open your Account page and press Start quiet hours now.

After quiet hours#

• Fixes are sessions under Automated in the session list, each merged the way your project merges. Once a fix Iterada started is live, its session moves to Archived by itself and the finding is marked resolved, unless you wrote in it; restore it to carry on. A session you opened with Fix now is yours: it stays until you archive it, or Platform tidying does.

• The quiet hours report is at the top of Artifacts, headed Latest quiet hours report: every finding quiet hours touched, a sentence or two each, what changed and why the rest was not fixed, and anything your tasks published. How quiet hours ran says what went wrong, how many minutes each subscription had set aside and used, and how each task's passes went. To stop it, remove Write report from the Quiet hours workflow and press Save.

• Findings whose fix would have a side effect wait for you under Needs you in Artifacts, each with what was expected, what happened, how to fix it and a screenshot. Everything else is fixed by itself.

• Platform tidying, the first task of the Quiet hours workflow, has archived the sessions whose work is merged, live and quiet for a week, each with a note saying why, and dismissed each new issue that reports the same problem as another one, naming the one kept. Restore a session to carry on, or reopen an issue under Dismissed to bring it back. To stop it, remove its step from the Quiet hours workflow and press Save.