Agent

Automations

Run the agent automatically on schedules, GitHub events, or manual triggers.

Automations let you configure the agent to run automatically in response to events or on a schedule. Each automation has a prompt, target repositories, and one or more triggers.

Creating an Automation

  1. Go to Agent > Automations in the dashboard
  2. Click New Automation
  3. Configure the automation:
    • Name — A descriptive name for the automation
    • Prompt — The instruction the agent will execute
    • Repositories — Which repos the automation targets
    • Model — Agent model tier (Max, Mid, Fast, or Auto)
    • Triggers — When the automation should run

Triggers

Schedule Triggers

Run the agent on a recurring schedule:

  • Daily — Runs at a specific time each day
  • Weekly — Runs on selected days at a specific time

GitHub Event Triggers

Run the agent in response to GitHub activity:

TriggerDescription
PR CreatedA new pull request is opened
PR MergedA pull request is merged
PushCode is pushed to a branch
Comment CreatedA comment is posted on a PR
Review SubmittedA code review is submitted

Filters

Narrow down when triggers fire:

  • Branch patterns — Only trigger on branches matching a regex (e.g., ^feature/.*)
  • Label filters — Only trigger on PRs with specific labels

Manual Triggers

Click Run on any automation to trigger it immediately. This creates an agent session with the automation's prompt and settings.

Templates

Paragon provides preset automation templates for common workflows. Browse templates when creating a new automation to get started quickly.

Viewing Runs

Each automation tracks its execution history. Click an automation to see:

  • Recent runs with status (completed, failed, running)
  • Links to the agent sessions created by each run
  • Timestamps and duration

Examples

Nightly QA review:

Review all changes pushed today. Flag security vulnerabilities, missing tests, performance regressions, and potential bugs. Open a PR with fixes.

Trigger: Daily at 9:00 AM

Auto-fix on review:

Address the requested changes in this review. Follow the reviewer's feedback exactly.

Trigger: Review submitted with "changes requested"

Test generation on new PRs:

Generate unit tests for all new or modified functions in this PR. Ensure edge cases and error paths are covered.

Trigger: PR created

Regression check on merge:

Run the full test suite against this merge. If any tests fail, investigate the root cause and open a fix PR.

Trigger: PR merged