---
title: Autopilot 2.4
source: https://docs.newrelic.com/docs/release-notes/autopilot-release-notes/autopilot-26-09-24
---

### New features

-   **Deeper root cause analysis when you're paged:** Autopilot can now help trace an alert back to the code change behind it from more entry points, including incident and Slack-triggered investigations, so you can pinpoint the issue without digging through the entire deployment history.
-   **See the full data, not just the chart:** Tool results now show the underlying data alongside a visualization, so you can more easily verify what Autopilot based its answer on.
-   **Spot intermittent spikes, not just averages:** Metric analysis now surfaces percentile detail and trend history, making a brief spike easier to catch than it would be from an average alone.
-   **Ask about a full month of alerts in one request:** The alert lookback window for entity-scoped queries has been widened from 7 to 30 days, and an oversized request now gets automatically scaled back instead of rejected outright.
-   **Jump straight into your session:** Responses now include direct session links for browser and mobile, so you can pick up where Autopilot left off without hunting for it.

### Improvements and enhancements

> #### 💡 PREVIEW
>
> We're still working on this feature, but we'd love for you to try it out!
>
> This feature is currently provided as part of a preview program pursuant to our [pre-release policies](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).

**GitHub MCP Integration Capability Updates (Public Preview)**

Autopilot's GitHub integration now ties active alerts more directly to your deployment and release history, so you can triage without switching between tools.

-   **See in-flight fixes before duplicating the work:** During alert triage, Autopilot now checks GitHub for open pull requests already targeting the affected service, so you can see whether a hotfix or related fix is already underway before starting your own.
-   **Spot version drift the moment an alert fires:** Autopilot now compares the release actually deployed against the version that was running when the incident started, surfacing recent rollouts or unverified deployments that may be contributing to the issue.

### Bug fixes

-   **Fixed queries that could fail when counting unique values:** Questions that required counting something unique — like how many distinct users hit a specific error — could cause Autopilot to build an invalid NRQL query and fail to respond. Autopilot is now guided to better handle this, making these questions less likely to error out.
-   **Fewer rejected error-analysis responses:** Fixed an issue where asking for a detailed error breakdown could get rejected for being too large to deliver.
-   **Fewer timeouts analyzing high-volume logs:** Increased the time allotted for log analysis so accounts with large log volumes are less likely to time out.
-   **Cancel to stop the run:** Canceling an investigation from the chat panel now stops it running on the backend.
-   **Faster, cleaner chat panel load:** The chat panel now loads Ask AI and Autopilot first instead of waiting on your full agent list, and no longer shows either one twice in the agent dropdown.
-   **More consistent knowledge-base grounding:** Fast, direct-answer responses and alert-triage investigations now draw more consistently on your knowledge base before answering.
-   **More accurate deployment status in GitHub investigations:** Better reporting of service release status.
-   **Clearer guidance when Autopilot can't find an answer:** Replaced a generic "something went wrong" message with more helpful guidance to try rephrasing your question.
-   **Corrected a misleading connection error:** A login-related redirect was being reported as an expired connection; it's now identified correctly.