Where Does Qodo Store Review Configuration?
Qodo code review config as code: the repo .pr_agent.toml file plus IDE extension settings.
Last updated
Qodo keeps review behavior in the repository, not on your machine. The file is called .pr_agent.toml at the repo root. Sections cover review output, summary publishing, automation triggers and per tool settings.
Local IDE extensions (VS Code, JetBrains, Visual Studio) only hold login and UI state. The real rules travel with the code. That design is deliberate. Review standards stay identical for every contributor without syncing editor folders.
Where Qodo stores this, by platform
C:\Users\[Username]\Documents\GitHub\[Repo]\.pr_agent.toml
Repo root file, checked into git. Higher precedence levels (wiki, org, project) override it. Use /config in a PR comment to list effective keys.
~/Documents/GitHub/[Repo]/.pr_agent.toml
Same repo relative path on every OS. IDE login state lives in the editor settings area, but review output and visibility always resolve from this file.
~/projects/[Repo]/.pr_agent.toml
Keep only needed sections. The docs warn against copying the full example config. Minimal files survive Qodo upgrades.
Frequently asked questions
Where do I put Qodo review rules?
Keep the file minimal with only the sections you change. Qodo merges repo, project and org levels by precedence. Bloated copies break on upgrades.
Can I share Qodo config across repos?
Yes. Create a pr-agent-settings repo inside the project or group with a .pr_agent.toml at its default branch root. That applies to every repo directly under it.
Notice an outdated path? Let us know.