Configure automation and integrations

Use Settings → Integrations to connect accounts and Settings → Automation inside a repository to schedule reviews. These are separate choices: a connection gives Kensa access to a provider; automation decides when and what to review.

Connect only the accounts you need

The Integrations catalog groups source-control and tracker providers. Add a connection with the authentication method that its form supports, provide a host or email when requested, then use Test to verify it. You can keep more than one connection for a provider type and select a default connection where the UI offers it.

Connection methods and required fields differ by provider and host. A successful connection does not mean every provider supports the same pull-request, tracker, or publishing behavior. See the provider reference before treating a catalog entry as a feature-parity promise.

Schedule an auto-review deliberately

Automation is configured per repository that has remote pull requests. Choose the PR criteria, then set a schedule such as an interval or selected times. The editor can preview the matching PRs before a run, and Run now uses the same selection rules.

Choose the review mode, agents, skills, provider settings, retry behavior, and an auto-publish policy for the schedule. Publishing is a separate switch with a severity filter; when it is off, a scheduled review does not post findings. Deep scheduled reviews need a local clone. Only one auto-review batch runs at a time, so an already-running batch must finish or be stopped before another starts.

Safe operating routine

1. Test the source-control connection before arming a schedule.
2. Preview the PR selection after changing labels, authors, or review state filters.
3. Start with publishing disabled; enable it only after you have verified the review recipe.
4. Review paused or failed batch status before changing retry or quota-related settings.

Next step

Privacy and data boundaries