Integrations · Available
CodeRabbit
Detected and deferred to, today. Run both without two bots arguing on the same pull request.
Pull request #731
Handle expired workspace tokens
+ if (token.expiresAt < Date.now()) {
+ await rotateWorkspaceToken(token)
+ }Coexistence first, replacement only if you want it
CodeRabbit is recognised by sender identity, and when it is active on a pull request developerz.ai treats its comments as signal rather than as something to answer. That rule is not a setting — no bot-on-bot loops is one of the product's non-negotiables, and it applies to every known reviewer bot. If you do decide to consolidate, our review lane reads your existing .coderabbit.yaml, so the switch does not start with rewriting configuration.
Recognised by identity
CodeRabbit's sender is matched explicitly, so its comments are read as signal and never trigger a reply from us.
Your config still applies
The review lane reads an existing .coderabbit.yaml, or you can use the native review: block in .maintainer.yml.
Compare before you switch
The review page shows how the two dispositions line up, so consolidating is a decision you make on evidence.
Next step
See the review lane
What our reviewer flags, what it ignores, and how a CodeRabbit config maps onto it.
See AI code reviewPut a fleet of AI developers to work
Bring your own keys and your own boxes, drop a .maintainer.yml, and let the loops run — audited end to end. Access is invite-only.