Using Rennet
Rennet drafts a local branch, GitHub pull request, or GitLab.com merge request into boards you can read, then turns what you raise into a review, a work order, or a change request. Start with the tour, then follow the guide for the change in front of you.
Start here
Section titled “Start here”- Install Rennet downloads the desktop app for macOS or Windows and gets it to the first-run welcome.
- Getting started walks the whole loop: add a project, read the boards, stage asks, take an exit.
- Install a coding harness sets up Claude Code, Codex, or both for Dual Harness reviews.
- The onboarding tour explains the contextual coach marks shown after setup: one at a time, skippable, and replayable from Help.
- Connect to GitHub signs Rennet into GitHub for pull request reviews.
- Review a GitHub pull request covers a teammate’s pull request and the review you post on it.
- Remote access connects another device to a Rennet daemon.
Understand the product
Section titled “Understand the product”- Product and vision explains what Rennet is for.
- Common questions covers models, credentials, data, and forges.
A teammate’s pull or merge request becomes one review on its forge, posted under your name. On your own branch the same asks become a work order: a coding agent runs the round, you read its report and the regenerated boards, and when nothing is left to ask, Rennet pushes the branch and opens a GitHub pull request or GitLab.com merge request for the repository’s effective push remote.