> For the complete documentation index, see [llms.txt](https://docs.pinescriptstrategy.com/tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinescriptstrategy.com/tools/settings/visual-info.md).

# Visual Info

<figure><img src="/files/HMMrxr4PwpaRubvm6dxw" alt=""><figcaption><p>"Visual Info" group settings</p></figcaption></figure>

<figure><img src="/files/fnjALfASHyTiEZpZvj5X" alt=""><figcaption><p>"Visual" Info For Trades and Strategy Summary</p></figcaption></figure>

Every Trade comes with entry, exit, TP, SL and a "Trade Summary" visualizations so you can get a detailed view of each trade.

The entire strategy is analyzed and a "Strategy Summary" summarizes the key metrics of your strategy with visual colors hinting at good or bad performance and hot tips and clues built in when you hover over values. There's a lot more than meets the eye here.


---

# 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.pinescriptstrategy.com/tools/settings/visual-info.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.