Quickstart
Set up the hosted GitHub App and verify a first review without enabling code changes.
Use the hosted App and the portal. No local CLI is required. This is a setup checklist, not a guarantee that a fresh account can complete every step: GitHub access, installation permissions, saved settings, and model availability must all be checked.
1. Review App access before installing
Open the Autofeat GitHub App. Choose Only select repositories and a disposable test repository for your first review. You may need a GitHub account or organization administrator to approve installation.
Check GitHub's actual permission prompt before consenting. The public App metadata checked on October 24, 2026 reports much broader requested permissions than code review alone needs, including organization and enterprise write permissions. It reports Checks read, not Checks write. These are App metadata, not proof of the effective permissions granted to your installation. Do not assume the App requests only code-review access; ask your administrator to review the requested access before installing.
2. Open the portal and check the connection
Sign in with GitHub at portal.autofeat.app. Choose the personal account or organization that owns the test repository. Check Connections and the repository's setup status. Installing the App grants repository access; it does not by itself turn on automatic reviews.
If access or setup is blocked, stop at the reported reason. A successful sign-in or deployment alone does not prove a working review connection.
3. Save review settings
Open Settings for the selected account or organization. To request automatic reviews, set Review to Automatic, choose All eligible pull requests, choose whether to review new changes, and save. Reload to confirm the saved status. Repository overrides and the trusted default-branch settings file can change the effective settings.
Keep fixes, implementation, approval, and merging off while checking review. Enabling review does not enable those actions. Draft, fork, trusted-actor, pause, and budget restrictions still apply.
4. Verify one review on a test pull request
Open a small text-only pull request in the installed test repository. An
eligible automatic review should publish comment feedback with a summary and
findings. Confirm it belongs to Autofeat and the current changes, not an older
review or another bot. If a prior attempt failed on the same changes, request
@autofeat full review in that pull request after addressing the reported
blocker.
Automatic comment review is separate from a required merge check. It does not approve the pull request, run your tests, or create repository merge rules. A managed required check additionally needs Checks write permission and administrator setup; do not assume it is available from the public App's Checks read permission. Keep independent repository tests and human approval.
If no useful review appears, check setup, saved review selection, permissions, model availability, and the reported failure. Do not interpret silence or an incomplete response as approval. After testing, remove the App's access to the disposable repository if it is no longer needed.
Billing is not part of activation
Paid checkout and customer subscription management are not currently available.
Changing autonomy.dry_run does not buy or activate a subscription. Budgets and
model-provider costs are separate from customer billing. See
Budgets and billing.
The retired hosted engine's sticky-state comment, journal branches, label setup, and neutral dry-run checks are not acceptance criteria for this hosted review path.