Start
Import from other tools
Switch in minutes. Bring your review rules over from CodeRabbit, Greptile, Cursor Bugbot, GitHub Copilot, Gemini Code Assist, Cursor rules or AGENTS.md, preview the mapping, then apply it.
You have already written down how your team wants code reviewed, in another tool's config. Forseti reads those files and turns them into its own settings: a strictness profile, ignored paths, target branches, and path-scoped team rules. Nothing changes until you have seen the mapping and applied it.
Two ways in
- Paste or upload the files in the import wizard under Settings (also offered during onboarding).
- Scan my repos: pick repositories and Forseti reads the files below from each default branch, using the app's read-only access. Up to 40 files, 200 KB each.
Either way you get a preview: the settings that would change, every rule with the file it came from, and a list of what could not be mapped and why. Pick the rules you want and apply. Only owners and admins can import, each import is applied once, and it is written to the audit log.
What is read, and how it maps
| Tool | Files | Becomes |
|---|---|---|
| CodeRabbit | .coderabbit.yaml | reviews.profile chill → quiet, assertive → thorough. path_filters excludes (!pattern) → ignored paths. auto_review.base_branches → target branches. auto_review.drafts → drafts. path_instructions → path-scoped rules. tone_instructions → a rule. |
| Greptile | greptile.json, .greptile/config.json, .greptile/rules.md | strictness 1, 2, 3 → thorough, balanced, quiet. ignorePatterns → ignored paths. rules with scope → path-scoped rules. includeBranches → target branches. Markdown → rules. |
| Cursor Bugbot | BUGBOT.md | Each section becomes a rule, scoped to the folder the file sits in. |
| GitHub Copilot | .github/copilot-instructions.md, .github/instructions/*.instructions.md | Sections become rules; applyTo globs become their scope. |
| Gemini Code Assist | .gemini/config.yaml, .gemini/styleguide.md | comment_severity_threshold LOW, MEDIUM, HIGH → thorough, balanced, quiet. ignore_patterns → ignored paths. The style guide → rules. |
| Cursor rules | .cursor/rules/*.mdc, .cursorrules | Rules, scoped by their globs. |
| Agent instructions | AGENTS.md, CLAUDE.md | Each section becomes a rule, scoped to the folder the file sits in. |
Settings with no Forseti equivalent, such as another tool's chat or knowledge-base options, are listed as unmapped rather than guessed. If two files disagree on the profile, the first wins and the preview warns you. Up to 100 rules come over per import, each up to 2,000 characters.
Where imported rules go
Imported rules join your workspace's team memory, next to the lessons Forseti learns when people dismiss findings. Each rule keeps its path scope and its source, can be switched off or deleted, and is applied to every review it matches. A workspace holds up to 500 learnings.
Guidance files Forseti already reads
Even without an import, every review reads AGENTS.md, CLAUDE.md, REVIEW.md, .github/copilot-instructions.md and your team rules file, .forseti/rules.md, from the base commit when they exist. Secrets in them are redacted first. Importing turns them into explicit rules you can see, scope and switch off one by one.
Export: take it with you
Your policies and team rules export as a .forseti.yaml and a .forseti/rules.md (or as JSON). Commit them to keep settings in the repo, share them between workspaces, or simply keep a copy: there is no lock-in.