Groups are flexible organizational containers — teams, departments, or technology stacks. They sit between global and project settings, providing shared guardrails, genome traits, and expert preferences to all member projects.
no-public-s3
infrastructure · critical
LOCKEDrequire-mfa
process · critical
LOCKEDaudit-logging
process · high
LOCKEDmax-file-changes: 10
quality · medium · overridable
testing: vitest
testing · medium
NEWstyle: prettier
content-pattern · low
NEWmax-file-changes: 15
← overrides global (10)
locked rules pass through
cannot override
min-coverage: 80%
testing · project-specific
NEWmax-file-changes: 20
← overrides group (15)
EFFECTIVE RULES · api-gateway
Group-level guardrails apply to all member projects. Override global rules or add group-specific constraints. Projects inherit and can further customize.
Define conventions once at the group level. All member projects inherit them automatically — consistent patterns across related codebases.
Enable specific expert agents for the group. A frontend team always gets accessibility reviewers. A platform team always gets Terraform and Kubernetes specialists.
Set default workflow configurations for the group. Member projects start with sensible defaults that match your team's process.
Settings flow from Global → Group → Project → Job. Each level can add rules, and exempt non-locked parent rules. Security-critical global rules stay locked.
Request access to see how Groups structure multi-team engineering with shared standards.
Request Early Access