> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/changelog/q2-2026/46-escalating-your-ai-pentest-and-additional-context-for-autotriage.md).

# #46 - Escalating your AI Pentest and Additional Context for AutoTriage

28 Apr 2026

### Features

* [**Escalate a Pentest Vulnerability**](https://help.aikido.dev/pentests/coverage-and-findings/human-in-the-loop) - Aikido Pentest Agents are cautious by default to avoid unintended impact. Removing agent restrictions enables deeper analysis, confirming either that additional protection layers hold up or that a vulnerability is genuinely exploitable before it's discovered by real attackers.
* [**Additional Context for AutoTriage**](https://help.aikido.dev/code-scanning/scanning-practices/custom-code-context-for-sast-rules) - Provide Aikido's AutoTriage with specific knowledge about your environment to improve the accuracy of its findings and cut down on false positives.

### **Aikido Intel - Malware & Vulnerability Database**

Our research team has discovered over [#47 new vulnerabilities](https://intel.aikido.dev) over the last two weeks! Including one that turned out far less scary than the headlines suggest: [read our breakdown of the Axios CVE-2026-40175](https://www.aikido.dev/blog/axios-cve-2026-40175-a-critical-bug-thats-not-exploitable).

### Improvements

* Reports - [Trends Over Time now has an “out of SLA” graph](https://help.aikido.dev/compliance-and-reporting/reports/trends-over-time-report)
* Integrations - [Directly reply or ignore via Gitlab MR comments](https://help.aikido.dev/pr-and-release-gating/github-ci-pr-gating-via-aikido-dashboard#ignore-issues-directly-from-pr-comments)
* Cloud - [Reachability for containers](https://help.aikido.dev/container-image-scanning/container-reachability-analysis) is now available for Google Cloud Run
* AutoFix - [Add custom context for AutoFix via .aikido file](https://help.aikido.dev/autofix-and-remediation/automation-and-merging/custom-context-for-autofixes)
* Pentest - [Additional login methods: files, keys and scripts](https://help.aikido.dev/pentests/configure-a-pentest/setting-up-authenticated-testing/handling-files-for-authentication)
* Integrations - [Broker support for websockets](https://help.aikido.dev/miscellaneous-info/aikido-broker-for-internal-applications)
* Zen - [Exclude specific users from rate limiting](https://help.aikido.dev/zen-firewall/zen-features/blocking-users-with-zen-firewall#remove-rate-limiting)
* Safe-chain - [Release 1.4.9 adds shrinkwrap to npm](https://www.notion.so/Changelog-Items-28-03-10-04-3445cb88a38280cb9ef4d92804c38251?pvs=21)
* Zen Firewall - Agent releases for [Dotnet](https://github.com/AikidoSec/firewall-dotnet/releases), [Golang](https://github.com/AikidoSec/firewall-go/releases) and [Node](https://github.com/AikidoSec/firewall-node/releases)
* IDE - New releases for [VSCode](https://marketplace.visualstudio.com/items?itemName=AikidoSecurity.aikido), [Jetbrains](https://plugins.jetbrains.com/plugin/24993-aikido-security/versions/stable) and [Visual Studio](https://marketplace.visualstudio.com/items?itemName=AikidoSecurity.aikido-visualstudio)
* API - [Add Azure container registry](https://apidocs.aikido.dev/reference/addazurecontainerregistry)
* API - [Add GCP registry](https://apidocs.aikido.dev/reference/addgcpartifactregistry)
* API - [Update headers for Domain scan](https://apidocs.aikido.dev/reference/updatedomaincustomscanheaders)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/changelog/q2-2026/46-escalating-your-ai-pentest-and-additional-context-for-autotriage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.