# Ask Aikido: Contextual AI Chat

<figure><img src="/files/ULgqMDUoqpgehtfEgCzr" alt=""><figcaption></figcaption></figure>

`Ask Aikido` is the in-product chat for digging deeper into a finding. Aikido already filters noise automatically. AutoTriage suppresses false positives and reprioritizes issues using reachability, CVE signals, and your environment context. Most of the time, that is enough.

Use `Ask Aikido` when you want to validate a decision, inspect the real attack path, or adapt a generated fix. You stay inside Aikido. You do not need to switch tools or copy findings into a separate chatbot.

### Use cases

#### 1. SAST: Code analysis

Ask questions like `Is this actually risky for us?` , `Why did AutoTriage raise the severity for this issue?` or `Walk me through how this could be exploited in practice.`

Use this chat to:

* validate severity
* understand the realistic attack path
* decide whether to fix now, schedule it, or ignore it with a reason

<figure><img src="/files/fzz3eLJvruI3rSXs1MMv" alt=""><figcaption></figcaption></figure>

This chat can be reached by clicking 'View Code Analysis' in the sidebar (for SAST issues). Then click the button 'Ask Aikido' on top left.

#### 2. Dependencies: Full impact analysis

Ask questions like `Is this actually reachable in our app?` or `Explain the full impact analysis`

Use this chat to turn dependency paths and call graph output into plain-language exploitability guidance.

<figure><img src="/files/23SBZZB1sFakSVfHBzFa" alt=""><figcaption></figcaption></figure>

This chat can be reached by clicking 'View Reachability Analysis' in the sidebar (for dependency issues). Then click the button 'Ask Aikido' in the bottom left.

#### 3. Refine AutoFix

Use this chat when an AutoFix is close, but not ready to merge. Ask questions like `Can you adjust this patch to X` , `Explain the reasoning for this fix` , `Please add a comment explaining the fix`

You can ask Aikido to:

* match your naming and style conventions
* add tests or small logic changes
* adapt the patch to your architecture

For more on fix refinement, see [Refine AutoFixes with Aikido AI](/autofix-and-remediation/automation-and-merging/refine-autofixes-with-aikido-ai.md).

<figure><img src="/files/ggt70Jj6fZwUUQiSApCV" alt=""><figcaption></figcaption></figure>

### What it knows

Each chat runs with full context: the finding, affected code, CVE metadata, reachability signals, and the diff (where relevant). Answers are grounded in your specific stack, not generic security advice.

### Actions you can take from chat

From the chat, you can:

* ignore the issue with AI-generated reasoning
* create or refine an AutoFix
* save custom context to improve future suggestions

### Related pages

* [How Aikido Uses AI](/ai-and-dev-tools/how-aikido-uses-ai.md)
* [Refine AutoFixes with Aikido AI](/autofix-and-remediation/automation-and-merging/refine-autofixes-with-aikido-ai.md)
* [Introduction to Reachability Analysis](/getting-started/reachability-analysis/introduction-to-reachability-analysis.md)


---

# Agent Instructions: 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:

```
GET https://help.aikido.dev/ai-and-dev-tools/ask-aikido-contextual-ai-chat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.