Your team's settings

With a workspace, repositories and a model, Gryndel is ready to review. These are the next things most teams adjust.

How thorough and how chatty

In Repositories, choose for each repository (or for everyone, under Organization settings):

• Review mode: single pass, verified (a second pass checks every finding, which is slower but leads to fewer false alarms), or agents (several specialists, then verification).
• Comment level: how many suggestions and nitpicks Gryndel posts besides real issues.
• Severity: the minimum severity to post, and which severity fails the commit status.
• Exclusions: paths to skip, such as generated files.

Settings in Organization settings can be locked, so repositories can't change them.

On GitHub

Suggest and apply fixes works on GitLab only. On GitHub, Gryndel suggests fixes but doesn't commit them; people apply the ones they agree with using GitHub's Commit suggestion.

Your team's rules

Add your conventions on Rules & learnings, for example "new endpoints need an integration test". Teammates can also teach Gryndel from a merge or pull request with @gryndel learn: <what to remember>.

Gryndel also reads guideline files from your repositories, such as AGENTS.md or .gryndel/rules.md. To share settings across many repositories, put a .gryndel.yaml in a repository called gryndel-config:

• GitLab: a project called gryndel-config in the group. It applies to every project in that group and its subgroups, top group first.
• GitHub: a repository called gryndel-config on the account (<account>/gryndel-config). It applies to every repository of the account. Include it in the App's installation, or Gryndel can't read it.

Your operator can choose a different name for it. Each repository's settings drawer has Preview, which shows the levels that apply. See How settings combine.

Your team

Members come from GitLab or GitHub automatically; nobody needs inviting.

	GitLab	GitHub
Members	Everyone with access to the group	The organisation's members, or the owner of a personal account
Admins by default	Owners and Maintainers	Organisation owners (needs the App's Members permission)
Add or remove people	Change their access to the group in GitLab	Change their membership of the organisation on GitHub

Everyone else is a viewer. To change someone's role in Gryndel, use Members.

Keep an eye on it

• Reports shows which findings people accepted or rejected, by repository, severity and agent.
• Costs shows what reviews cost, by provider and model.
• System health shows whether GitLab, GitHub and the models can be reached.

Pausing or turning off

Comment @gryndel pause to stop reviews on one merge or pull request, or pause a repository in Repositories. On GitLab, turning a repository off also turns its webhook off; on GitHub it changes nothing on GitHub, and the App stays installed until you remove it there. To stop every review in the workspace, use Turn reviews off on the Workspace page.