Skip to main content
Automations let you run Replicas agents automatically, on a schedule or in response to events from your connected GitHub repositories. Use them for nightly maintenance, scheduled audits, automatic responses to PR activity, and any other workflow you want to run without a human in the loop.
Automations and the public API are the only sanctioned channels for programmatic use of Replicas. Driving the dashboard, Slack, Linear, GitHub, or CLI from scripts is prohibited under our Terms of Service.

​
How it works

Each automation has:
  • A prompt the agent will receive when the automation runs.
  • One or more repositories (or a repository set) the agent will work against.
  • One or more triggers that decide when the automation fires.
When a trigger fires, Replicas creates a fresh workspace, sends the prompt to the configured coding agent, and tracks the run as an execution you can review in the dashboard.

​
Triggers

Two trigger types are supported today:

​
Cron triggers

Run an automation on a recurring schedule defined by a standard cron expression. The minimum interval is 60 minutes between runs.

​
GitHub triggers

Run an automation in response to events from your connected GitHub repositories. For example, when a pull request opens, when a workflow run finishes, or when an issue is filed. You can optionally filter a GitHub trigger to a specific subset of repositories.

​
Plan availability and limits

PlanMax automationsOrg executions / hourPer-automation executions / hourMin cron interval
HobbyNot available———
Developer520560 minutes
TeamUnlimitedUnlimitedUnlimited60 minutes
EnterpriseUnlimitedUnlimitedUnlimited60 minutes
The Hobby plan does not include access to Automations.

​
Reliability

Automations include a circuit breaker: if an automation fails 5 times in a row, it is automatically disabled to prevent runaway behavior. You can re-enable it from the dashboard once the underlying issue is fixed. Every execution is recorded with its status (pending, creating, running, completed, or failed) and any error message.

​
Billing

Automation workspaces are metered separately from your seat subscription, at the same rate as API usage. See Billing for rates, rounding, and plan details.

​
Managing automations

Automations can be created, updated, listed, and triggered from the dashboard, the CLI, or via the same REST API and API key as the rest of the public API. You can also fire an automation on demand from the dashboard or CLI to test that it works without waiting for the next scheduled or webhook-driven run.