> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/core/decompiler/concepts/ctree-view.md).
# CTree view
The CTree view is a subview that renders the decompiler's C-level AST (the **ctree**) for the current function.
{% hint style="info" %}
The CTree view is new and still settling. Its layout, the shown information, and the available actions may change in future versions.
{% endhint %}
## Opening the CTree view
You can open the CTree view in two ways:
* Press Ctrl + F6 while viewing a function
* Navigate to **View → Open subviews → Generate ctree**
## What it shows
Each line in the view represents one ctree node, indented to reflect its depth in the tree. Statement and expression node types are printed along with the most important attributes for that kind of node (operand types, referenced variables, immediate values, and so on).
---
# 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.hex-rays.com/core/decompiler/concepts/ctree-view.md?ask=&goal=
```
`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.