Skip to main content
Once a project is linked to a GitHub repository, Aether can react to repository events and inbound replies without you opening the dashboard. These behaviors are per-project settings on the project’s linked repo; each is off by default and you opt in.
This page covers event-driven automation. Aether also has scheduled automations — recurring prompts that run on an interval, daily, or weekly schedule — managed through the Automations API. Those are a separate feature from the GitHub-triggered behaviors below.

​
PR reviews

Aether can open a review task that inspects a pull request and leaves its review on GitHub. A project’s PR review trigger controls when this happens automatically: Draft PRs are skipped. Each review targets the exact head commit from the triggering event, not the moving branch tip. You can also trigger a review on demand: comment aether review on a pull request. This requires the project’s PR-review comment trigger to be enabled, and the commenter must be authorized on the repo.

​
Auto-fix CI failures

When auto-fix CI is enabled for a task’s project, a failing check suite on the task’s PR sends the agent a follow-up describing the failure so it can push a fix. With auto-fix disabled, the failure is recorded on the task but no follow-up is dispatched. Follow-ups are deduplicated per PR head commit, so a single failing head triggers at most one fix attempt.

​
Auto-rebase

When auto-rebase is enabled, Aether follows up the task to rebase its PR branch when GitHub reports the branch is behind its base or has merge conflicts with the base. As with CI fixes, rebase follow-ups are deduplicated per head commit and only fire while the PR is open.

​
PR comment follow-ups

Comments on a tracked PR can drive the agent:
  • Comments and reviews on a PR the agent authored feed back as follow-ups when auto-fix PR comments is enabled for the task.
  • Comments on a PR the agent reviewed feed back when respond to comments is enabled.
Only comments from authorized actors (the repo’s collaborators, or the Aether app itself) are acted on; others are ignored.

​
Reply by email

Task notification emails are sent from a per-task reply address of the form reply+<token>@<domain>. Replying to that email delivers your message to the task as a follow-up — the agent resumes with your reply as its next input. The token is signed and resolves to exactly one task, so no task ID or dashboard visit is needed.
Inbound email replies require the deployment to have an inbound email domain and provider configured. Where it is unset, notification emails are sent without a reply address.

​
Where these settings live

PR review trigger, comment trigger, auto-fix CI, auto-fix PR comments, and auto-rebase are configured per project (and inherited by its tasks). See Projects and the GitHub integration guide for connecting a repo.