How It Works
- Reply to a Macroscope review comment requesting a fix (or ask from Slack)
- Macroscope creates a new branch and applies the fix via an AI agent
- Macroscope opens a PR. If triggered from a review comment, the base is the feature branch. If from Slack, the base is your main branch.
- GitHub Actions run on the new PR. If any fail, Macroscope attempts to fix them automatically.
- If the base is a feature branch and auto-merge is enabled, Macroscope will auto-merge once all checks pass. PRs against your main branch always require manual merge.
Auto-Merge Control
Override the default auto-merge setting per fix:- “Fix it for me and auto-merge”: auto-merges once checks pass, even if auto-merge is off by default.
- “Fix it but don’t auto-merge”: opens the PR but leaves it for manual merge.
Branch Protection
Macroscope operates like any other developer. It never writes directly to main branches. Branches follow the patternmacroscope/*/**.
If you have branch protection rules that apply to all branches (like “Require a pull request before merging”), you may need to exclude macroscope/*/** branches.
GitHub Actions
Macroscope uses your existing GitHub Actions and CheckSuites to validate fixes. To reduce latency or cost on Macroscope PRs, you can add branch-specific rules formacroscope/*/** to limit which actions run.