Migration
autofeat covers the CodeRabbit workflow with repo-controlled policy, hard budget ceilings, and a merge path. This page compares the two feature by feature and shows the switch-over. autofeat does not do chat threads in pull requests or issue-tracker exports; it reviews, fixes, gates, and merges.
| Feature | autofeat | CodeRabbit |
|---|---|---|
| PR review triggers | LiveThe autofeat:go label, or fully automatic review when a PR opens and when new pushes land (review_automations). Reviewer-request routing is planned. | Automatic review on open and push; @coderabbit review command. |
| Comment commands | Planned@Autofeat review, review incremental, fix, merge, pause, resume, status. Collaborator or owner comments only; replies post as comments. | @coderabbit commands, including chat-style follow-ups. |
| Inline comments | PlannedA bounded findings comment with severity per finding today; walkthrough summary plus inline diff comments with actionability labels planned. | Walkthrough summary with inline comments on the diff. |
| Review instructions file | Planned.autofeat/review.md project instructions plus review.ignore_paths globs in .autofeat/config.yml. | .coderabbit.yaml with instructions and path filters. |
| Auto-fix PRs | Planned@Autofeat fix turns actionable findings into commits on the PR branch, then re-runs the gate inside the same budget. | AI commits pushed to the pull request branch. |
| Auto-merge | Livemerge_mode auto with auto_approve, required green checks, and branch-protection checks. autofeat can drive a PR all the way to merge. | Review only; no merge. |
| Provider BYOK with KMS | LiveVercel AI Gateway by default for every agent. OpenAI-compatible providers use keys stored in KMS-backed Secret Manager, injected by the sandbox egress firewall; the agent uid never holds the real key. | BYOK on the self-hosted offering. |
| Self-hosted option | LiveYes: a GitHub Actions path with pinned workflow SHAs, or the full hosted stack on your own GCP project. | Yes: self-hosted deployment. |
Live means shipped on main and exercised on the hosted deployment. Planned means in flight on a branch, not yet available; this page is updated when each item lands.
01
Install autofeat-axc on the repositories you choose, open the portal Setup page, and create the four autofeat:* labels plus the state ruleset.
02
Move review instructions to .autofeat/review.md and path filters to review.ignore_paths when those land; today, port budgets, merge behavior, and review automations through the portal Settings page.
03
dry_run defaults to true: the first reviews are rehearsals with a neutral check conclusion. Compare the findings comment against your CodeRabbit baseline on the same pull requests.
04
Set dry_run: false, keep merge_mode: stop_before_merge, and let autofeat set autofeat:ready. Move to approve_only or auto only when the gate behavior earns it.