> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macroscope.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Notes

<Update label="June 5, 2026">
  **MCP Connector Access Controls**

  MCP connectors now support per-user access controls. When creating or editing an MCP connection, use the **Access** tab to define an allow list of users who can use it. [Learn more about MCP Connectors](/integrations#mcp-connectors).

  <Frame>
    <img src="https://mintcdn.com/macroscope/jC6IHLkvzO9lPc9p/images/mcp-connector-access.gif?s=88caf2f583c7fab041282b7af15f7885" alt="MCP connector access controls" width="800" height="655" data-path="images/mcp-connector-access.gif" />
  </Frame>

  **Code Review Feedback Analysis**

  The Code Review activity log now includes a **Feedback Source** column and filter, so that you can see how feedback was captured:

  * **Explicit** feedback covers emoji reactions (i.e. 👍 or 👎) on review comments
  * **Inferred** feedback reflects sentiment Macroscope classifies from replies when a PR is closed.

  **Macro Author Filtering**

  Event-triggered Macros now support filtering by author, letting you include or exclude specific authors when defining trigger conditions. [Learn more about Macros](/macros).
</Update>

<Update label="May 29, 2026">
  **Check Run Agent Prerequisite Steps**

  Custom Review Agents now support prerequisite CI step gating with the `waitsFor` configuration option. Specify CI checks that must complete before a review agent runs—useful for sequencing reviews after builds, tests, or other checks. Configure per-agent prerequisites with optional custom timeouts, or use `"*"` to wait for all other checks. See [Check Run Agents](/check-run-agents#prerequisite-steps) for details.

  **Claude Opus 4.8 for Check Run Agents**

  Claude Opus 4.8 (`claude-opus-4-8`) is now available as a model option for Check Run Agents. Set `model: claude-opus-4-8` in your agent's front matter to use the latest Opus generation.
</Update>

<Update label="May 22, 2026">
  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased recall for TypeScript, Rust, Swift, Kotlin, JavaScript, Python, Java, and Go.
</Update>

<Update label="May 15, 2026">
  **Exclude GitHub Authors from Commit Processing**

  Admins can exclude specific GitHub authors from commit summarization and productivity metrics (i.e. Status features). Manage the list under **Settings** → **Workspace → Excluded Commit Authors**.

  **Check Run Cost Visibility**

  [Check Run Agents](/check-run-agents) display their billed total directly in the GitHub Checks tab, so you can see the cost of each run.

  **Slack Connection Refresh**

  Admins can reconnect their Slack workspace from **Settings → Connections** to reauthorize new OAuth scopes. Use this whenever we add new bot capabilities and you want your existing connection to pick them up without uninstalling.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased precision and recall for Go.
</Update>

<Update label="May 8, 2026">
  **Macroscope CLI**

  You can now run Macroscope code review locally from your terminal, against uncommitted changes, before you push. [Learn more about the CLI](/cli).

  <Frame>
    <video autoPlay muted loop playsInline />
  </Frame>

  **New Models in Check Run Agents**

  Check Run Agents now supports four additional models: `claude-sonnet-4-5`, `claude-sonnet-4-6`, `gpt-5-4`, and `gpt-5-5` -- alongside the existing Opus 4.5 / 4.6 / 4.7 and GPT-5.2 options. [Learn more about Check Run Agents](/check-run-agents#models).

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased recall for Python and Elixir.
</Update>

<Update label="May 1, 2026">
  **Check Run Agents: now GA!**

  Check Run Agents are fully customizable AI agents that execute as GitHub Check Runs on your pull requests. For each Check Run Agent, you can define exactly what the agent checks, which files it should/shouldn't review, which tools it can use, what actions it should take, and how it formats its output — all from a markdown file in your `.macroscope/` directory. [Learn more in our docs](/check-run-agents) and [check out our video about it](https://x.com/kayvz/status/2050259933409792386).
</Update>

<Update label="April 24, 2026">
  **Delegated Admins**

  Workspace admins can now delegate admin permissions to other members from **Settings → Macroscope Access → Members**. Delegated admins can manage Macroscope settings on behalf of the workspace. GitHub roles and permissions are unaffected.

  **One-Time Credit Purchase**

  Admins on usage based billing can make one-time credit purchases from **Settings → Billing**.
</Update>

<Update label="April 17, 2026">
  **Check Run Agents Can Write Code**

  Check Run Agents can now fix the issues they find. Add the `write_code` tool to any agent and it will commit changes directly to the pull request. [Learn more about Check Run Agents in our docs](/check-run-agents).
</Update>

<Update label="April 10, 2026">
  **Check Run Agents**

  Check Run Agents are fully customizable AI agents that execute as GitHub Check Runs on every pull request. They have full access to your codebase, git history, and connected integrations. You can define exactly what an agent checks, which files it reviews, which tools it can use, what actions it can take, and how it formats its output — all from a markdown file in your `.macroscope/` directory. [Learn more in our docs](/check-run-agents).

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased recall for Kotlin and Swift.
</Update>

<Update label="April 3, 2026">
  **Event-Driven Macros**

  Macros can now trigger on new commits and new pull requests, in addition to recurring schedules. Configure repo and branch filters to control which events run your Macro. Results can be delivered to Slack or forwarded to a webhook URL.

  **New Integrations**

  We've added several new integrations, including Amplitude, Sentry, and GCP Cloud Logging. You can configure your integrations in **Settings → Connections**. [Learn more about supported integrations in our docs](/integrations).

  **Image Generation**

  The Macroscope Agent can now generate images on demand, including architecture diagrams, flowcharts, and visual explanations.

  **Code Review Filter Persistence**

  Filters in the Code Review activity log now persist in the URL. Copy the link to share a filtered view with your team.

  **New Code Review Settings**

  "Review Draft PRs" and "Automatically merge Macroscope's PRs" can now be configured at the workspace and repo level. Admins can set organization-wide defaults and manage settings in batch across repos; contributors can override in their account settings.
</Update>

<Update label="March 27, 2026">
  **MCP Connector Support**

  Macroscope's Agent can now connect to any [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) compatible server, so you can give it access to tools like Datadog, PagerDuty, or your own internal APIs. Macroscope auto-discovers available tools and supports OAuth 2.1 and header-based auth. [Learn more](/integrations#mcp-connectors).

  **Webhooks**

  You can now trigger Macroscope's Agent programmatically via webhooks. Send a query over HTTP and specify where to deliver the results: a Slack channel or an external URL. Note: using Webhooks requires Status to be enabled. [Learn more](/api).

  **Cross-Repo PR Reviews**

  Macroscope can now review pull requests where the head branch and base branch are in different repositories. Enable per repo with the new **Review Cross-Repo PRs** toggle in **Settings → Repos**.
</Update>

<Update label="March 20, 2026">
  **Ask Macroscope Anything: GitHub API + Docs Search**

  AMA can now query the GitHub REST API for live data on PRs, issues, check runs, and deployments. Ask "what checks failed on PR #42?" or "show me the latest deployment" and get real-time answers. The agent can also search [Macroscope's help docs](https://docs.macroscope.com) to answer any product questions.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased recall for Rust and TypeScript.
</Update>

<Update label="March 13, 2026">
  **Next Scheduled Run for Macros**

  Macros now show when they'll next run. The next run time appears in the macro header and as a tooltip on the cadence pill, so you always know when to expect your next scheduled report.

  <img src="https://mintcdn.com/macroscope/Ij1wsJ7EUw4zYzA-/images/nextscheduledmacro.png?fit=max&auto=format&n=Ij1wsJ7EUw4zYzA-&q=85&s=fee567c5fdb921da3ac85fd48255addb" alt="Next scheduled run for macros" width="1996" height="1282" data-path="images/nextscheduledmacro.png" />
</Update>

<Update label="March 6, 2026">
  **Approvability — Now Generally Available**

  Approvability has graduated from beta and is available to all workspaces. Approvability lets Macroscope automatically approve low-risk PRs from trusted authors when they pass code review with zero issues — freeing engineers from rubber-stamping routine changes. Enable it in **Settings** under the **Code Review** section. [Learn more about Approvability](/approvability).

  **Slack Group DMs**

  You can now create a Slack group DM that includes Macroscope alongside your teammates, so you can collaborate with Macroscope outside of a channel.

  **Ask Macroscope to Add PR Reviewers**

  You can ask Macroscope to assign a reviewer to any pull request directly from Slack — just tell it who to add and to which PR.

  **Per-File Exclusion Reasons in Check Runs**

  Check run details now surface per-file exclusion reasons, showing why specific files were skipped during review.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increases in precision for Elixir, Starlark, and PHP, as well as increased recall for Python, Rust, Java, JavaScript, Swift, Kotlin, and PHP.
</Update>

<Update label="February 27, 2026">
  **Biweekly Macro Cadence**

  Macros now support a Biweekly schedule (i.e. every other week) in addition to Daily and Weekly.

  <img src="https://mintcdn.com/macroscope/F2eW309M0UQQNdHV/images/biweeklymacro.png?fit=max&auto=format&n=F2eW309M0UQQNdHV&q=85&s=ced88601be429d2ebfb4e464f905e3b4" alt="biweekly" width="1760" height="554" data-path="images/biweeklymacro.png" />

  **PR Description Formatting**

  When a PR already contains user-written text, Macroscope's review summary renders as a blockquoted note rather than replacing the content.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increases in precision for Go as well as increased recall for TypeScript and Elixir.
</Update>

<Update label="February 20, 2026">
  **Webhooks**

  You can now trigger Macroscope queries from external services like Zapier, n8n, or your own APIs. Pass in a query and a destination (either a Slack channel ID or forwarding URL), and Macroscope will post the result to the provided destination. You can create webhooks and see detailed instructions in Settings → Connections → Webhooks.

  **PostHog Integration**

  Macroscope now connects to PostHog as a data source. With this connection, you can query your PostHog event data, run HogQL queries, and explore feature flags directly through Macroscope. Connect PostHog in Settings → Connections → PostHog.

  **Always-Review PR Labels**

  You can now add "always-review" labels to have Macroscope review any PR, even on repositories where automatic reviews are turned off. This also overrides skip-review labels. Go to Settings → Code Review → Always Review PR Labels to add a label (e.g., `macroscope-review`), then apply it to any PR on GitHub to trigger a review.

  **Slack Attachment Support**

  Macroscope now reads attachments from all messages in a Slack thread, including images, text documents, and code snippets. For example, you can tag @Macroscope in a thread with a screenshot of a bug and it can parse the attachment and open a PR with a fix.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increased recall for Go, Java, Rust, and TypeScript.
</Update>

<Update label="February 13, 2026">
  **Filter by PR Status in Code Review Dashboard**

  In the Code Review Dashboard, you can now filter code review issues by the status of the pull request (draft, open, merged, or closed), enabling you to see a more focused list of issues and analyze more specific code review stats.

  <img src="https://mintcdn.com/macroscope/1S55A_GR6pnPNwIH/images/filterbyprstatus.gif?s=15a5d45e922618172c50da7909c64327" alt="Filter by PR Status" width="800" height="295" data-path="images/filterbyprstatus.gif" />

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in increases in precision for Ruby, Rust, and Starlark, as well as increased recall for Go, Java, and Starlark, Swift.
</Update>

<Update label="February 6, 2026">
  **V3 Code Review**

  We released a new version of Macroscope Code Review. Based on our benchmark, v3 leaves 22% fewer comments overall, with 64% fewer nitpicks in Python and 80% fewer in TypeScript, and demonstrates a step-change improvement in precision from 75% to 98%. [Learn more on our v3 Code Review blog](https://macroscope.com/blog/code-review-v3).

  **Approvability \[beta]**

  We're launching Approvability, which enables Macroscope to automatically approve PRs when low-risk changes from trusted authors meet safety criteria. When a PR is opened or updated, Macroscope runs two automated checks:

  1. **Eligibility**: Do the changes meet your team's criteria for auto-approval? This includes evaluating code ownership as a contextual signal — factoring in `CODEOWNERS`, blame history, and author role.
  2. **Correctness** : Does the PR pass Macroscope code review with zero issues?

  If both hurdles are cleared, Macroscope will approve the PR automatically.

  [Learn more about Approvability in our help docs](/approvability). Reach out to [support@macroscope.com](mailto:support@macroscope.com) if you would like to use this feature.

  **Impact Severity on Code Review Comments**

  Review comments now display impact severity (Critical / High / Medium / Low) so you can quickly triage which issues need immediate attention.

  <img src="https://mintcdn.com/macroscope/9P8I2DoTVBliiEBK/images/highseveritybug.png?fit=max&auto=format&n=9P8I2DoTVBliiEBK&q=85&s=54561479bc12105dd2de1ca06c7b12c3" alt="high severity bug" width="2246" height="1397" data-path="images/highseveritybug.png" />

  **Updates to Code Review Dashboard**

  We've released several updates to the Code Review dashboard, including:

  * Filter comments by author, date, feedback reaction (or ), and addressed status (whether a review comment has been resolved).
  * View high-level stats, including total PRs reviewed, average issues per PR, total comments left, % comments addressed, fix-it-for-me tasks started, and time saved resulting from fix-it-for-me.
  * "Useful Comments Over Time" chart shows the % of review comments that were addressed by PR close or that received positive feedback (from a  reaction or a reply).
  * Download your code review history as a CSV.

      <img src="https://mintcdn.com/macroscope/9P8I2DoTVBliiEBK/images/newcodereviewdashboard.png?fit=max&auto=format&n=9P8I2DoTVBliiEBK&q=85&s=d8a57d41d22061035516dc6d43dc4150" alt="new dash" width="2152" height="846" data-path="images/newcodereviewdashboard.png" />

  **Universal File Support**

  Previously, Macroscope code review only reviewed files in languages with native AST-parsing. Now, every file in your PR gets reviewed.
</Update>

<Update label="January 30, 2026">
  **Linked Issues in Slack Commit Summaries**

  Commit summary notifications in Slack now display linked Linear and Jira tickets when available. You'll see a "Linked Issues" section with ticket IDs linked to their URLs, making it easier to trace commits back to the work they address.

  **PR Closed Notifications**

  Macroscope now sends PR closed notifications even when a PR is closed without merging.

  **Code Review Improvements**

  We've made improvements to our code review pipeline, resulting in measurable increases in precision for Java, Kotlin, and Swift, as well as increased recall for Python.
</Update>

<Update label="January 23, 2026">
  **Custom AMA Instructions**

  You can customize how Macroscope responds to questions about your codebase. Go to **Workspace Settings → Custom AMA Instructions** to add your instructions, such as preferred response tone, domain-specific context, or output format preferences. You can also define person-specific instructions, like: “customer success teammates should get less technical responses.”

  **Code Review Improvements**

  We've made several improvements to our code review pipeline, resulting in measurable increases in precision for TypeScript, Python, Go, Java, Ruby, and Kotlin, as well as increased recall for Java and Elixir.
</Update>

<Update label="January 16, 2026">
  **Pre-Configured Macro Templates**

  You can now create Macros from pre-built templates. Browse templates on the Macros page and click any template to create a new Macro that you can customize or use as-is.

  <img src="https://mintcdn.com/macroscope/qv3bHI8gXhPzbHhB/images/macrotemplates.png?fit=max&auto=format&n=qv3bHI8gXhPzbHhB&q=85&s=bad22d5794d7e6da5c275bf233c3fead" alt="Templates" width="1894" height="894" data-path="images/macrotemplates.png" />

  **Reassign Project Areas from Breakdown Chart**

  When hovering over a Project in the Project Focus Breakdown chart, you can click the “Move Area” button to reassign the Project to a different Area.

  <img src="https://mintcdn.com/macroscope/qv3bHI8gXhPzbHhB/images/moveprojectareas.gif?s=b0438c84fd9d1d0b9a2c73d9d40a9ebb" alt="areas" width="800" height="188" data-path="images/moveprojectareas.gif" />

  **Skip Labels Now Work for PR Summaries**

  Labels configured to skip code review now also skip PR summary posting. Add your configured skip label to any PR to disable both features at once.

  **Improvements to Code Review**

  Better handling of language-specific patterns and reduced noise from non-actionable issues.
</Update>

<Update label="January 9, 2026">
  **Comment Resolution Tracking**

  Code review comments now link to the commit where they were resolved and indicate if feedback has been addressed. Macroscope automatically evaluates and updates comments when new code is pushed to a PR.

  <img src="https://mintcdn.com/macroscope/LIuXNp_8L9fiXnLa/images/addressedcomment.png?fit=max&auto=format&n=LIuXNp_8L9fiXnLa&q=85&s=4087bf587cb2a47a8564a3efa0eedd9c" alt="Comment Resolution Tracking" width="1943" height="782" data-path="images/addressedcomment.png" />

  **Per-PR Auto-Merge Control**

  You can override your default auto-merge settings when asking Macroscope to fix an issue by adding instructions like “Fix it for me and auto-merge” or “Fix it but don't auto-merge.”

  **Timezone-Aware Date Selection**

  Date presets (e.g. “Yesterday”, “This Month”) in the Macroscope web app now automatically align with your local timezone.
</Update>

<Update label="January 2, 2026">
  **Neutral Check Run Status**

  When Macroscope reviews your code and posts comments with issues that need addressing, check runs now complete with `NEUTRAL` status instead of `SUCCESS`, so it's clear when there's pending feedback to address.

  **Explanations for Blocked Auto-Merges**

  When you use Macroscope's coding agent to automatically fix issues on a feature branch, the agent creates a pull request with the fixes and attempts to auto-merge it back to your base branch (if you have auto-merge enabled).

  If auto-merge is blocked, Macroscope now posts a comment explaining the specific GitHub requirement preventing the merge (e.g. missing reviews, merge conflicts, failed checks).

  **Flexible @Mention Support in GitHub**

  Macroscope now responds to both `@macroscope` and `@macroscope-app`.
</Update>

<Update label="December 26, 2025">
  **Fix It For Me**

  Macroscope can directly fix issues found during code review. Just reply to a GitHub review comment and ask Macroscope to fix it. Macroscope will create a branch, push commits, open a PR, and merge it back into your working branch. [See help docs for more details](/fix-it-for-me).

  <img src="https://mintcdn.com/macroscope/pOcfkLu6bNwYjvlb/images/fix-it-for-me.gif?s=37482b57cb0aaaf711c824bd28497da6" alt="Fix It For Me" width="800" height="336" data-path="images/fix-it-for-me.gif" />

  **Updated Check Run Labels**

  GitHub Check Runs now display as "Macroscope - Correctness Check" and "Macroscope - Custom Rules Check" (previously "Review for correctness" and "Review custom rules").

  **Pull Request Closure Messages**

  When someone manually closes a PR, Macroscope now posts a comment identifying who closed it and whether it was merged.
</Update>

<Update label="December 19, 2025">
  **Personal Code Review Settings**

  Individuals can now customize their individual preferences for PR Summaries and Code Review that override their workspace defaults. Select "Repo Default" to inherit preferences from the repository level.

  <img src="https://mintcdn.com/macroscope/zLGqpC4A_A_cjxbN/images/personalsettings.gif?s=12744b59023fdf1ad32bc1409463e0d5" alt="Personal Code Review Settings" width="800" height="401" data-path="images/personalsettings.gif" />

  **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.
</Update>

<Update label="December 12, 2025">
  **v2 Code Review by 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 40% higher recall and generates 10% fewer false positives. [Learn more in our blog post](https://blog.macroscope.com/blog/opus-4.5-code-review).

  **Invoking Macroscope in PR Discussions**

  Macroscope can now respond to your comments in the main PR discussion thread, not just inline code comments. When you mention @macroscope-app in a comment, Macroscope will react with 👀 to acknowledge it’s thinking about your question and then respond in the main discussion thread.

  **Ignoring Bot Comments in GitHub**

  @macroscope-app no longer responds to comments authored by other bots in GitHub.
</Update>

<Update label="December 5, 2025">
  **Improved Executive Summaries**

  We’ve simplified summaries on the home page. Summaries are organized by [Areas](/areas) and have collapsible sections, so you can easily see a high level view of what’s changed in your codebase this sprint.

  <img src="https://mintcdn.com/macroscope/N4Ucmsp9tHFh8NN9/images/executive-summaries.gif?s=be42adb34605c1d23b239a55c0792538" alt="Executive Summaries" width="800" height="554" data-path="images/executive-summaries.gif" />

  **@mentions in Slack**

  Users can configure whether or not Macroscope can @mention them directly in Slack. When enabled, Macroscope will @mention them when relevant, such as when they are assigned as a reviewer on a PR. When disabled, Macroscope will reference the user’s Slack name instead of @mentioning them directly. This setting is configurable per user in Settings → Account.

  **Language Support for Elixir and Starlark**

  Macroscope code review now supports Elixir (.ex, .exs files) and Starlark (.star, Tiltfile, BUILD files).

  **Login Improvements for Enterprise/SAML Customers**

  For customers using SAML login alongside GitHub Enterprise Managed Users, Macroscope’s login flow should be smoother and smarter about automatically detecting expired tokens.
</Update>

<Update label="November 21, 2025">
  **Streamlined Macros Scheduling**

  Scheduling regular reports with Macros is now even easier. After you set your daily/weekly cadence and write your prompt, all you need to do is copy/paste the generated Slack command into any Slack channel(s) you want to subscribe to the Macro. [Learn more about Macros in our help docs](/macros).

  <img src="https://mintcdn.com/macroscope/4T9fGgYNxijaTAUn/images/macros-gif.gif?s=9b579b85f0e252d64872dd79a01661f7" alt="Macros GIF" width="800" height="461" data-path="images/macros-gif.gif" />
</Update>

<Update label="November 14, 2025">
  **Manually Trigger Code Review in GitHub**

  You can now manually trigger a code review on a PR in GitHub by commenting `@macroscope-app review`, regardless of whether Macroscope code review is enabled for the repository. Macroscope will acknowledge your comment with a thumbs-up reaction and run a code review on the PR. This is useful when you want Macroscope to run another review after making changes, or when automatic reviews are disabled for a repo.

  **Visualize Your Code in Slack**

  Want to see how tables are connected in a database? Map a diagram of a workflow’s lifecycle? You can ask @Macroscope to generate ASCII diagrams of anything related to your code.

  <img src="https://mintcdn.com/macroscope/4tj8K_EVtuqnVMZu/images/ascii-art.png?fit=max&auto=format&n=4tj8K_EVtuqnVMZu&q=85&s=342cba5c12393e99e4874c781f1d144f" alt="ASCII Art" width="966" height="818" data-path="images/ascii-art.png" />

  **Updates to Query Agent (a.k.a. Ask Macroscope Anything)**

  * **Smarter Guidance** - Query Agent can provide guidance when you explicitly request help, even for tasks outside its direct capabilities.
  * **Adaptive Tone** - Macroscope adapts to your communication style. If you use humor or casual language, Query Agent will respond in kind while maintaining accurate and factual responses.
  * **Content for External Stakeholders** - When you need content for external audiences, Query Agent can format responses and links appropriately for sharing outside your organization. Just request externally-facing content when preparing materials.
  * **More Flexibility** - Under the hood, Query Agent's underlying prompt system supports broader interaction patterns, allowing it to handle a wider variety of interactions with users.
</Update>

<Update label="November 7, 2025">
  **Merge Notifications in Slack**

  Macroscope now notifies you in Slack in real-time when commits are merged to release branches. When a merge occurs, Macroscope reacts to the original PR summary message with a 🚀 emoji and posts a reply in the message thread. This works for all merge types, including squash, rebase, and fast-forward merges.

  Note: this requires subscribing to commit notifications in a Slack channel with the `/macroscope subscribe-commits` command.

  <img src="https://mintcdn.com/macroscope/qgyhQ8BrbNQDWjW0/images/Merge-Status_Commits_slack.png?fit=max&auto=format&n=qgyhQ8BrbNQDWjW0&q=85&s=b9a416b58458b7d11f833ba5ad3b7376" alt="Merge Notifications" width="1486" height="838" data-path="images/Merge-Status_Commits_slack.png" />

  **Skip Code Review with GitHub Labels**

  You can now tell Macroscope to skip code review on PRs tagged with specific [GitHub labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels). In Settings → Repos → Skip PR Labels, you can specify which GitHub labels that you want Macroscope to ignore during code review (e.g. “docs-only”). When you apply any of these designated labels to a PR, Macroscope will automatically skip the code review process for that PR.

  <img src="https://mintcdn.com/macroscope/_oqEJXvukn4PNgDT/images/skip-pr-labels.png?fit=max&auto=format&n=_oqEJXvukn4PNgDT&q=85&s=e87a734e95cc4aed3c0e6f2fde73ba5c" alt="Skip Code Review" width="1512" height="1305" data-path="images/skip-pr-labels.png" />

  **New Rendering Modes for Suggested Fixes in Review Comments**

  Macroscope now automatically selects the best format for displaying suggested code fixes in review comments. Depending on the context, Macroscope chooses between three options:

  * GitHub’s native inline suggestion block (i.e. “accept diff”)
  * Unified diff blocks (i.e. static code diff)
  * No diff (i.e. text-only explanations)

  **Code Review Latency**

  We significantly improved code review latency in the case where you push multiple commits to a PR in quick succession.
</Update>

<Update label="October 31, 2025">
  **Batch Repository Settings**

  You can now configure settings for multiple repositories at once. The new interface, found in Settings → Repos, allows you to search repos, select multiple repos, and apply settings across multiple repos simultaneously.

  <img src="https://mintcdn.com/macroscope/gigJLPA2aOWCgrn4/images/multiple-repos-settings.png?fit=max&auto=format&n=gigJLPA2aOWCgrn4&q=85&s=5f1695747de3fc594ac316a5e3de0086" alt="Multiple Repos Settings" width="1416" height="1384" data-path="images/multiple-repos-settings.png" />

  **AMA for Repos with Summaries Disabled**

  Macroscope’s Slackbot can answer questions about any repository you’ve linked to Macroscope, even if PR summaries are disabled. Based on customer feedback, we changed the PR summary setting so that it only controls whether generated summaries are posted to GitHub. This allows your Slack users to @ mention Macroscope with questions about PRs in repos where the PR summary posting feature is disabled.

  **Shorter Code Review Comments**

  We’ve adjusted Macroscope code review comments to be more succinct.
</Update>

<Update label="October 24, 2025">
  **Path-Based Filters for Slack Subscriptions**

  With path-based filters, you can limit code activity subscriptions to specific parts of a repository. Any activity that modifies files matching the specified path filter(s) will trigger a Slack notification in the subscribed Slack channel. To create a code activity subscription that is filtered by file path, add the`--paths=` flag to the end of a `/macroscope` subscription command, and specify which file path(s) you want to filter by. [Learn more about path-based filters in our help docs](/slack-subscriptions#path-based-filters).

  **Filtered Issues in Code Review**

  If you’ve been curious which comments Macroscope considered leaving on your pull request but didn’t, you can now see them. By default, these lower-signal comments are hidden to keep reviews focused. However, you can expand the “Filtered Issues” section at the bottom of the PR description to see which comments were excluded, by file, and expand each file to view the specific comment(s) identified.

  <img src="https://mintcdn.com/macroscope/BH6PPia_ORrXEKbA/images/filtered-comment-example.png?fit=max&auto=format&n=BH6PPia_ORrXEKbA&q=85&s=f487bfc262f9de433153e7a05cfc534b" alt="Filtered Comment" width="3842" height="1544" data-path="images/filtered-comment-example.png" />

  **Custom Rules \[deprecated for [Check Run Agents](/check-run-agents)]**

  We’re introducing the ability for Macroscope to run an independent code review focused on your team’s best practices, based on custom rules you define. In `macroscope.md` files throughout your codebase, you can define your team’s best practices (i.e. anything that’s idiomatic of how you want code to be written). During reviews, Macroscope will run a separate CheckRun that flags violations and leaves inline comments that reference the relevant rule.

  <img src="https://mintcdn.com/macroscope/BH6PPia_ORrXEKbA/images/idiom-violation-example.png?fit=max&auto=format&n=BH6PPia_ORrXEKbA&q=85&s=fdc9c0d7abf23c82e4d850d2386a96c6" alt="Code Review Rules" width="3332" height="2292" data-path="images/idiom-violation-example.png" />
</Update>

<Update label="October 17, 2025">
  **AI Web Research in Code Review**

  Code review now has web research capabilities, meaning that Macroscope can search the web for external knowledge sources. When reviewing your code, Macroscope uses [Parallel](https://www.parallel.ai/)’s search API to find the latest documentation, so that code reviews take into account every library and package you use.

  <img src="https://mintcdn.com/macroscope/zqSwq_ILVwd2z5We/images/code-review-web-search.png?fit=max&auto=format&n=zqSwq_ILVwd2z5We&q=85&s=af5b8ee558fbfea2f5e0b7fd2996969f" alt="Web Search with Parallel" width="2536" height="1364" data-path="images/code-review-web-search.png" />

  **Ticket Creation in Slack**

  You can now ask the Macroscope Slackbot to create Jira and Linear tickets. Ask @Macroscope to create a ticket and Macroscope will use the context provided to generate a ticket on your behalf. To enable this, you will need to re-authorize your Jira / Linear integrations in Settings → Connections. [Learn more about our Jira / Linear integrations here](/issue-management-integrations).

  <img src="https://mintcdn.com/macroscope/PAwlZ1eBM5x0L3WO/images/make-a-ticket-for-me.png?fit=max&auto=format&n=PAwlZ1eBM5x0L3WO&q=85&s=363e709f9018a8dfe1290b4900abff60" alt="Make a Jira Ticket" width="1550" height="310" data-path="images/make-a-ticket-for-me.png" />

  **Displaying Teammate Names**

  The web app now shows contributors’ GitHub display names (instead of their GitHub usernames) across commits, contributors, and team views, making it easier to identify team members.
</Update>

<Update label="October 10, 2025">
  **Contributor Metrics in AMA**

  Macroscope AMA now has access to Contributor Productivity Metrics (e.g. # commits, # PR, coding time), so you can ask questions like “@Macroscope how many PRs were opened in the last 2 days?”. Macroscope’s agent can retrieve any metrics that are visible on the Macroscope website, across any time range.

  **Linear Integration v2**

  Macroscope is now using Linear's new "Agents" framework. Soon, Macroscope will be able to take actions on behalf of users in Linear. Existing customers will need to unlink and re-link their Linear application in their Macroscope settings in order to authorize fresh permissions.

  **Jira Integration v2**

  We are building a deeper Jira integration in Macroscope AMA. Soon, Macroscope will be able to create Jira issues and answer questions about your Jira projects and issues.

  **Squash Merge Summaries**

  The Commits page now displays summaries for squash merges. Users can hover over a branch’s release details to view the summary, which shows the number of commits squashed and the date range covered.

  <img src="https://mintcdn.com/macroscope/CTrDNb7YCwqlEep4/images/squashmerge.png?fit=max&auto=format&n=CTrDNb7YCwqlEep4&q=85&s=0b2fad2450951eb5ebb1304dd8a3368b" alt="Squash Merge" width="1595" height="760" data-path="images/squashmerge.png" />
</Update>

<Update label="October 3, 2025">
  **Support for GitHub PR Templates**

  You can now add Macroscope summaries directly into a PR template by placing special markers where you want the summary to appear. [Learn more in our help center.](https://docs.macroscope.com/pull-request-descriptions#inserting-macroscope-summaries-into-your-pr-templates)

  <img src="https://mintcdn.com/macroscope/wV9iF7_iN4IIoRrw/images/PRtemplate.png?fit=max&auto=format&n=wV9iF7_iN4IIoRrw&q=85&s=bc66b19be6f42e335298131601fe2c43" alt="PR Template" width="940" height="752" data-path="images/PRtemplate.png" />

  **Exportable Contributor Stats across Custom Time Ranges**

  The Contributors page shows engineering productivity metrics grouped by individual contributors or by GitHub Team. This page now includes total opened PRs, in addition to Commits and Coding Time. Metrics can be filtered across any custom date range and exported as a CSV.

  <img src="https://mintcdn.com/macroscope/wV9iF7_iN4IIoRrw/images/contributors-date-range.png?fit=max&auto=format&n=wV9iF7_iN4IIoRrw&q=85&s=307a642209fe749a65649782d64df2f4" alt="Contributors Date Range" width="2918" height="1644" data-path="images/contributors-date-range.png" />

  **Smarter, Faster “PR Assistant”**

  We made our PR bot smarter and faster by ensuring it retains all the context of the code research it collected while reviewing your code. This means that when you’re asking clarifying questions or debating implementation details within a Pull Request review comment, Macroscope will have better informed responses and lower latency.

  **Better Code Review**

  We have made several improvements to code review that increase bug detection rate while reducing false positives.

  **Slack Messages**

  We have improved the formatting of code activity updates in Slack so that messages are easier to scan and understand.
</Update>

<Update label="September 19, 2025">
  **We’re Live!**

  As of September 17, we’re officially out of private beta.

  **Coding Time Estimates**

  Improved our Coding Time estimate algorithm to provide more accurate estimations based on the complexity of code changes.

  **Code Review Improvements**

  Optimized our code review pipeline to reduce the likelihood of false positives. In our testing, this results in \~30% lower comment volume without a meaningful impact to overall bug detection rate.

  **Deployment Tracking for Commits**

  <div style={{ textAlign:"center",marginBottom:"15px" }}>
    <img src="https://mintcdn.com/macroscope/gMmVbfesraMtgQT_/images/rocket-for-deployment-tracking.png?fit=max&auto=format&n=gMmVbfesraMtgQT_&q=85&s=a8cf6ce826a08a45fd193b2287920b12" alt="Deployment tracking with rocket icon" style={{ width:"100%",height:"auto" }} width="1144" height="568" data-path="images/rocket-for-deployment-tracking.png" />
  </div>

  Commits now display a "Released to" indicator with a rocket icon and linked branch tag when released to a specific branch, making it easier to track deployment status.

  **Slackbot Resilience**

  Improved reliability and resilience of responses from Macroscope’s Slackbot. Sometimes, when users asked code research questions, the Slackbot would struggle to respond when the response included emojis due to Slack API compatibility issues. Now, the Slackbot responds without failure.

  **Mobile Viewing**

  Better viewing on tablets and larger mobile devices, plus improved chart displays.

  **Resynchronize with GitHub**

  In the rare event your repositories or related data in Macroscope ever fall out of sync with GitHub, you can click the "Resynchronize Now” button in Settings → Support to manually trigger a resynchronization.
</Update>

<Update label="September 12, 2025">
  **Code Review Improvements**

  Improved bug detection across the 8 languages Macroscope code review supports. Our new pipeline will identify many more potential issues than before. In testing, we observed a significant improvement in detection rates with only a marginal increase in disapproval rates.

  **Status for “Run Now” Macros**

  When clicked, the “Run Now” button on the Macros Page shows live status, so users know when a Macro is executing and that the results will be posted to Slack soon.

  **Project Focus Breakdown Chart Tooltips**

  Tooltips in the Project Focus Breakdown chart on the Productivity Page have been improved for readability.
</Update>

<Update label="September 5, 2025">
  **Account Settings Code Review Toggle**

  Users now have the flexibility to turn off correctness code reviews for their own PRs at the account level. This toggle is available in Settings → Account and gives each user more control over their review experience.

  **Mobile Experience Improvements**

  Improved scrolling behavior and updated UI for a smoother, more consistent experience on mobile.
</Update>