> For the complete documentation index, see [llms.txt](https://cube.ewelink.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cube.ewelink.cc/blog/faq-you-ask-we-answer.md).

# FAQ - You Ask, We Answer

We see many interesting questions coming from our users in the past months since CUBE OS v0.4 beta released - on Facebook, Discord, and different community groups. Some of you ask about hardware, some about compatibility, and others about the difference between CUBE OS and iHost. Instead of answering them one by one, we thought: why not make it easier for everyone?

That’s why we are starting **“You Ask, We Answer”**. Every two weeks, we will collect the most common questions from the community and share clear answers here. Our goal is simple: help more users understand CUBE OS without digging through endless documents or forum threads.

<figure><img src="/files/7pkEfA2l0neTEoPhwZv5" alt=""><figcaption></figcaption></figure>


---

# 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://cube.ewelink.cc/blog/faq-you-ask-we-answer.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.