December Changelog
Macroscope
Macroscope
Engineering Team

December Changelog

We shipped a bunch of improvements to Macroscope last month. Here's an overview.

Code Review

Fix It For Me

Macroscope can now fix bugs for you — automatically. Our code review catches bugs other tools miss. But finding bugs is only part of the problem. Someone still has to fix them. Fix It For Me closes that loop.

When Macroscope flags an issue in your PR, reply with "fix it for me." Macroscope creates a branch, commits the fix using state of the art coding models, opens a PR, and automatically merges it back into your feature branch once all checks pass. If any checks fail, Macroscope will attempt to self-heal by looking at logs and making subsequent commits. Read more about how it works.

In GitHub, Macroscope identifies a bug and makes a suggestion, the PR author replies 'Fix it for me,' and Macroscope automatically creates, verifies, and merges the fix.

Better Bug Detection With Opus 4.5

We released a new version of Code Review powered exclusively by Claude Opus 4.5. Compared to our previous code review pipeline, the new pipeline has significantly improved performance with 40% higher recall and generates 10% fewer false positives. Learn more in our blog post.

Image

Personal Code Review Settings

You can now customize your personal code review preferences. Each team member can set individual preferences for PR Summaries (like auto-summarize PRs and posting in PR descriptions) and Code Review (including correctness, draft PR review, and auto-merge) that override repo defaults.

Navigate to Personal Settings and select your preference under Code Review → Custom Rules. Select "Repo Default" to inherit preferences from the repository level.

Personalize your code review settings in Macroscope Settings.

Issue Comment Support

Macroscope now responds to issue comments in GitHub, not just review comments. Mention @macroscope-app in any comment, and Macroscope will react with 👀 while thinking, and then respond in the main discussion thread. Ask questions about changes, get clarifications, or request deeper analysis without leaving GitHub.

Simply ask @macroscope-app a question directly in an issue comment in Github.

The Little Things

  • Elixir and Starlark Support: Code Review now supports Elixir (.ex, .exs files) and Starlark (.star, Tiltfile, BUILD files).
  • Slack @mentions Controls: Configure whether or not Macroscope @mentions you directly or just uses your name in Slack (e.g. when assigned as a PR reviewer). Less interruption, same visibility. Enable the toggle in Settings → Account.
  • Enterprise/SAML Login: Smoother login flow for SAML customers using GitHub Enterprise Managed Users, with smarter handling of expired tokens.
  • Timezone Support in AMA: When asking Macroscope questions, the query agent now automatically uses your timezone to interpret dates and times. This means you get more accurate results when asking about "yesterday," "this week," or specific dates.
  • Updated Check Run Status: Status now shows ✅ when no issues are found and ◻️ (neutral) when correctness issues are identified. If your branch rules are tied to Macroscope, update your Check Run names accordingly. Moving forward, we'll be making our usage of Check Runs more powerful and customizable to allow you to configure powerful branch protection rules. This is a small step in that direction.

Loving Macroscope? Tag us @Macroscope on X, email contact@macroscope.com, or reach out on Slack – we'd love to hear your feedback!

Haven't tried Macroscope yet?
Try Macroscope free for 2 weeks.