Create a routine

A routine saves the prompt and session configuration for work you want to repeat. Routines currently run Engineering work. A routine shown through another agent's navigation still uses the supported Engineering execution model.

Create the routineCopy Anchor Link

1. Open Routines and choose the new-routine action or a template.
2. Give it a name that describes the repeated outcome.
3. Write the prompt, including scope, constraints, checks, and expected output.
4. Open Session configuration and select at least one repository, plus the model and supported controls.
5. Choose Schedule or GitHub as the trigger category and configure it.
6. Save and review the resulting routine.

Schedule and GitHub are mutually exclusive categories. You can run a saved routine manually using Test run without waiting for its next trigger.

Use a bounded promptCopy Anchor Link

Review changes to the API since the previous working day.
Identify missing regression coverage in the selected repositories.
Create a short report with file references. Do not modify code.

For a routine that changes code, specify the delivery boundary and expected PR behavior. A recurring prompt should be safe and useful on repeated runs, including when there is nothing new to do.

Test before relying on itCopy Anchor Link

Choose Test run, wait for queued feedback, and open the linked run or session. Verify repository selection, model access, tools, and the output. A saved configuration is not proof that the first execution will succeed.

See schedules and timezones, GitHub event triggers, and run history.