Skip to main content
This guide covers Automation configuration in detail. For a quick walkthrough, see Create your first Automation.
Automations work best with projects. A project provides the Dev Container configuration, dependencies, and environment settings that your Automation runs against. We recommend setting up a project before creating Automations.

​
Create an Automation

  1. Navigate to Automations in the left panel.
  2. Click New Automation.
  3. Choose Start from scratch or select a pre-configured template.
Automations page

​
Basic settings

  • Name: short, descriptive name (e.g., “Weekly dependency updates”)
  • Description: what the Automation does
  • Run as: your user (manual workflows) or a service account (scheduled/event-driven)
Basic configuration

​
Trigger type

​
Guardrails

Control execution limits to prevent Automations from running excessively:
  • Max concurrent executions: simultaneous runs
  • Max total executions: total allowed per run
Maximum values depend on your plan. See Plans and limits for per-plan caps and Guardrails for details.

​
Steps

Steps execute in sequence within the same environment. Each step can access files, environment variables, and context from previous steps.

​
Step types

TypeUse when
PromptFlexible tasks requiring agent judgment: “analyze and improve”, “update based on context”
CommandDeterministic operations: npm test, docker build
Pull requestSubmit changes for review after making modifications
ReportExtract structured data from the execution: test coverage, dependency counts, build metrics

​
Example workflow

Step 1 (Prompt):    "Upgrade all dependencies to their latest versions"
Step 2 (Command):   npm test
Step 3 (PR):        Create pull request with summary
Guidance:
  • Use prompts for context-aware tasks that vary by repository.
  • Use commands for predictable, repeatable operations.
  • Combine both: commands for validation, prompts for intelligent changes.
Steps configuration

​
Save and edit

Click Save to create the Automation. All settings can be modified after creation.
Pull request triggers require a webhook. Select an existing webhook or create a new one from the trigger configuration. See Pull request triggers for details.

​
Next steps