Skip to content

Automations

Automations let you trigger AI sessions based on events, enabling hands-off workflows that respond to your development process.

An automation consists of:

  • Trigger - An event that starts the automation (e.g., a new GitHub issue)
  • Action - What happens when triggered (e.g., start a session with a specific agent)
  • Configuration - Settings that customize behavior (e.g., which repos, labels, models)

When the trigger event occurs, Cheffed automatically starts a session with your configured agent and context.

Event (GitHub Issue) → Automation → Session Started → Agent Works → Results
  1. An event occurs (e.g., someone opens a GitHub issue with a specific label)
  2. Cheffed detects the event via your connected integrations
  3. The automation’s trigger conditions are evaluated
  4. If conditions match, a new session is created
  5. The agent receives context from the event and begins working
  6. Results can include code changes, PRs, comments, or reports

Trigger on new GitHub issues labeled bug. The agent analyzes the issue, searches the codebase for relevant code, and posts a comment with initial findings.

Trigger on new pull requests. The agent reviews the changes, checks for common issues, and provides feedback as PR comments.

Trigger on issues labeled automate. The agent reads the issue, implements the requested feature, and creates a pull request.

Trigger on merged PRs that touch specific files. The agent updates relevant documentation based on the code changes.

React to new issues or issue updates:

  • Filter by repository
  • Filter by labels (e.g., only bug or enhancement)
  • Access issue title, body, and metadata in the session

React to PR events:

  • New PRs opened
  • PR updates
  • Filter by base branch, labels, or files changed

Currently, automations support one action type:

Creates a new AI session with:

  • Agent/Prompt - Which agent template to use
  • Model - Which AI model powers the session
  • Context - Information passed from the trigger event
  • Repository - Optionally clone a repo into the session

Track your automations on the Automations page:

  • View all configured automations
  • See execution history
  • Monitor success/failure rates
  • Debug failed executions