Create an Automation

Open Settings > Automations and choose New automation, or open the Templates tab and select a starting point. Templates and blank automations use the same editor; a template only prefills the definition.

Choose the owning workspace

The workspace is the personal account or organization that owns the automation. It determines:

• Which repositories can be selected.
• Which bot installations are eligible.
• Who can manage the definition and view its runs.
• Which AI balance pays for runs.

Choose this value carefully. The workspace is fixed after creation. To move an automation to another personal account or organization, recreate it in the destination workspace.

Organization owners and administrators can manage organization automations. Repository access alone is not sufficient to manage an organization-wide definition.

Select the bot, runtime, and model

Only ready bots installed on the selected workspace can be selected. Changing the workspace while creating an automation clears the current bot selection because that bot may not be installed on the new workspace.

Changing the runtime resets the model to that runtime's default. Use a fast model for routine classification or triage and a stronger model for long edits, multi-file reasoning, or deep review.

Automation models are hosted through Trylle. There is no automation BYOK setting in the current dashboard.

Set repository scope

Choose one of these scopes:

The repository picker is restricted to repositories owned by the automation workspace. A manual run cannot escape the saved scope, even if a caller supplies another repository ID.

Use the narrowest practical scope. Repository scope and permission scopes protect different boundaries: repository scope decides where the bot can act, while permission scopes decide what it can do there.

Add triggers

At least one trigger is required.

Select the event that best represents the work. For example, use platform/pr.opened for a first-pass review, platform/pr.updated to reconsider new commits, and bot.review_requested when the bot should act only after being explicitly requested.

Multiple triggers are additive. With selected repositories, Trylle creates a match for every selected trigger and repository combination.

Add a schedule

The schedule builder supports:

• Hourly, at a selected quarter-hour offset.
• Daily, at a selected UTC time.
• Weekly, on a selected weekday and UTC time.
• Monthly, on a selected day and UTC time.

Schedules are stored as standard five-field cron expressions and evaluated in UTC. The schedule supplements the event configuration; the editor still requires at least one trigger.

Write instructions

Instructions are required and can contain up to 16,000 characters. The automation name can contain up to 120 characters and its description up to 500.

Write instructions as an operational contract. State:

• The objective and the conditions for taking action.
• What repository context to inspect first.
• Whether the agent may edit files, comment, label, merge, or only report.
• Required checks and how to handle uncertainty.
• The expected final output.

For example:

Review the newly opened pull request for correctness and regressions.

Read the pull request description and diff, then inspect affected tests and
callers. Leave one concise review comment only when there is a concrete issue.
Do not merge, rewrite the branch, or make unrelated changes. If the change is
sound, report that no blocking issue was found.

The runtime writes these instructions into the sandbox and supplies structured trigger and repository context separately.

Restrict permissions

The Permissions field has two modes:

An automation cannot add a permission the bot does not have. Selecting narrower permissions is useful when one broadly installed bot backs several workflows with different duties.

For example, a bot might have pulls:read, pulls:comment, and files:write, while a review-only automation narrows itself to pulls:read and pulls:comment.

See Bot identities for the complete scope list and installation rules.

Save and test

The editor enables Create automation only after it has a name, ready bot, workspace, at least one trigger, a nonempty repository scope, and nonempty instructions.

After creation, select Run. The manual-run dialog asks for context that matches the configured triggers, such as a pull request, issue, comment target, push ref, or repository. Inspect the first run's target, model, status, credits, and logs before depending on automatic dispatch.

Enable, disable, edit, and delete

Existing definitions can be edited and saved in the dashboard. Their workspace remains fixed. Delete an automation from the Installed list under Settings > Automations.

Use the CLI to stop or resume new dispatches:

try automation list --account OWNER
try automation disable AUTOMATION_ID
try automation enable AUTOMATION_ID