context.repos field in greptile.json, but instead of pointing one repo at others, you define a group once and every member shares context with every other member.
Clusters are useful when a set of repos are tightly coupled, for example a service, its SDK, and its shared types, where a change in one often can’t be reviewed well without the others.
Creating a cluster
Open Repo Clusters
On the Greptile dashboard, go to Custom Context → Repo Clusters. Managing clusters requires admin access.
A repository can belong to only one cluster at a time. If a repo is already claimed, you’ll see which cluster it’s in when you search for it.
Suggested clusters
Greptile suggests clusters for you based on shared contributors, meaning repositories the same people have committed to over the last 90 days. Suggestions appear with a confidence indicator; click Use this to create the cluster, or Discard to dismiss it.How clusters affect reviews
When Greptile reviews a PR in a clustered repo, it clones the other members read-only and makes them available to the reviewer, exactly likecontext.repos. Across both sources, Greptile reads up to 7 related repositories per review, and repos listed explicitly in context.repos take priority.