> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/products-and-services/demo/security-engineer-chat.md).

# Security Engineer - Chat

Still jumping between dashboards, logs, and a sea of metrics to understand your app’s security posture? 😩

What if you could just… ask?

No noise, no fluff—just a straight answer from your locally running AI Security Engineer. 🤖

🧠 It knows your environment.

🔐 It understands code.

⚙️ It thinks like a security expert.

And it lives *right on your machine*—no cloud dependency, no delays.

This is AppSec reimagined.

Why waste time when you can have an AI that triages findings, explains risks, and recommends fixes—in seconds.

🚀 The new paradigm isn’t more dashboards—it’s an AI that is your security team.

{% embed url="<https://vimeo.com/1072373982?share=copy#t=0>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aquilax.ai/products-and-services/demo/security-engineer-chat.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.