> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/cortex-assistant/cortex-assistant-layout.md).

# Cortex Assistant layout

Navigate the Cortex Assistant layout to investigate security data in Cortex XSIAM.

Cortex Assistant consists of the following primary components:

<details>

<summary>Search bar</summary>

The search bar is located at the top of the Cortex Assistant screen. This is where you interact with Cortex Assistant, providing a centralized location to access assistance, obtain insights, and navigate the platform efficiently.

</details>

<details>

<summary>Insights and suggestions</summary>

You can find Cortex Assistant's responses to your queries in the insights and suggestions area. The insights section includes all the important information Cortex Assistant can provide in response to your query.

Below that, Cortex Assistant offers suggestions, which are divided into three columns, each with specific functionalities:

* **Investigate**: Choose from the recommended relevant questions you can ask to further your investigation. Responses leverage advanced XQL queries.
* **Respond**: Take action by running recommended playbooks or scripts, enabling you to initiate response actions based on Cortex Assistant's suggestions.

</details>


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/cortex-assistant/cortex-assistant-layout.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.
